Problem is if you rely on the features of auto thresholds, then things that are definite faults can be delayed, so for things such as Windows events, log file monitoring, process presence, these are best forwarded directly to the cell. Things that are more "transient" such as CPU percent busy best done via BPPM I understand that there was a plan to integrate BII4P with the connectors not sure if that has happened.

If you want to send the PATROL events directly to the BPPM cell then you need to have Bii4p/mcxp

On the other hand you can use the PATROL Adapter on the BPPM side to collect the data from the PATROL environment, and configure threshold on the monitered instance. When the threshold is breached you will get an ALARM on the BPPM.

Also you cannot have BEM and BPPM installed on the same machine as there will be conflict in certain port and environment variables. But if you just want some additional cell in your BBPM environment then you can create them using the mcrtcell command.

In version 9.0 of the PATROL agent we introduced a new capability that allows you to forward and event directly to a BEM/BPPM cell from the PATROL agent without requiring BiiP3 or BiiP7. This will be the new best practices for event integration for PATROL agents 9.0 and later, for more information please see the release notes or the PATROL agent reference manual.

This indeed is a good enhancement to Service Assurance stack ! Please share scalability docs, if available, so that we can plan for number of cells needed to handle a certain number of events from certain number of PatrolAgents. Till this enhancement, cell's scalability used to be mainly a function of number of events per unit time. However with this new feature, I am sure it won't be just #of event per unit time but also number of concurrent connections a cell can handle. We will appreciate if you could throw some light in this regards.

My thoughts on your question Rahul:-

If you decide go with the latest PatrolAgent, you will certainly not need Bii4P. However, you will have to upgrade all your PatrolAgent to the latest version ( Mattias, please correct me if I am wrong here ).

If you just want threshold related events, you need to add PatrolAgents into BPPM using Patrol Integration Service. (This fairly is a straight forward job). With this you will get 'metric data' collected by KMs on your PatrolAgent into BPPM. You will certainly use BPPM's thresholding capabilities by configuring thresholds on your newly created BPPM server. You don't strictly need Bii4P if you are pulling all your metric data in BPPM as Intelligent Events will be generated in BPPM based on thresholds you define. However, you may need Bii4 if (a) you have some devices, instances, etc left out of BPPM. (b) you need to subscribe for non-threshold related events that are generated by some KMs (using PSL event_trigger() function)

Events generated by the PATROL agent running on ISN can be "forwarded" to the cell resided on the same ISN.

In thoery, you can use this PATROL agent to do remote monitoring on VMs. But since VM monitoring is resource intensive, it is better not to let PATROL agent compete resources with other important components on ISN such as integration service and cell. In a large environment, I would even suggest to split integration service and cell to different servers for both performance and failover purpose.

Yes. The integration between PATROL agent v9.x and BEM 7.4 does not need bii4P and is fully supported. That was the exactly same configuration I had at my last client. All you need is to have the following variables set in your pconfig: