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.
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 .
integrate_atrium_cmdbcommand 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.
bmc.uddi.registryserver.secure.enabled=truein the pw\custom\conf\pronet.conf file and restart TrueSight Infrastructure Management server before running the
Use the following script:
cmdbServerHostNameis 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
cmdbServerPortNumberis the Remedy Action Request System TCP port number, used to log into the system server
cmdbUserNameis 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:
uddiServerHostNameis the host name of the UDDI web service where Atrium CMDB is running
uddiServerPortNumberis the port number used by the UDDI web service on the specified host
uddiUserUameis the user name for the UDDI web service
uddiPasswordis the password for the UDDI web service user
cmdbPasswordis the password for the Remedy Action Request System server user
All user names and passwords are case sensitive.
Use the following optional arguments if you need to enable the cross-launch into Infrastructure Management:
webServerProtocolis the ProactiveNet web server protocol, either
proactiveNetWebServerPortNumberis the ProactiveNet web server port number. The default value is 80.
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:
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
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:
psstatcommand. For more information about running the command, see
Started - Automated mode
Started - Manual mode
If the integration was not successful, it is recommended that you use the command line option for performing the integration.
Ensure that you run the
integrate_atrium_cmdb command on both the primary and the secondary hosts in the following way:
To integrate Infrastructure Management with Atrium Service Context, see Enabling cross-launch to Atrium Service Context.