Creating packages for provisioning

You can create packages of all currently available components in the Operations Management Central Monitoring Repository, store those packages in TrueSight Server Automation, and then create a TrueSight Server Automation job to deploy those packages to servers to be installed and configured.

Related topic

Command-line-options-for-configuring-the-TrueSight-Server-Automation-integration

Before you begin

Ensure that your environment is properly set up. See Provisioning Operations Management components with BMC Server Automation.


To create packages for provisioning

In this procedure, you push packages from the Central Monitoring Administration repository (base and extended) to TrueSight Server Automation.

On the computer that hosts the BMC TrueSight Presentation Server, open a command prompt and execute the following command:

(Windows) From the %TRUESIGHTPSERVER_HOME%\truesightpserver\bin folder, execute 
blade.bat auto_prov_prep

(Linux) From the $TRUESIGHTPSERVER_HOME/truesightpserver/bin folder, execute 
./blade.sh auto_prov_prep

This command goes through the repository solutions (in both the base and extended repositories) in Infrastructure Management, and creates for each solution and each version, a new package in TrueSight Server Automation. You must run this command manually to populate all the packages from the repository to TrueSight Server Automation.

If a package already exists in TrueSight Server Automation, it is not updated.


To view the status of the packages in TrueSight Server Automation

Run the following command to view the status of the packages in TrueSight Server Automation.

(Windows) From the %TRUESIGHTPSERVER_HOME%\truesightpserver\bin folder, execute blade.bat get_package_status

(Linux) From the $TRUESIGHTPSERVER_HOME/truesightpserver/bin folder, execute ./blade.sh get_package_status

This XML file contains one entry for each combination of solution and version.

Note

If you import a package or solution using Central Monitoring Administration, the package or solution is automatically populated in TrueSight Server Automation and the status is updated in the BLStatus.xml log file. If the package or solution already exists in TrueSight Server Automation, it will not be populated.

After you push the packages from the repository to TrueSight Server Automation, the next step is to create a property instance in TrueSight Server Automation. For more information, see Creating-a-property-instance-in-TrueSight-Server-Automation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*