Configuring BMC ProactiveNet Event Manager Integration

Configure the details for the BMC ProactiveNet Event Manager integration by entering values for the following variables:

Connection settings for BMC ProactiveNet Event Manager integration

PATROL Agent can be configured to be integrated with BMC ProactiveNet Event Manager running both in Stand Alone and High Availability (HA) modes. It is governed through the pconfig variable.

/EventSetup/Configuration/EventCells = { REPLACE = "PrimaryHost/PrimaryPort,SecondaryHost/SecondaryPort"}

For example,

/EventSetup/Configuration/EventCells = { REPLACE = "137.72.224.151/1828"}

/EventSetup/Configuration/EventCells = { REPLACE = "137.72.224.151/1828,137.72.224.231/1828"}

Note

The Secondary host is a computer running the BMC ProactiveNet Event Manager, that is used in a failover scenario.

Key variable

Enter the encryption key used by the BMC ProactiveNet Event Manager using the following variable:

/EventSetup/Configuration/Key = <Key>

For example,

/EventSetup/Configuration/Key = mc

Format variable

You can create or select an event format to be used by setting the value for the following variable:

/EventSetup/Configuration/Format = <Format>

For example,

/EventSetup/Configuration/Format = Biip3

Note

PATROL does not populate a value for the Format variable or forward any events by default.

Forward events through an Integration Service

You can choose to route events via an Integration Service. To route events via an Integration Service, set the /EventSetup/Configuration/ForwardEventsToIS PATROL Agent pconfig variable to Yes.

/EventSetup/Configuration/ForwardEventsToIS = Yes

For example, if /EventSetup/Configuration/ForwardEventsToIS is set to Yes, and BMC ProactiveNet - Primary Cell is set to localhost/1828, then the PATROL Agent sends events to the local Cell of the Integration Service.