To manage a BSM Connector system with HPOM, you need to configure an agent-based flexible management policy. The policy configures the OMi server as the primary manager of BSM Connector, and the HPOM management server as a secondary and action-allowed management server. This enables the HPOM management server to start actions, and deploy policies and packages.
The policy also configures HP Operations Agent to send the collected data as follows:
The OMi server receives all events generated by BSM Connector policies that have the Type attribute set to BSMC_Message.
The HPOM management server receives all events that do not have the Type attribute set to BSMC_Message.
BSM Connector sets the event type attribute automatically to BSMC_Message
. You can delete the value in a policy but BSM Connector inserts it again when you save the policy. The type attribute is available in the Advanced attributes tab of the policy editors.
The BSM Connector server stores all metrics data.
The OMi server receives all topology data (both HP Operations Agent and DFM-discovered data).
Note:
The flexible management policy cannot be edited in the BSM Connector user interface.
In the procedures below, use the ovcoreid
command-line tool to find out the required core ID of the system.
Exchange certificates between the OMi and HPOM systems. For information about exchanging certificates, see To configure trusted certificates:.
On the HPOM management server, use the Configure Managed Nodes dialog box to add the BSM Connector system as a managed node. In the node's properties, manually add the core ID and set the certificate state to Installed
.
On the BSM Connector system, create and activate an agent-based flexible management policy:
Make a copy of the flexible management policy template.
Open a command prompt and type:
copy "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_data.template" "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_data"
copy "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_header.xml.template" "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_header.xml"
Open a shell and type:
cp /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_data.template /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_data
cp /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_header.xml.template /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_header.xml
Edit the policy data file f6b8aff0-f467-4851-8407-5b60395648b4_data
.
Locate the string ${OM_MGR_SRV}
and replace all occurrences with the FQDN of the HPOM management server.
Locate the string ${OM_MGR_SRV_ID}
and replace all occurrences with the core ID of the HPOM management server.
Locate the string ${OMi_MGR_SRV}
and replace all occurrences with the FQDN of the OMi gateway server.
Locate the string ${OMi_MGR_SRV_ID}
and replace all occurrences with the core ID of the OMi data processing server.
Save the policy data file. Import the policy in BSM Connector and activate it.
In the HPOM console, right-click the node that represents the BSM Connector system and select All Tasks > Synchronize inventory > Packages.
On the HPOM management server, check that you can manage the BSM Connector system, type:
opcragt -status <BSM Connector hostname>
The output should indicate that the agent is running.
For more information about HPOM for Windows, see the HPOM for Windows online help.
Exchange certificates between the OMi and HPOM systems. For information about exchanging certificates, see To configure trusted certificates:.
On the HPOM management server, add the BSM Connector system as a managed node, type:
opcnode -add_node <BSM Connector hostname>
On the HPOM management server, specify the core ID of the BSM Connector server, type:
opcnode -chg_id node_name=<BSM Connector hostname> id=<core ID of BSM Connector system>
On the BSM Connector system, create and activate an agent-based flexible management policy:
Make a copy of the flexible management policy template.
Open a command prompt and type:
copy "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_data.template" "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_data"
copy "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_header.xml.template" "%OvDataDir%\conf\HPOprBSMC\f6b8aff0-f467-4851-8407-5b60395648b4_header.xml"
Open a shell and type:
cp /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_data.template /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_data
cp /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_header.xml.template /var/opt/OV/conf/HPOprBSMC/f6b8aff0-f467-4851-8407-5b60395648b4_header.xml
Edit the policy data file f6b8aff0-f467-4851-8407-5b60395648b4_data
.
Locate the string ${OM_MGR_SRV}
and replace all occurrences with the FQDN of the HPOM management server.
Locate the string ${OM_MGR_SRV_ID}
and replace all occurrences with the core ID of the HPOM management server.
Locate the string ${OMi_MGR_SRV}
and replace all occurrences with the FQDN of the OMi gateway server.
Locate the string ${OMi_MGR_SRV_ID}
and replace all occurrences with the core ID of the OMi data processing server.
Save the policy data file. Import the policy in BSM Connector and activate it.
On the HPOM management server, check that you can manage the BSM Connector system, type:
opcragt -status <BSM Connector hostname>
The output should indicate that the agent is running.
For more information about HPOM for UNIX or Linux, see the documentation that HPOM for UNIX or Linux provides.
In an environment with multiple servers, you must configure each server to trust certificates that the other servers issued. This task involves exporting every server's trusted certificate, and then importing this trusted certificate to every other server. You must also update the agent's trusted certificates, so that the agent also trusts the OMi servers.
Configure trusted certificates for every server (OMi gateway and data processing servers, HPOM management server):
On every OMi server, export the trusted certificate to a file using the following command:
ovcert -exporttrusted -file <file>
The command generates a file with the name that you specify.
Copy each file to every other server, and then import the trusted certificate using the following commands:
ovcert -importtrusted -file <file>
ovcert -importtrusted -ovrg server -file <file>
On the BSM Connector system, update the trusted certificates using the following command:
ovcert –updatetrusted