You can install multiple ProactiveNet Agents on the same Windows box.
However, I don't believe the installation will create three separate Integration
services. You can try it but unless you get three integration service services,
your efforts are in vain. You might open a case with BMC Technical Support
to verify this.
We need 3 BPMM agents because I have 240 Patrol Agents and BMC ProactiveNet best practices tell us that we must configure 80 Patrol agentes approximately for each BPPM agent and I want to know if it is possible that the three BPPM can be installed on a same server and how to configure the Patrol Agent to connect to each BPPM agent installed on a single server.
For the answers sent to me, a solution is to install the three agents on different servers and other solution is to install one BPPM agent on a server and create two additional profiles to "SA_DEFAULT" to distribute the 240 Patrol agents in these three profiles.
I do not know if the last solution is consistent with best practices ProactiveNet.
Which document refers to 80 days???
The answer is below - as you can do you what you want.
So assume you have three agents added and Green in the BPPM admin UI.
You could create 3xAdapters manually and bind these to one BPPM Proxy.
Just create the adapters and don't import any monitors.
From Adapters Import Monitor types add adapter >>> BMC PATROL
On this screen select source BPPM Agent and source BPPM Proxy
You have to add one Agent into the Proxy before going to the next screen (this you can delete and the end of process) using Configure Integration Services
After adding one server to the system click NEXT and then CLOSE
The new adapter should appear. repeat
Adapter1 - BPPM Agent 3181 and bind to ProxyAgent1
Adapter2 - BPPM Agent 3182 and bind to ProxyAgent1
Adapter3 - BPPM Agent 3183 and bind to ProxyAgent1
Convert a manually created adapter instance into an automated workflowenabled
instance, run the following command:
pw adapter -type patrol -enable_motype_sync <instance_name>
where <instance_name> is the name of the manually created adapter instance.
pw adapter -type patrol -enable_motype_sync Adapter1 (repeat for 2 and 3)
Now using the intgreation variable - add ONE agent to BPPM Agent 3181 - it should import and build correctly
Repeat for Adapter2 (3182) and Adapter3(3183)
Once you have all the adpaters built and collecting then add the other agents to - 79 to each one.
I still think you can do this with one BPPM agent and one BPPM Proxy and you therefore if you do this, the Adapter etc will be created automatically assuming you have BPM agents 3.8 and above...
Thanks for your answer, but I don't understand wery well. I have did the following:
1. Installed a PNET remote agent pnet_agent_01
2. Added the pnet agent pnet_agent_01 to PNET server
3. In Adapters=>BMC Patrol appeared pnet_agent_01.
4.- Import and ADD BMC PATROL
5. In source agent I have typed: pnet_agent_01. Then I entered the admin key. Click on Next
6. Selected Configure Integration Service
7. The SA_DEFAULT profile has set 3183 default port.
8.- I have created two additonal profiles SA_TEST01 and SA_TEST02 with 3184 and 3185 ports respectively
9. Using Patrol Configuration management, I have created three rulsets with Integration service variable: tcp:hostname_pnet_agent_01:3183, tcp:hostname_pnet_agent_01:3184, tcp:hostname_pnet_agent_01:3185
10. I have applied these rulsets to three patrol agent groups respectively
11. After one day, the SA_DEFAULT profile shows the first group of patrol agents, the SA_TEST01 profile shows the second group of patrol agents and SA_TEST02 profile has the las group patrol agents.
I'm looking for some best practice here. What benefit is there in running 3 (multiple) BPPM agents when you can only have one IS/proxy process.
I think a one to one mapping sounds common sense.
There is talk of multiple _SAs per Adapter. Is that the way to add scalability.
I have managed to create multiple Adapter instances bound to the one BPPM/IS pairing.
Is the import a one off ?
I'd prefer to control what gets imported.
Are the monitors that are imported bound to the IS that imported them ? i.e can I have a test IS with a test agent pointing at it and import just CPU and MEMORY. Once the monitors are loaded its the production IS that takes in these metrics.