ovbbccb

NAME

ovbbccb

- control HTTPS communication using HP Operations Communication Broker proxies 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

You use the ovbbccb command to control HTTPS communication using HP Operations Communication Broker proxies on local nodes. It controls the starting of the Communication Broker as a background daemon process or in normal mode, stopping, and re-initializing of the Communication Broker. You can also use the command to start and stop HPOM Resource Groups in the Communication Broker.

In addition, you can use the command to list all active HPOM 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. For example, the syntax for the [<hostname>|<ip>][:<port>]] string in the options -registrations or -ping can be a hostname and a port separated by a colon (:). It can also be a full URL path, including protocol.

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 HPOM communication in use.

-install

Installs the Communications Broker program as a service on a Microsoft Windows machine.

-remove

Removes the Communications Broker program from the services on a Microsoft Windows machine.

-daemon

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

-nodaemon

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

-debug

Disable the Control-C signal handler for debugging.

-verbose

Shows more detailed output.

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

Starts the HPOM Resource Group specified by <ovrg> in the Communication Broker on the host specified by <hostname> or <ip>. If you do not specify the hostname or IP, ovbbccb uses the local host as the host. You must configure the HPOM Resource Group on a cluster node to use this option.

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

Stops the HPOM Resource Group specified by <ovrg> in the Communication Broker on the host specified by <hostname> or <ip>. If you do not specify the hostname or IP, ovbbccb uses the local host as the host. You must configure the HPOM Resource Group on a cluster node to use this option.

-kill [<hostname>|<ip>]

Stops the Communication Broker on the host specified by <hostname> or <ip>. If you do not specify the hostname or IP, ovbbccb used 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.

-reinit [<hostname>|<ip>]

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

You can also use the SIGHUP signal on UNIX systems to re-initialize 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 HPOM Resource Group for the Communication Broker on the node specified by <hostname> or <ip>. If you do not specify the hostname or IP, ovbbccb uses the localhost 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 HPOM for Windows server process. To locate the server process to ping, you can provide a hostname or IP address with an optional port number or a URI. If you provide a URI with the path of a valid process registered with the Communication Broker, the Communication Broker automatically forwards the ping to the registered process. You can specify the node with a hostname or IP address. The default for the node is localhost. The default for the port is the HP Operations Communication Broker port on the specified node.

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

Displays the status of the specified HPOM for Windows server process. To locate the server process, you can provide a hostname or IP address with an optional port number. The default for the node is localhost. The default for the port is the Communication 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 was encountered. For possible values, see the command syntax.

2

Command partially succeeded.

3

Command failed. For details, see the command output.

4

Communications Broker start command failed because a Communications Broker process is already running.

5

Communications Broker failed to start because a Local Location Broker process is already running. The Communications Broker is not supported on systems running the LLB. Stop the LLB before attempting to start the Communications Broker.

6

Communications Broker failed to stop because the Communications Broker process is already stopped.

7

Communications Broker failed to start because of a bind exception on the Communications Broker port to be opened.

8

Communications Broker could not complete the command because of an authorization error.

100

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 HPOM Resource Group WebCluster1 in the Communication Broker on host merlin:

  ovbbccb -start WebCluster1 merlin

• To display the status of the specified HPOM for Windows server process:

  ovbbccb -status
  

  Status: OK
  

  (Namespace, Port, Bind Address, Open Sockets)
  

  <default> 383	ANY	2
  

  HP Operations HTTP Communication Incoming Connections 
  

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

  HP Operations 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(1), bbc.ini(4).

COPYRIGHT

© Copyright 2001-2007 Hewlett-Packard Development Company, L.P.

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