Share This:

If you have BPPM 9.x you have access to the Central Monitoring Administration which allows you to manage BMC PATROL configuration across one or more BMC ProactiveNet Child Servers


The diagram below illustrates a multiple BPPM Server environment with a Central BPPM Server with the Central Management and Administration (CMA) module and Child Servers.





BMC Recommends implementing one of two architectures for CMA.  The two options are listed below with their pros and cons.


Option One - Implement a single CMA Instance for all environments including Development, Test and Production.


1)    The creation, testing, and deployment of monitoring policies into production are very easy because you do not have to copy or export/import any data.  The application of policies to Development, Test and Production is simply managed in the policy’s agent selection criteria.


2)    It requires less infrastructure nodes and components.  Only a single Staging Integration Service host is needed.  Only a single CMA instance is used.


1)    This many not be supported in some sites where all the necessary connections between Development, Test and Production environments are not available or allowed to be connected over the network.


2)    Due to the powerful ease of use, it is easier for administrators to make mistakes applying policies unintentionally to production.  However, this can be managed.


Option Two - Implement a separate CMA Instance for the Development, Test and Production environments each.


1)    Is supported in sites where all the necessary connections between Development, Test and Production environments are not available or allowed to be connected over the network.


2)    Provides a platform and supports policy management methods that help prevent administrators from making mistakes when applying policies to production.


1)    The creation, testing, and deployment of monitoring policies into production require more manual effort because you have to export/import policy data from Development to Test and from Test to Production.


2)    Policies could get out of synch across the Development, Test, and Production environments if not managed properly.  Keeping them up to date is more of a manual process supported by the export/import utility.


3)    It requires more infrastructure nodes and components.  The Development, Test, and Production environments should each have a dedicated Staging Integration Service host and a dedicated CMA instance.


IMPORTANT: Neither method supports seamless creation, testing, and production deployment of updates and deletion for existing policies.  Updates and deletion of existing policies that are already in production should be created, tested, and populated to production leveraging the policy export/import capability.  This topic is discussed in detail in the configuration best practices.

In all scenarios, CMA communicates thorough the agent controller process on the BPPM Server(s) to the Integration Service nodes.


These implementation architecture options are not installation options.  The CMA components are the same.  These two implementation architecture options are simply choices in how you install CMA instances and connect them to the various BPPM Servers.

Accessing Central Monitoring Administration

1.    Ensure that you have access to Central Monitoring Administration.

2.    In a supported browser, open http://serverHostName/admin.

The serverHostName variable is the name of the BMC ProactiveNet Central Server where Central Monitoring Administration is enabled.

3.    Log in to Central Monitoring Administration.

The default user name and password are admin


Once you have accessed the Central Monitoring Administration console, what can you do? Here’s a couple of topics of interest:

Setting an intelligent threshold using Central Monitoring Administration

Which monitoring solutions can be configured using BMC ProactiveNet Central Monitoring Administration

Create or Edit a monitoring policy


BMC ProactiveNet Central Monitoring Administration enhancements in BPPM 9.5 - BMC ProactiveNet Central Monitoring Administration is enhanced to perform the following tasks:

•Configuring Monitoring policies

•Configuring Staging policies

•Configuring Blackout policies

•Adding Integration Services to BMC ProactiveNet Server

•Creating Integration Service clusters

•Enabling Global thresholds


Connectivity between the Integration Service processes and the Central Management & Administration module (CMA) has been consolidated.  CMA now communicates with each Integration Service through the BPPM Server that the Integration Service is connected to.

The new Central Monitoring Administration features in version 9.5 do not work with the 9.0 versions of the Integration Service and the BMC PATROL Agent. For information about the compatibility between BMC ProactiveNet and the BMC PATROL Agent, see BMC ProactiveNet and BMC PATROL Agent compatibility


Central Monitoring Administration Q&A

When trying to register a child server on the central server, we encounter an error using the following command: pw cmadmin registerChildServer -ChildHost=mychildhostname -ChildPort=443 -ChildUser=user -ChildPasswd=password -ChildProtocol=https

The error: An Exception has occurred. Message: Unable to register BMC ProactiveNet Child server as the Child server or web services running on it is unreachable. How do we troubleshoot this?

Verify the configuration is correct on the BPPM servers as central or child (as required) manually as


If the child server is still not visible in the CMA and/or central ops console then please do the following:

1) On both BPPM servers (child and central) enable jserver debug
pw debug on -p jserver
2) Re-run the failing pw cmadmin registerChildServer command
3) Turn off jserver debug
pw debug off -p jserver
4) Zip up and send us the following from both child and central servers:
pw/pronto/logs/ProactiveNet.log (if possible send the whole pw/pronto/logs directory)
5) Please also run the following on the CMA server and send us the output:
sqli "select * from SERVER_DETAILS"


Can you restart a PATROL Agent via the CMA?
PATROL agent restarts from CMA will be achieved by manually selecting an agent and triggering a restart on it using the Reinitialize Agent/Query Agent feature available in CMA 9.5


Is there a way to export CMA policies from one BPPM server to another BPPM server?
Starting in BPPM 9.0 SP1 we added a new feature to import PCM RuleSets, which allows importing existing PCM RuleSets to new Agents. We currently do not have a feature to export CMA policies from one server to another. We do have an Idea posted about this on BMC Communities web site. We urge you to visit the Idea and vote for it if you would like to see it in a future release.


Is it possible to change the option of the view in CMA? For example, can we set the option of physical view or logical view?

The view presented in CMA is a general List view. There is currently, no option available to change the views in the CMA console.  We encourage you to submit an Idea via our BMC Communities to request this feature/functionality.

BMC Ideas is a new way to provide enhancement requests within our growing BMC Communities. We are offering you the opportunity to submit on and vote for your requests for enhancement for your favorite BMC Products!  Check out these short video presentations detailing how to get started with BMC Ideas


Does CMA support instance level threshold management?

CMA does support instance level threshold management. Please refer to the document


How can I make sure that one policy is applied before another if there are different tags?

The BMC PATROL Agent sends a configuration request by passing its tag or tags to Central Monitoring Administration, via the Integration Service. Central Monitoring Administration evaluates policies that match the tags, 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.


The BMC PATROL Agent initiates a configuration request after certain events, such as agent installation, agent restart, or changing a tag on the agent. If no policy matches the tags associated with the agent, the agent does not receive configuration information. The agent does not begin monitoring 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 with matching tags.


Can a PATROL Agent be assigned multiple tags used to apply policies from the CMA?

Yes it is possible to assign multiple tags to a single agent. You would need to have several pconfig policies each with a different tag name to apply multiple polices for same agent.

An example would be as follows:

/AgentSetup/Identification/TagsTAG/<tag name1>

/AgentSetup/Identification/TagsTAG/<tag name2>

/AgentSetup/Identification/TagsTAG/<tag name3>

The value for these variables can be the description of policy/tag


Where can I learn more about CMA?




Newly Published Knowledge Articles - New Content has been added!

KA409225 - In BPPM, a Query Agent can display a list of common PSL commands to be executed. Is it possible to add more PSL commands to this list?

KA409228 – Install of BPPM 9.5 server hangs at step 'Started CMDB Integration...'

KA409289 - After installing BPPM 9.5, LDAP user is unable to login - "BMC-BSW000609E Failed to find user groups for user xxxxxx"

KA408948 - BPPM Reporting 9.0.x does not work with BPPM Server 9.5

KA409568 - Trying to update Threshold Override(s) on multiple devices fails with a System Error

KA409576 - "Unable to establish the database connection for Report User" when installing BPPM 9.5 with Oracle database

KA409573 - BPPM 9.5 installation with Oracle database ended with warnings due to ORA-00942 on sys.props$ table


Popular Knowledge Articles

KA349542 - How to monitor the connectivity status between Patrol Agent and Integration Service (Pproxy Service)? 

KA345591 - BPPM Cell crashes when xact files grows rapidly.   

KA356575 - Usage of the PATROL Proxy command "pproxcli"

KA356684 - Executing SQL Queries against the BPPM Database

KA354768 - Unable to validate user when using LDAP user to login BPPM console



Looking for a previous blog posting? Find them here: BMC TrueSight Support Blogs


The Pulse blogs share the experience of BMC Customer Support on how to understand and best use particular product features.  You can read more about the goals of Pulse Blogs in About the Customer Support Community These blogs are posted in the individual product community, but as many community members have multiple BMC ProactiveNet products, this document provides a summary and links to these posts to make them easier to find.


Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series





Was this helpful?  Are there related topics I missed? Please add comments to share your experience.