BPPM Disabling PATROL Auto Adapter Creation - Tech Note

Summary

 

Configuring the integration between PATROL and the BPPM server involves connecting the remote ProactiveNet agent and Integration Service to the BPPM server. The default configuration of the ProactiveNet remote agent(s) will cause a PATROL adapter to be created and updated automatically. In most cases this behavior may not be desired due to the volume of data it introduces to the BPPM infrastructure including unwanted data that may have been previously filtered.  This note lists the configuration for disabling the automated process.

 

Audience

 

The intended audience for this note are people who are implementing BPPM analytics with PATROL data collection.

 

Usage Scenarios

 

 

IMPORTANT: BMC generally recommends configuring for manual discovering PATROL adapters.  This controls the data sent into the BPPM server and manages scalability.  If you do not wish for the PATROL adapter to automatically discover new KMs and instances DO NOT leave the pproxy.enabled set to "true".  Leave it set to "false".  BPPM versions 8.5 SP5, 8.6 SP3, and 9.0 support a watchdog setting on the Integration Server nodes that ensures the pproxy process is started when the ProactiveNet remote agent is started.  For versions 8.5 SP5, 8.6 SP3, and 9.0 of BPPM, in order for the PATROL adapters to operate in manual mode and never toggle to auto workflow you should configure the following settings in the remote ProactiveNet agents custom pronet.conf file.

      

          pronet.apps.agent.patrol.proxy.enabled=false

          pronet.apps.agent.pproxy.watchdog.enabled=true

 

If you have a previous version of BPPM you should upgrade.  If you cannot upgrade and you wish to use manual adapters you will have to ensure the pproxy process on the Integration Server nodes is automatically started leveraging OS configuration outside the BPPM software.

 

Supporting Materials