Creating packages to deploy BMC ProactiveNet Agents to BMC Server Automation managed systems
After you have set up and tested the credentials necessary to connect the BMC ProactiveNet Server to the BMC Server Automation managed system, you can create packages so that BMC Server Automation can deploy BMC ProactiveNet Agents to BMC Server Automation managed systems.
Before you begin
- You must have administrator privileges to create these packages.
- A BMC Server Automation RCSD Agent must be installed on the BMC ProactiveNet Server, and it must be running.
- The computer on which the BMC ProactiveNet Server is installed must be accessible from the computer where BMC Server Automation Application Server is installed.
To create packages to deploy BMC ProactiveNet Agents from the BMC ProactiveNet Server to BMC Server Automation managed systems
- Log on to the BMC ProactiveNet Server as administrator.
Access a command line and enter pw blade create packages. If the command succeeds, the following message is displayed.
Creating BMC BladeLogic packages for BMC ProactiveNet agents
This may take a long time...
Info: Creation of BMC BladeLogic packages for BMC ProactiveNet agents succeeded.- Follow the appropriate instructions based on the return code that you receive:
- If the command returns 0, execution was successful.
- If the command returns 1, there is a syntax error. Reenter the pw blade create packages command correctly.
- If the command returns a number other than 0 or 1, an execution error has occurred. An error message is displayed indicating which error occurred.
The BMC ProactiveNet Agent software is loaded into the BMC Server Automation depot in the Software/BMC/ProactiveNet directory as BMC_PN_Agent_version_build_platform. The packages are created in the BMC Server Automation depot in the Packages/BMC/ProactiveNet directory as BMC_PN_Agent_platform. After the packages have been created, use BMC Server Automation to create and run a deploy job to deploy the packages to BMC Server Automation managed systems.
BMC recommends that the BMC Server Automation Application Server and the BMC ProactiveNet Server are in the same LAN. Creating packages across a slow WAN is not recommended because the pw blade create packages command might time out while copying the agent packages from the BMC ProactiveNet Server to the BMC Server Automation Application Server.
Additional change information using snapshot job execution
Certain events (critical or major events) generated or received on BMC ProactiveNet can cause a BMC ProactiveNet provided snapshot job to be executed. This snapshot job captures change information about the device associated with the generated or received event, provided a BMC Server Automation Application server RSCD Agent is also running on that device. This information can be viewed from the BMC Server Automation Application server Device History results screen. For more information, see Viewing BMC Server Automation device history information.
When events matching the criteria mentioned above are received or generated, BMC ProactiveNet refers to the installationDirectory/pronto/conf/supportedDeviceTypesAndOSForBlade.conf mapping file to determine which snapshot jobs to run on BMC Server Automation Application server. If a match is found, the snapshot jobs are executed.
BMC ProactiveNet can run multiple snapshot jobs for a specific device type and operating system combination. The supportedDeviceTypesAndOSForBlade.conf file lists various combinations of device types and operating systems and their associated snapshot jobs.
Limitations
A default throttling logic time period of 10 minutes (can be altered in pronet.conf) needs to elapse before a snapshot job is executed again. This may lead to some events on BMC ProactiveNet not triggering snapshot jobs on BMC Server Automation Application server (because earlier snapshot jobs might not have completed).