BMC PATROL Agent is a core component of the BMC ProactiveNet architecture that monitors and manages the distributed environment.
A BMC PATROL Agent performs the following tasks:
For information about BMC PATROL Agent, see BMC PATROL Agent 9.0.
BMC PATROL Agent is configured for BMC ProactiveNet using BMC ProactiveNet Central Monitoring Administration.
For information about BMC ProactiveNet Central Monitoring Administration, see BMC ProactiveNet Central Monitoring Administration architecture.
The BMC PATROL Agent reads the tag information from the following pconfig variable:
/AgentSetup/Identification/Tags/Tag/tagName, where tagName is the name of the tag
The BMC PATROL Agent sends the information to the Integration Service, which passes the information to Central Monitoring Administration. Central Monitoring Administration evaluates policies that match the tags or the agent properties, determines the final configuration to be applied, and sends the configuration information back to the agent. Monitoring is based on the configuration information received by the agent, under /AgentSetup/preloadedKMs pconfig variable. It contains the list of .kml files that must be loaded for the corresponding configuration.
The BMC PATROL Agent initiates a configuration request after certain events, such as agent installation, agent restart, agent auto-connection with Integration Service, or changing a tag on the agent. If no policy matches the agent conditions, the agent does not receive configuration information. The agent does not receive the configuration until a matching policy is created.
If a policy is created or updated, changes are pushed from Central Monitoring Administration, via the Integration Service, to BMC PATROL Agents, and the /AgentSetup/preloadedKMs pconfig variable is received as a part of configuration.
The monitoring solutions configuration is stored under /ConfigData pconfig branch. The pconfig variables received by BMC PATROL Agent from Central Monitoring Administration are with REPLACE request. For the configuration under /ConfigData, only the difference between the configuration received and the configuration that the agent contains is applied. If some configuration is not received, it is considered to be deleted and is deleted from /ConfigData. For the configuration under /AgentSetup, it is applied directly.
For /AgentSetup configurations, the variables under the /ConfigData pconfig branch take precedence.
You should not manually update any variables and values under /ConfigData. The variables and values are only for internal use.
For information about BMC PATROL Agent, see the BMC PATROL Agent 9.0.