Enabling cross-launch to BMC Atrium Service Context
You must manually register the Infrastructure Management with the Web Services Registry (UDDI) to enable the cross-launch from the Infrastructure Management operator console to the BMC Atrium Service Context application in the following circumstances:
- You integrated with the BMC Atrium CMDB after you installed the Infrastructure Management components by using either the integrate_atrium_cmdb script or the post installation configuration utility in the operator console.
- You implemented a multiple server deployment of Infrastructure Management.
If you have a multiple server Infrastructure Management deployment, you must configure the mcell.dir file on the computer that hosts the central server before you register the Infrastructure Management with the UDDI registry.
Before you begin
Ensure that you have installed the BMC Atrium Core components (which includes BMC Atrium Service Context) and integrated Infrastructure Management with the BMC Atrium CMDB. For details about installing the BMC Atrium Core components, see BMC Atrium Core online technical documentation. For details about integrating with the BMC Atrium CMDB after you install the Infrastructure Management components, see Configuring-Infrastructure-Management-Integrations-using-the-operator-console or Configuring-BMC-Atrium-CMDB-integration for using the integrate_atrium_cmdb script.
To define the cells associated with the Central and Child Servers in a multi-server deployment
Do the following before you register the Infrastructure Management with the UDDI registry if you have a multiple server Infrastructure Management deployment. If you do not have a multiple server deployment, proceed to the next procedure, To register the Infrastructure Management with the UDDI registry
- Open the mcell.dir file located in the installationDirectory/server/etc directory on the central server computer.
Define each cell associated with the central server and child servers by entering the following line for each cell:
cell cellName encryptionKey hostNameOnWhichCellIsInstalled:portOnWhichCellIsInstalledFor example, if you have three servers in a multiple server deployment, you must enter three cell entries in the mcell.dir file on the central server.
After you edit the mcell.dir file on the central server, perform the following procedure to register the Infrastructure Management with the UDDI registry.
To register the Infrastructure Management Service Context web services with the UDDI registry
Do the following on the computer that hosts the BMC TrueSight Infrastructure Management Server in a single-server deployment or on the computer that hosts the central server in a multiple server deployment.
- From a command line, change to the installationDirectory/pronto/bin directory and run the following command to configure the BMC Atrium CMDB connection information in the installationDirectory/pronto/conf/bppmsaiws.properties file:
bppmsai_integrate_atrium -p "CMDBServer=<CMDBServer>"
[-p "CMDBPort=<CMDBPort>"]
[-p "CMDBUser=<CMDBUser>"]
[-p "CMDBPassword=<CMDBPassword>"] - From the installationDirectory/pronto/bin directory, run the following command to configure the UDDI connection information in the installationDirectory/pronto/conf/bppmsai_uddi_registry.properties file:
bppmsai_integrate_atrium -p "UDDIServer=<UDDIServer>"
[-p "UDDIPort=<UDDIPort>"]
[-p "UDDIUser=<UDDIUser>"]
[-p "UDDIPassword=<UDDIPassword>"] - From the installationDirectory/pronto/bin directory, run the following script:
- (Windows): bppmsai_uddi_publish.cmd
- (Solaris and Linux): bppmsai_uddi_publish.sh
You can now launch the BMC Atrium Service Context application from a configuration item (CI) defined in a service model and displayed in the Tile view, Canvas view, Graph view, or Heat Map view. For details, see Launching the BMC Atrium Service Context application from the operator console.
For more information about BMC Atrium Service Context, see BMC-Atrium-Service-Context-integration-overview and BMC Atrium Core online technical documentation.
To register the Infrastructure Management Service Context web services with the UDDI registry
When UDDI is enabled in TrueSight Infrastructure Management Server, you can cross-launch to the Service Context view from the CI Graph view. The following image displays the CI graph view:
You can view the following page when you cross-launch to the Service Context view:
If a CI status is Unavailable, the following page is displayed:
On the AS-Changemanagement page, click the arrow against the service to view the following page:
Do the following on the computer that hosts the TrueSight Infrastructure Management Server in a single-server deployment or on the computer that hosts the central server in a multiple server deployment.
Open the pw\pronto\conf\bppmsai_uddi_registry.properties file and run the following command:
pw\pronto\bin\bppmsai_integrate_atriumUse the -p options to provide property values for CMDB abd UDDI.
Example
bppmsai_integrate_atrium -p "UDDIServer=<UDDIServer>"[-p "UDDIPort=<UDDIPort>"][-p "UDDIUser=<UDDIUser>"][-p "UDDIPassword=<UDDIPassword>"]
The following parameters are populated:
- bmc.uddiregistry.uddiUsername
- bmc.uddiregistry.uddiPassword
- bmc.uddiregistry.uddiHostname
- bmc.uddiregistry.uddiPort
- bmc.uddiregistry.uddiProtocol
- bmc.bppmsaiws.accessPointUrl
- In the pw\pronto\conf\bppmsai_uddi_registry.properties file, ensure the following:
- The URL of the SOAP web service is correct. For example:
http://<tsim server name>:<tsim port>/bppmsai/services/servicecontext_attr - The following URL returns the WSDL value correctly:
http://<tsim server name>:<tsim port>/bppmsai/services/servicecontext_attr?wsdl
- The URL of the SOAP web service is correct. For example:
Publish the web service in UDDI by using the following command:
pw\pronto\bin\bppmsai_uddi_publishVerify that the web service is correctly published by using the following command:
pw\pronto\bin\bppmsai_uddi_findsvc- Open the pw\pronto\conf\bppmsaiws.properties file and ensure that the CMDB parameters are correctly specified.
- If more than 1 pservers are connected to the CMDB, in the PEnterpriseNodes field, enter the pserver name. The PN:PublishedData form is searched for information about the specified pserver.