.\"Generated by nroff_template.wdt (12-Sep-06). Do NOT edit this output file. Instead, edit the source FM+SGML file.
.de Sh \" Subsection
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Ip \" List item
.br
.ie \\n(.$>=3 .ne \\$3
.el .ne 3
.IP "\\$1" \\$2
..
.TH ovbbccb "" "" ""
.ds )H Hewlett-Packard Company
.ds ]L
.ds ]W June 2007
.SH NAME
ovbbccb - Controls HTTPS communication using Communication Broker proxies on local nodes.
.SH "SYNOPSIS"

.PP
ovbbccb -h|-help 

.PP
ovbbccb -version 

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

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

.PP
ovbbccb -start|-stop <\fIovrg\fR> [<\fIhostname\fR>|<\fIip\fR>] [-v|-verbose] 

.PP
ovbbccb -kill|-reinit [<\fIhostname\fR>|<\fIip\fR>] [-v|-verbose] 

.PP
ovbbccb -listovrg [<\fIhostname\fR>|<\fIip\fR>] [-v|-verbose] 

.PP
ovbbccb -ping {[<\fIhostname\fR>|<\fIip\fR>[:<\fIport\fR>]] | [<\fIuri\fR>} [-v|-verbose]] 

.PP
ovbbccb -status {[<\fIhostname\fR>|<\fIip\fR>[:<\fIport\fR>]] | [<\fIuri\fR>} [-v|-verbose]] 

.SH "DESCRIPTION"

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

.LP
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.

.Sh "Parameters"

.LP
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:

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

.LP
ovbbccb recognizes the following options:

.TP
-h|-help

Displays and describes the available options for the ovbbccb command.

.TP
-version

Displays the version of the OV communication in use.

.TP
-install

Installs the HP OpenView Communications Broker program as a service on an MS Windows machine.

.TP
-remove 

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

.TP
-daemon 

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

.TP
-nodaemon

Starts the Communication Broker as a foreground process (\fIdefault\fR).

.TP
-debug

Disable Control-C signal handler for debugging.

.TP
-verbose

Shows more detailed output.

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

Starts the OV resource group specified by \fI<ovrg>\fR in the Communication Broker on the host specified by \fI<hostname>\fR or \fI <ip>\fR. 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.

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

Stops the OV resource group specified by \fI<ovrg>\fR in the Communication Broker on the host specified by \fI<hostname>\fR or \fI <ip>\fR. 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.

.TP
-kill [<hostname>|<ip>]

Stops the Communication Broker on the host specified by \fI<hostname>\fR or\fI <ip>\fR. If the hostname or IP is not specified, 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.

.TP
-reinit [<hostname>|<ip>]

The Communication Broker specified in \fI<hostname>\fR or \fI <ip>\fR 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-initialize the Communication Broker process.

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

.TP
-listovrg [<hostname>|<ip>]

Displays a list of all active OV resource groups for the Communication Broker on the node specified by \fI<hostname>\fR or \fI <ip>\fR. 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.

.TP
-ping {[<\fIhostname\fR>|<\fIip\fR>[:<\fIport\fR>]] | [<\fIuri\fR>]}

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 Broker, 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.

.TP
-status {[<\fIhostname\fR>|<\fIip\fR>[:<\fIport\fR>]] | [<\fIuri\fR>]}

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 Communication Broker port on the specified node.

.SH "AUTHOR"

.LP
ovbbccb was developed by Hewlett-Packard Company.

.SH "EXIT STATUS"

.LP
The following exit values are returned:

.TP
0

ovbbccb exited normally with no error.

.TP
1

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

.TP
2

Command partially succeeded.

.TP
3

Command failed. See command output for more detailed information.

.TP
4

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

.TP
5

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

.TP
6

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

.TP
7

The Communications Broker failed to start due to a bind exception on the Communications Broker port to be opened.

.TP
8

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

.TP
100

An exception was encountered causing the Communications Broker to exit.

.LP
Corresponding error messages are written to stderror.

.SH "EXAMPLES"

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

.TP 3
\(bu 
To start the Communication Broker as a daemon process on the local system:

ovbbccb -daemon

.TP
\(bu 
To start the OV resource group WebCluster1 in the Communication Broker on host merlin:

ovbbccb -start WebCluster1 merlin

.TP
\(bu 
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
.LP

.SH "SEE ALSO"

.LP
bbcutil bbc.ini

.SH "COPYRIGHT"

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

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