Use the BMC Software Event Manager to integrate to BMC ProctiveNet Performance Management (BPPM), formerly SMC Event Manager.
To integrate Event Manager:
Create a BMC Event Manager adapter.
For general instructions on creating adapters, see Section 2.1, Creating an Adapter.
Accept the defaults for the adapter properties and click Create.
In general, it is acceptable to use these defaults. For more information about adapter properties, see Section A.4, BMC Software Event ManagerSection A.4, BMC Software Event Manager.
For detailed descriptions of the adapter properties, see Section A.4, BMC Software Event Manager.
Start the adapter.
Do the following to configure the adapter:
Right-click the adapter instance under Elements, and select Properties.
In Properties, open Event Manager Administration.
In the General tab, specify the following:
Web Services Host URL: Address of the IIWS server. Specify the path portion of the URL if it is different from /imws/services/ImpactManager. For example: http://164.99.17.72:9003 or http://164.99.17.72:9003/imws/services/ImpactManager.
Polling Filter: Name of a filter defined on the IIWS server that determines the alarms received after initial discovery. Once the Web Services Host URL is populated, the Browse feature (magnifying glass icon) is available to load polling filters from the IIWS server.
Polling Interval (seconds): How often the adapter polls for events after initial discovery.
BAROC Query: The query in BAROC syntax (a BMC proprietary syntax) that identifies the events loaded during initial discovery.
Replace ***ADD IIWS CELL NAME HERE*** with the cell name of the IIWS server (usually iiwsgatewayserver). The default query retrieves all non-closed events that normally propagate to the IIWS server. If the string {EVENT-CLASS} is included in the query, the query is executed once for each valued specified in {EVENT-CLASS} Substitution Values.
{EVENT-CLASS} Substitution Values: List of event classes to discover. Event classes in the BPPM environment are hierarchical and EVENT is typically the root of that hierarchy. All sub-classes of a requested event class are included, so there is no need to specify another event class is the root type is specified. Add, edit or delete substitution values.
In the Cells tab, add cell configurations to be discovered. The adapter only receives updates from these cells after initial discovery if they are configured to propagate events to the IIWS server. Propagation rules are configured in the BPPM environment. Click the Add icon to add the cell configurations to be discovered, then specify:
Cell Name: Name of the cell in the BPPM environment.
Passive discovery: When selected, this cell is not queried during initial discovery in adapter start-up. If the adapter receives an event from the cell during it's polling process, then normal discovery of the cell is initiated.
Use Custom Delivery Query: When selected, the enclosed BAROC Query and {EVEN-CLASS} Substitution Values settings are used instead of the defaults specified in the General tab.
Use Custom Credentials: When selected, the Username and Password settings are used instead of the defaults specified in the Advanced tab.
(Optional) If necessary, use settings in the Advanced tab to further configure the adapter:
Max Events Requested Per Fetch: Maximum number of the events to retrieve per SOAP request. A larger value here can improve performance but may require more memory in the IIWS server process.
Communications Timeout (seconds): Number of seconds to wait for a response from the IIWS server.
Max Retry Count (use 0 for unlimited): Number of times to retry after a communications failure.
Retry Interval (seconds): Number of seconds to wait between each retry.
Default Cell Credentials: Username and Password used to communicate with cells (not typically required).