Page tree
Skip to end of metadata
Go to start of metadata

During the installation process, you have the option to configure the TrueSight Infrastructure Management Server integration with Atrium CMDB. If you did not configure the Atrium CMDB integration during installation, you can configure it post installation of Infrastructure Management.

Warning

Before you configure integration with Atrium CMDB, ensure that BMC CMDB Extensions are installed on the computer where the Atrium CMDB is installed. For information about installing the CMDB extensions, see Preparing for BMC Atrium CMDB integration .

Notes

  • The UDDI parameters in the integrate_atrium_cmdb command are optional because UDDI is not mandatory for Infrastructure Management to integrate with BMC Atrium CMDB. If UDDI is not configured then there will be no cross launch from operator console into the federated links configured in BMC Atrium CMDB.
  • If UDDI is configured for HTTPS, set bmc.uddi.registryserver.secure.enabled=true  in the pw\custom\conf\pronet.conf file and restart TrueSight Infrastructure Management server before running the integrate_atrium_cmdb  script.

Use the following script:

integrate_atrium_cmdb [-uddi_server_host_name <uddiServerHostName>] [-uddi_server_port_no <uddiServerPortNumber>] [-uddi_user_name <uddiUserUame>] [-uddi_password  <uddiPassword>] -cmdb_server_host_name <cmdbServerHostName> -cmdb_server_port_no <cmdbServerPortNumber> -cmdb_user_name <cmdbUserName> [-cmdb_password  <cmdbPassword>] -cmdb_version <cmdbVersion> [-bppm_webserver_protocol <webServerProtocol>] [-bppm_webserver_port_no <proactiveNetWebServerPortNumber>] [-enterprise (T|F)]

where,

  • cmdbServerHostName is the host name where Atrium CMDB is running. For integration with an AR Server Group, cmdbServerHostName is the AR Server load balancer host name or the AR Server integration server host name
  • cmdbServerPortNumber is the Remedy Action Request System TCP port number, used to log into the system server
  • cmdbUserName is the user name to access the BMC Remedy Action Request System server

Use the following optional arguments if you need Infrastructure Management to cross-launch into other Atrium applications:

  • (Optional) uddiServerHostName is the host name of the UDDI web service where Atrium CMDB is running
  • (Optional) uddiServerPortNumber is the port number used by the UDDI web service on the specified host
  • (Optional) uddiUserUame is the user name for the UDDI web service
  • (Optional) uddiPassword is the password for the UDDI web service user
  • (Optional) cmdbPassword is the password for the Remedy Action Request System server user

Note

All user names and passwords are case sensitive.

Use the following optional arguments if you need to enable the cross-launch into Infrastructure Management:

  • webServerProtocol is the ProactiveNet web server protocol, either http (default) or https.
  • proactiveNetWebServerPortNumber is the ProactiveNet web server port number. The default value is 80.
  • -enterprise (T|F) indicates whether or not your enterprise environment has multiple Infrastructure Management Servers that will be communicating with the same CMDB.

For example:

integrate_atrium_cmdb -uddi_server_host_name Vm-w23-rds1184 -uddi_server_port_no 8080 -uddi_user_name admin -uddi_password admin -cmdb_server_host_name Vm-w23-rds1183 -cmdb_server_port_no 5555 -cmdb_user_name Admin -cmdb_password Admin -cmdb_version 7.6.04 -bppm_webserver_protocol https -bppm_webserver_port_no 8888 -enterprise T

If you integrate with Atrium CMDB in an AR Server Group, you must manually configure the pserver.conf file. Edit the ARSGroupMembers in the pserver.conf file and set to all AR Servers of the group that have reconciliation function enabled. See also Configuring the Publishing Server to integrate with an AR Server group.

If you run integrate_atrium_cmdb without providing UDDI settings and later require cross launch, then at that time you can configure the UDDI settings via the pw cmdb settings command.

At the time of installation, if you have selected not to integrate BMC Atrium CMDB, then you need to configure SDIG. For more information, see Configuring the integration with BMC Service Resolution. 

Integration notes for an HA environment

If you are running Infrastructure Management in the high-availability mode, you can integrate with Atrium CMDB by using the Operator Console or the command line interface.

The following notes are important based on the option that you choose for performing the integration:

 If you are using the Operator Console

Ensure that you perform the integration from the Infrastructure Management's load balancer node.

For more information about using the Operator Console for performing the integration, see Configuring Infrastructure Management Integrations using the operator console.

When you provide details of the Atrium CMDB server (on the Configure Infrastructure Management Integrations dialog box) and click Apply, it is possible that you see the following error:

Error occurred while loading data from server

In this scenario, you can verify if the integration was successful by using one of the following methods:

  • Run the psstat command. For more information about running the command, see psstat command.
    If the command returns one of the following messages, it indicates that the integration was successful. You can ignore the error.
    • Started - Automated mode
    • Started - Manual mode
  • Navigate to the %TSIM INSTALLATION PATH%/pw/server/etc/pserver.conf file and check if the following properties are populated with the integration details that you provided.
    • CMDBServer
    • CMDBPort
    • CMDBUser
    • CMDBPassword
    If the preceding properties are populated, it indicates that the integration was successful. You can ignore the error.

If the integration was not successful, it is recommended that you use the command line option for performing the integration.


 If you are using the command line

Ensure that you run the integrate_atrium_cmdb command on both the primary and the secondary hosts in the following way:

  1. Navigate to the primary host and run the integrate_atrium_cmdb command.
  2. Stop the Infrastructure Management server on the primary host.
    This will ensure that the secondary host becomes active.
  3. Navigate to the secondary host and run the integrate_atrium_cmdb command.


To integrate Infrastructure Management with Atrium Service Context, see Enabling cross-launch to Atrium Service Context.