BMC Server Automation helps manage, control, and enforce configuration changes in data centers. With the integration of BMC Server Automation, BMC TrueSight Operations Management retrieves change information from BMC Server Automation for Probable Cause Analysis (PCA) candidates.
After you have set up the integration between BMC TrueSight Operations Management and BMC Server Automation, you can create packages so that BMC Server Automation can deploy local agents to BMC Server Automation managed systems.
A BMC Server Automation job might change the configuration of a device, causing its behavior to change. Integrating BMC TrueSight Operations Management with BMC Server Automation makes BMC Server Automation job history information available to probable cause analysis so that when you invoke probable cause analysis for an event, the probable cause analysis results page flags devices which have had BMC Server Automation jobs execute in the same time frame as the event that you are troubleshooting. In addition, certain events that are generated on BMC TrueSight Operations Management trigger the execution of a predefined snapshot job on BMC Server Automation. This snapshot job detects the configuration changes made to the device.
Packages can be created of all components in the Infrastructure Management Central Monitoring Repository. These packages are stored in BMC Server Automation, and then a BMC Server Automation job to deploy those packages to servers to be installed and configured is created.
To create packages for provisioning, you need to push packages from the base Infrastructure Management Central Monitoring Repository to BMC Server Automation, and then push packages from the extended Infrastructure Management Central Monitoring Repository to BMC Server Automation.
The following BMC Server Automation job types are considered during probable cause analysis:
Snapshot job executions are listed in the BladeLogic Device History page only if the snapshot job detects any changes.
Batch jobs also are not listed in the probable cause analysis device history, unless the batch job contains any of the supported job types, such as a deploy job or a Network Shell Script job.
The following table lists the supported software versions for the integration:
|BMC TrueSight Presentation Server
BMC Server Automation
|8.5, 8.6, 8.7
Perform the following tasks after installing the BMC TrueSight Presentation Server:
Add the following entry in the exports file that is located on the computer where TrueSight Presentation Server is installed.
<Installation Directory of rsc>\exports -rw, user=administrator
Default path of <Installation directory of rsc> is C:\Windows\rsc
<Installation Directory of rsc>/exports -rw, user=root
Default path of <Installation directory of rsc> is /etc/rsc
Give appropriate permissions for BladeLogic installation directory on the computer where TrueSight Presentation Server is installed.
Use the command-line commands to enable the integration. For more information, see Command line options for configuring the BMC Server Automation integration.
3. You can change the following integration settings.
|User name to connect to the BMC Server Automation Server
|Password to connect to the BMC Server Automation Server
|Role to connect to BMC Server Automation Server
|Hostname or IP address of BMC Server Automation Web Services or UDDI Server
Port Number of BMC Server Automation Web Services or UDDI Server.
Default port number is 9843.
If you are an existing BMC ProactiveNet customer upgrading to BMC TrueSight Operations Management, the existing BMC Server Automation details are not migrated. You need to manually set up the integration using command-line options on the TrueSight Presentation Server.