Develop > Command Line Tools > Operations Connector Configuration Tool

Operations Connector Configuration Tool

You can reconfigure Operations Connector by running the configuration program bsmc-conf.

The bsmc-conf tool is located on the Operations Connector server at the following location:

Windows: %OvDataDir%\installation\HPOprBSMC\bsmc-conf.bat

Linux: /var/opt/OV/installation/HPOprBSMC/bsmc-conf.sh

Command Syntax

bsmc-conf.[bat|sh] -srv <hostname> [-cs <hostname>] [-f] [-flexmgmt] 
-admin_user <username> <password>
[-https_port <port>] [-http_port <port>]
[-lwsso_domain <domain_name>] [-lwsso_groups <group0> [<group1> ...]] [-lwsso_key <initString>]

Option Descriptions

Option Value
-srv <hostname>

Specifies the OMi Gateway Server to which the Operations Connector sends the collected data.

<hostname> is the full qualified domain name (FQDN) of the OMi Gateway Server.

Default: not set

-cs <hostname>

Specifies the certificate server for your OMi environment.

<hostname> is the FQDN or IP address of the certificate server.

Use this option if you want to issue certificates from a certificate server other than the OMi server specified using the -s option (for example from an Operations Manager server or a OMi server from another OMi deployment).

If you omit this option, bsmc-conf uses the server specified with the -srv option.

When accessing OMi through an IIS secure reverse proxy (SRP), enter the FQDN of the OMi gateway server. For more information on configuring an IIS reverse proxy for OMi, see the OMi Administration section.

-flexmgmt

Creates the flexible management policy BSM Connector FlexMgmt Policy.The policy configures the agent to send the following data to the OMi server:

  • Events generated by Operations Connector policies. These events automatically have the Type attribute set to BSMC_Message.
[-f] Force mode (used to reconnect your Operations Agent).
-admin_user <username> <password>

Specify the credentials for the Operations Connector administrator. This user can access the local Operations Connector instance only by logging on with these credentials, and cannot gain access to OMi.

Default: not set

-https_port <port>

Specify the secure (HTTPS) port at which the Operations Connector user interface runs.

If not specified, port 30000 is used.

-http_port <port>

Specifies the HTTP port at which the Operations Connector user interface runs.

By default, the connection is redirected and HTTPS is used instead.

-lwsso_domain <domain_name>

Specifies the domain of the associated OMi gateway server. For more information about obtaining the domain name, see the Installation and Upgrade section.

LW-SSO does not require an external computer for authentication. LW-SSO enables a user to log into OMi once and gain access to all BSM applications in the same domain without being prompted to log in again. If you configure Operations Connector to use LW-SSO, OMi users can launch the Operations Connector user interface without having to provide additional credentials. For more information about LW-SSO, see the OMi Admin section.

Default: <lwsso_disabled>

-lwsso_groups [<group0> [<group1>...]

Specifies the OMi groups that will have access to Operations Connector. Separate individual groups with spaces (for example, -lwsso_groups BSMC_ADMINS BSMC_OPERS). For information about users and roles, see the Installation and Upgrade .

You cannot add the admin user to a group. If you want a super admin to be able to also have an LW-SSO connection to the Operations Connector, you need to create a separate user which is a super-admin (the check box Super-Admin is selected) and put this user in a group.

By default, LW-SSO is disabled.

-lwsso_key <initString>

Init string from SSO config.

The token key (init string) generated in the OMi Users and Permissions manager.

Single-sign on can only work if the token key that you type here is exactly the same as the token key on the OMi server. For more information about obtaining the token key, see the Installation and Upgrade section.

Default: <lwsso_disabled>

-omc_srv <hostname>

FQDN of the OM management server.

If you omit this option, bsmc-conf takes the value of MANAGER from the internal configuration settings file and inserts it as target server in the flexible management policy Operations Connector FlexMgmt Policy. All events that do not have the Type attribute set to BSMC_Message are sent to this server.

Use the following command to find the current value of MANAGER:

ovconfget sec.core.auth MANAGER

For example,

To configure Operations Connector to connect to the server "server1.company.com", with "server2.company.com" as the certificate server, using the user "admin" with the password "long3Not4short1password!" and using the default HTTPS port, execute:

bsmc-conf.bat -srv server1.company.com -cs server2.company.com -admin_user admin long3Not4short1password!

Command options

-s,-srv <hostname> 

Specifies the OMi server.

<hostname> is the FQDN or IP address of the OMi gateway server, load balancer, or reverse proxy (depending on your OMi deployment) to which you want to connect the Operations Connector.

You can look up the hostname in the Default Virtual Gateway Server for Data Collectors URL infrastructure setting:

Administration > Setup and Maintenance > Infrastructure Settings > Foundations > Platform Administration > Host Configuration

-cs,-cert_srv <hostname>

Specifies the certificate server.

<hostname> is the FQDN or IP address of the certificate server for your OMi environment.

Use this option if you want to issue certificates from a certificate server other than the OMi server specified using the -srv option (for example from an (Undefined variable: OMi.HPOM long) server or a OMi server from another OMi deployment).

If you omit this option, bsmc-conf uses the OMi server specified using the -srv option.

When accessing OMi through an IIS secure reverse proxy (SRP), enter the FQDN of the OMi gateway server. For more information on configuring an IIS reverse proxy for OMi, see the OMi Hardening section.

-f,-force>

Force mode (for example to reconfigure Operations Connector to connect to a different OMi server).

-fm,-flexmgmt

Creates the flexible management policy Operations Connector FlexMgmt Policy.The policy configures the agent to send the following data to the OMi server:

  • Events generated by Operations Connector policies. These events automatically have the Type attribute set to BSMC_Message.

    The OM management server specified using the -omc_svr option receives all events that do not have the Type attribute set to BSMC_Message.

  • Metrics data.

  • Topology data (both legacy and DDM-discovered data).

-omc,-omc_srv <hostname>

FQDN of the OM management server.

If you omit this option, bsmc-conf takes the value of MANAGER from the internal configuration settings file and inserts it as target server in the flexible management policy Operations Connector FlexMgmt Policy. All events that do not have the Type attribute set to BSMC_Message are sent to this server.

Use the following command to find the current value of MANAGER:

ovconfget sec.core.auth MANAGER

-h,-help

Shows tool usage and description.

-v,-version

Displays the Operations Connector version number.

When you run bsmc-conf, the program does the following:

  • Replaces all existing values with new or default values.

  • Creates a backup of the flexible management policy:

    Windows: %OvDataDir%\conf\HPOprIA\<policy_ID>_data.bak

                   %OvDataDir%\conf\HPOprIA\<policy_ID>_header.xml.bak

    Linux: /var/opt/OV/conf/HPOprIA/<policy_ID>_data.bak

              /var/opt/OV/conf/HPOprIA/<policy_ID>_header.xml.bak

To reconnect Operations Connector to another OMi server

  1. On the Operations Connector server, type the following command to reconnect the system to another OMi server:

    bsmc-conf -srv <new OMi server> -force

  2. Add the Operations Connector as a connected server to the OMi Connected Servers manager (Administration > Setup and Maintenance > Connected Servers).

  3. In the Certificate Requests Manager (Administration > Setup and Maintenance > Certificate Requests), grant the certificate generated by bsmc-conf.

  4. Delete the Operations Connector integration from the old OMi server.

  5. Results. Operations Connector sends all collected data to the new OMi server.

To install and configure Operations Connector on an HPOM managed node

  1. On the Operations Connector server, type the following command to configure the Operations Connector on an OM managed node:

    bsmc-conf -srv <new OMi server> -force -flexmgmt -omc_srv <HPOM management server>

  2. Add the Operations Connector as a connected server to the OMi Connected Servers manager (Administration > Setup and Maintenance > Connected Servers).

    Do not select the Configure policy management checkbox.

  3. In the Certificate Requests Manager (Administration > Setup and Maintenance > Certificate Requests), grant the certificate generated by bsmc-conf.

  4. Results. The new OMi server becomes the primary manager of the Operations Agent. The flexible management policy Operations Connector FlexMgmt Policy configures the agent to send the following data to the OMi server:

    • Events generated by Operations Connector policies. These events automatically have the Type attribute set to BSMC_Message.

      The HPOM management server receives only events that do not have the Type attribute set to BSMC_Message.

Log files

bsmc-conf writes information to the following log file:

Windows: %OvDataDir%log/opr-pm-cli.log

Linux: /var/opt/OV/log/opr-pm-cli.log

The tool appends log information to the file when you run the program again.

Using ovconfchg

The command-line tool ovconfchg enables you to change one or more configuration parameters in the internal configuration settings file. ovconfchg is an expert tool and should be used by experienced administrators only.

To run ovconfchg:

Windows: ovconfchg -edit

Linux: /opt/OV/bin/ovconfchg -edit

The -edit option starts a text editor to edit the settings file. After you have saved your changes, you must restart the application.