Archived - How do I forward events and incidents from ENA to the BMC TrueSight Operations Management Events integration?

To set up event forwarding

To set up incident forwarding

To configure the incident forwarding callback URL

To access event and incident details on the originating Entuity server

To amend Entuity server URL details

Events are forwarded to BMC TrueSight Operations Management via the ENA Event Management System (EMS). By default, the event URL will include the details of the Entuity server that originally raised the event.

To set up event forwarding:

You can forward events to the BMC TrueSight Operations Management Events integration by setting up an Event Rule:

1. In the ENA UI, click Main Menu and then click Administration.
2. Click Event Administration. Click the Rules tab.
3. Ensure the Post Storage option is selected in the left pane. Click Add Rule... at the bottom of the browser. This will open the Add Rule window.
4. Ensure the Type field is set to Generic, and that the enabled box is ticked.
5. Enter appropriate name and description in the Name and Description fields.
6. Leave the Condition field as None.
7. In Action Steps, click Add and set the Type to Send to BMC Event Manager. Select the cname parameter and click Set, followed by OK.
8. Click OK again to save and add the rule. The rule will forward all events to the TrueSight Operations Management server and cell defined through configure. You can Edit the rule filter to control the events forwarded and specify alternative receiving TrueSight Operations Management servers in the section described in Step 7 above. To do so, enter the connection name within the single quote marks as they are defined in bem-connections.cfg. Please see this article for further help and information on configuring additional servers and cells for incident and event forwarding.

To set up incident forwarding:

You can forward incidents to the BMC TrueSight Operations Management Events integration by setting up an Event Trigger. You can configure a global trigger so all incidents are forwarded to the server, or triggers against individual incidents to forward only those incidents.

1. In the ENA UI, click Main Menu and then click Administration.
2. Click Event Administration. Click the Incidents tab.
3. Click Edit Global Triggers at the bottom of the browser. This will open the Edit Global Triggers window. Click Add... to open the Create Trigger window.
4. Enter name and description in the Name and Description fields.
5. To ensure all incidents raised against the same source are sent to TrueSight, ensure the On Transition To field is set to "Any Change".
6. In the Condition dropdown field, select "All tests must succeed".
7. Click Add to add a conditional test. Set Type to "Incident Severity Test". Set Expression to the severity level you wish to forward, and click OK.
8. In Action Steps, click Add and set Type to "Send to BMC Event Manager". Select the cname parameter and click Set, followed by OK.
9. Click OK again to save and add the trigger. The rule will forward all incidents to the TrueSight Operations Management server and cell defined through configure. You can Edit the trigger to control the incidents forwarded and specify alternative receiving TrueSight Operations Management servers in the section described in Step 8 above. To do so, enter the connection name within the single quote marks as they are defined in bem-connections.cfg. Please see this article for further help and information on configuring additional servers and cells for incident and event forwarding.

To configure the incident forwarding callback URL:

1. You will need to change the callback URL to allow users to display event source component details in the Presentation Server, rather than the standard ENA user interface. To do this, add the following parameters to the [bem] section of entuity_home\etc\entuity.cfg:
   

   ps_server_name=truesight_presentation_server_name
   ps_server_web_port=443
   ps_redirect_enabled=true

   ps_server_name is the name of the TrueSight Operations Management Presentation Server where the Entuity Network Component is installed. ps_server_web_port is the port number of the TrueSight server.
2. After the parameters have been added to the entuity.cfg file, stop the Entuity server: entuity_home\bin\stopeye (entuity_home is the installation directory of ENA)
3. Run entuity_home\install\configure.exe
4. After the configuration process has finished, start the Entuity server: entuity_home\bin\starteye

To access event and incident details on the originating Entuity server:

From the TrueSight Operations Management server, you can access event and incident details on the originating Entuity server through the object URL. To do this, the original URL supplied by the Entuity server must include the user credentials that would allow you access.

To set up user credentials, navigate to the bem section of entuity_home\etc\entuity.cfg:

[bem]
connection_username=admin
connection_view=All Objects

Where:

• connection_username is the ENA user account used to access the Entuity server from the associated event or incident URL.
• connection_view is the ENA View used to access the Entuity server from the associated event or incident URL available.

The conditions added to rules and triggers determine which events and incidents are forwarded to the TrueSight Operations Management server. For the associated URL to succeed, the connection_username and connection_view settings must allow access to the data associated with those events and incidents.

To amend Entuity server URL details:

By default, the event/incident URL provided by the Entuity server that forwards the event will include the details of the Entuity server that originally raised and forwarded it. However, you can amend the Entuity server URL details so that you can view the raised even through the Entuity consolidation server instead of the originating Entuity server.

To amend the Entuity server URL details, navigate to the bem section of entuity_home\etc\entuity.cfg:

[bem]
consolidation_server_name=entlonppvm01
consolidation_server_web_port=81

Where:

• consolidation_server_name is the resolved name of the Entuity consolidation server that you want to use to access the event or incident data. This replaces the name of the Entuity server that originally raised and forwarded the event/incident.
• consolidation_server_web_port is the port number of the Entuity consolidation server that you want to use to access the event or incident data. By default, it is port 80.

If the Entuity server that is forwarding events/incidents is using a non-default web port, y ou can also use consolidation_server_name and consolidation_server_web_port to amend the URL to use the non-default port. You must set both parameters even when the Entuity server remains the same.