Operations Connector Configuration Tool

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 HP 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. Note: 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 guide.
`-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 HPE 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 Guide. 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 Guide. 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 Guide. Note: 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. Note: 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 Guide. 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. Tip: Use the following command to find the current value of `MANAGER`: `ovconfget sec.core.auth MANAGER`

Example

To configure HPE 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!

To reconnect Operations Connector to another OMi server

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

bsmc-conf -srv <new OMi server> -force
Add the Operations Connector as a connected server to the OMi Connected Servers manager (Administration > Setup and Maintenance > Connected Servers).
In the Certificate Requests Manager (Administration > Setup and Maintenance > Certificate Requests), grant the certificate generated by bsmc-conf.
Delete the Operations Connector integration from the old OMi server.
Results. Operations Connector sends all collected data to the new OMi server.

To install and configure Operations Connector on an HPOM managed node

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>
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.
In the Certificate Requests Manager (Administration > Setup and Maintenance > Certificate Requests), grant the certificate generated by bsmc-conf.
Results. The new OMi server becomes the primary manager of the HPE 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.