Installing the BMC ProactiveNet provided content on BMC Server Automation

BMC ProactiveNet provides predefined content by means of a content installer that helps load BMC ProactiveNet content into the BMC Server Automation Application Server.

You can create content that is more tuned to your environment by customizing the BMC ProactiveNet provided content or by creating new content (as described in Creating-new-BMC-Server-Automation-content). This content helps collect relevant configuration change information, which helps probable cause analysis. BMC ProactiveNet provided content consists of three component templates, three associated snapshot jobs, and three associated component discovery jobs. BMC ProactiveNet provides content that is appropriate for capturing configuration change for Solaris OS, Apache Web server on Solaris OS, and for WebLogic application server on Solaris OS.

Installing the BMC ProactiveNet provided content on BMC Server Automation

1. Log on to the BMC EPD website at https://webapps.bmc.com/epd/faces/licensedProd.jsp

2. In the Product Name column, expand BMC BladeLogic Server Automation Suite > BMC BladeLogic Server Automation Suite 8.5.00, and select the following links depending on your operating system to download the BMC ProactiveNet content installer:
   
   

   OS	File name
   Microsoft Windows	BSA 8.5.00 SP1 Server Automation PPM for Windows
   Solaris	BSA 8.5.00 SP1 Server Automation PPM for Solaris
   Linux	BSA 8.5.00 SP1 Server Automation PPM for Linux

3. Copy the content installer to the computer where BMC Server Automation Application Server is installed. 

4. Run the content installer which imports the BMC ProactiveNet provided content into the BMC Server Automation Application Server using the following command:

   <full path to Setup file> -i silent -DOPTIONS_FILE=<full path to Options file>

   Information

   Example

   ../PPM81-SOL8-SPARC.bin -i silent DOPTIONS_FILE=PPM_silent_install_sample.txt

5. Edit all three component discovery jobs (PPM-SolarisOS-ComponentDiscovery, PPM-ApacheSolaris-ComponentDiscovery, and PPM-WeblogicComponentDiscovery) to assign the proper targets and create an appropriate schedule for the component discovery jobs. Run all three component discovery jobs once. This step is mandatory.

   The component discovery job must run at least once on all targets so that components, if any, can be discovered. Snapshot jobs run on the same targets do not work unless components have been discovered, where

   v_n-nnn is the BMC Server Automation version number.

6. Edit all three snapshot jobs (PPM-SolarisOS-Snapshot, PPM-ApacheSolaris-Snapshot, PPM-WeblogicSolaris-Snapshot) to assign the proper targets and create an appropriate schedule for the snapshot jobs. Run all three snapshot jobs once. This step is mandatory.