ovbbccb man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

ovbbccb()							     ovbbccb()

NAME
       ovbbccb - Controls HTTPS communication using Communication Broker prox‐
       ies on local nodes.

SYNOPSIS
       ovbbccb -h|-help

       ovbbccb -version

       ovbbccb -install|-remove [-v|-verbose]

       ovbbccb -daemon|-nodaemon [-debug] [-v|-verbose]

       ovbbccb -start|-stop <ovrg> [<hostname>|<ip>] [-v|-verbose]

       ovbbccb -kill|-reinit [<hostname>|<ip>] [-v|-verbose]

       ovbbccb -listovrg [<hostname>|<ip>] [-v|-verbose]

       ovbbccb -ping {[<hostname>|<ip>[:<port>]] | [<uri>} [-v|-verbose]]

       ovbbccb -status {[<hostname>|<ip>[:<port>]] | [<uri>} [-v|-verbose]]

DESCRIPTION
       ovbbccb command is used to control HTTPS communication using Communica‐
       tion  Broker proxies on local nodes. It controls starting of the Commu‐
       nication Broker as a background daemon process or in normal mode, stop‐
       ping,  and re-initializing of the Communication Broker. ovbbccb is also
       used to start and stop OV resource groups in the Communication Broker.

       ovbbccb can also be used to list all active OV resource groups and  all
       applications  registered	 to  a	Communication Broker, to check whether
       specified communication services are alive and to display details about
       the current state of the server.

       Parameters

       The ovbbccb command incorporates the options in the following list. The
       syntax for the [<hostname>|<ip>][:<port>]] string, for example; in  the
       options -registrations or -ping, can be a hostname and a port separated
       by a colon (:) but can also be a full URL path including protocol.  for
       example:

       https://merlin.guilford.mycom.com:383/com.hp.ov.coda

       ovbbccb recognizes the following options:

       -h|-help

	      Displays	and  describes	the  available options for the ovbbccb
	      command.

       -version

	      Displays the version of the OV communication in use.

       -install

	      Installs the HP OpenView Communications Broker program as a ser‐
	      vice on an MS Windows machine.

       -remove

	      Removes  the  HP OpenView Communications Broker program from the
	      services on an MS Windows machine.

       -daemon

	      Starts the Communication Broker either as	 a  background	daemon
	      process on a UNIX machine or a service on an MS Windows machine.

       -nodaemon

	      Starts   the   Communication  Broker  as	a  foreground  process
	      (default).

       -debug

	      Disable Control-C signal handler for debugging.

       -verbose

	      Shows more detailed output.

       -start <ovrg> [<hostname>|<ip>]

	      Starts the OV resource group specified by <ovrg> in the Communi‐
	      cation  Broker  on the host specified by <hostname> or  <ip>. If
	      the hostname or IP is not specified, ovbbccb uses the local host
	      as  the host. You must configure the resource group on a cluster
	      node to use this option.

       -stop <ovrg> [<hostname>|<ip>]

	      Stops the OV resource group specified by <ovrg> in the  Communi‐
	      cation  Broker  on the host specified by <hostname> or  <ip>. If
	      the hostname or IP is not specified, ovbbccb uses the local host
	      as  the host. You must configure the resource group on a cluster
	      node to use this option.

       -kill [<hostname>|<ip>]

	      Stops the Communication Broker on the host specified  by	<host‐
	      name>  or	 <ip>. If the hostname or IP is not specified, ovbbccb
	      used the local host as the host. You  must  set  the  LOCAL_CON‐
	      TROL_ONLY	 parameter  to	false  to  make	 this option work on a
	      remote node.

       -reinit [<hostname>|<ip>]

	      The  Communication  Broker  specified  in	 <hostname>  or	  <ip>
	      reloads  the  configuration  data	 and is re-initialized. If the
	      hostname or IP is not specified, ovbbccb uses the local host  as
	      the host.

	      The  SIGHUP  signal  may also be used on UNIX systems to re-ini‐
	      tialize the Communication Broker process.

	      You must set the LOCAL_CONTROL_ONLY parameter to false  to  make
	      this option work on a remote node.

       -listovrg [<hostname>|<ip>]

	      Displays	a list of all active OV resource groups for the Commu‐
	      nication Broker on the node specified by <hostname> or  <ip>. If
	      the hostname or IP is not specified, ovbbccb uses the local host
	      as the host. You must set the  LOCAL_CONTROL_ONLY	 parameter  to
	      false to make this option work on a remote node.

       -ping {[<hostname>|<ip>[:<port>]] | [<uri>]}

	      Pings the specified HP OpenView server process. A hostname or IP
	      address with an optional port number or a URI may	 be  given  to
	      locate  the  server  process to ping. If a URI is given with the
	      path of a valid process registered with the  Communication  Bro‐
	      ker,  the	 Communication	Broker	will automatically forward the
	      ping to the registered process. The node may be specified with a
	      hostname	or  IP	address.  Default for the node is "localhost".
	      Default for the port is the  HP  OpenView	 Communication	Broker
	      port on the specified node.

       -status {[<hostname>|<ip>[:<port>]] | [<uri>]}

	      Displays the status of the specified HP OpenView server process.
	      A hostname or IP address with an optional	 port  number  may  be
	      given  to	 locate	 the  server  process. Default for the node is
	      "localhost". Default for the port is the HP OpenView  Communica‐
	      tion Broker port on the specified node.

AUTHOR
       ovbbccb was developed by Hewlett-Packard Company.

EXIT STATUS
       The following exit values are returned:

       0

	      ovbbccb exited normally with no error.

       1

	      Command  syntax  error  encountered. See command syntax for more
	      details on possible values.

       2

	      Command partially succeeded.

       3

	      Command failed. See command output for  more  detailed  informa‐
	      tion.

       4

	      The  Communications Broker start command failed because a Commu‐
	      nications Broker process is already running

       5

	      The Communications Broker failed to start because a Local	 Loca‐
	      tion Broker process is already running. The HP OpenView Communi‐
	      cations Broker is not supported on systems running the LLB. Stop
	      the LLB before attempting to start the Communications Broker.

       6

	      The  Communications Broker failed to stop because the Communica‐
	      tions Broker process is already stopped.

       7

	      The Communications Broker failed to start due to a  bind	excep‐
	      tion on the Communications Broker port to be opened.

       8

	      The  Communications Broker could not complete the command due to
	      an authorization error.

       100

	      An exception was encountered causing the	Communications	Broker
	      to exit.

       Corresponding error messages are written to stderror.

EXAMPLES
       The following examples show you how to use the ovbbccb command:

       ·  To  start  the Communication Broker as a daemon process on the local
	  system:

	  ovbbccb -daemon

       ·  To start the OV resource group WebCluster1 in the Communication Bro‐
	  ker on host merlin:

	  ovbbccb -start WebCluster1 merlin

       ·  To display the status of the specified HP OpenView server process:

	  ovbbccb -status

	  Status: OK

	  (Namespace, Port, Bind Address, Open Sockets)

	  <default>    383    ANY    2

	  HP OpenView HTTP Communication Incoming Connections

	      localhost:55467	  e91b67e4-a337-750a-163c-c3bbd2c257cc	   BBC
	  06.00.030; ovbbccb 06.00.030

	  HP OpenView HTTP Communication Reverse Channel Connections

	   Opened:

	    ovsolt9.india.hp.com:9090	 BBC 06.00.030; ovbbcrcp 06.00.030

	  Failed:

	    abc:990 Host Unknown

	  Pending:

	    gdstgd:9809 Host Unknown

SEE ALSO
       bbcutil bbc.ini

COPYRIGHT
       (c) Copyright 2001-2007 Hewlett-Packard Development Company, L.P.

       HP shall not be liable for technical or editorial errors	 or  omissions
       contained herein.

								     ovbbccb()
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net