The information in this article is the intellectual property of xMatters and is intended only for use with xMatters products by xMatters customers and their employees. Further, this intellectual property is proprietary and must not be reused or resold.
This article provides installation, configuration, and implementation details for the xMatters On-Demand for HP BSM (with OMi) integration. The integration focuses specifically on automating notification when HP OMi detects something that requires attention.
When HP OMi detects something that requires attention, xMatters places phone calls, sends pages, messages, or emails to the appropriate personnel, vendors or customers.
xMatters is also persistent, escalating through multiple devices and personnel until someone accepts responsibility or resolves the problem. Once contacted, xMatters gives the notified person instant two-way communication with HP BSM Operations Manager i software. Responses are executed immediately on HP OMi, enabling remote resolution of the event.
This integration supports event notifications (from HP OMi to xMatters) through the use of web service calls via the xMatters integration agent. It also supports inbound actions (from xMatters to HP OMi) to update events remotely.
The Value: This integration is meant to accelerate the notification of key personnel for important events to help reduce mean-time-to-resolution (MTTR) for the most business-impacting issues. Information about the event (such as failure) will be presented to the event resolver and decisions can be made in real-time.
In addition, the ability to take simple actions on the event from any device gives the event resolver a quick way to deal with many issues and communicate to other team members the current state of the event.
During the process, every notification, response, and action is logged in xMatters. In addition, xMatters automatically annotates the original event with status information.
Integration created and supplied by Lei Liu.
Before configuring anything in HP OMi, you'll need to configure xMatters.
The first step in configuring xMatters is to create a REST API user to authenticate REST web service calls when injecting events.
This user needs to be able to work with events, but not update administrative settings. The best way to create a user for this integration is to have a dedicated "REST Web Service User" role that includes the permissions and capabilities. If this role does not exist in your deployment, you will need to create it, or ask your xMatters Client Success Manager to create it for you. (For detailed procedures about creating the role, see Authentication and Permissions.)
In the following example, this role is named "REST Web Service User".
To create a REST API user:
- Log in to the target xMatters system.
- On the Users tab, click the Add New User icon.
- Enter the appropriate information for your new user.
- Assign the user to the REST Web Service User role.
- Click Save.
- On the next page, set the web login ID and password.
Notification Targets are the Assigned Group or Assignee value set for each monitoring event within HP OMi.using the EPIC feature.
The next step is to import the HP OMi communication plan.
To import the HP OMi communication plan:
- Download the attached .zip or tar.gz file to your system, and then extract the contents.
- In the target xMatters system, on the Developer tab, click Import Plan.
- Click Choose File, and then locate the following file within the extracted archive:
- Click Import Plan.
- Once the communication plan is imported, click Plan Disabled to enable the communication plan.
- In the Edit drop-down list, select Forms.
- For the HPOMi form, in the Not Deployed drop-down list, click Create Event Web Service.
- After you create the web service, the drop-down list label will change to Web Service Only.
- In the Web Service Only drop-down list, click Permissions.
- Enter the REST API user you created above, and then click Save Changes.
- Repeat step 7 through 9 for the HPOMi-fyi form as well.
To enable REST/JSON event injection into the imported communication plan, you need to create an integration service on the "applications" event domain.
To create an integration service:
- Log in to the target xMatters system.
- On the Developer tab, click Event Domains.
- On the Event Domains page, click applications.
- At the bottom of the details page, in the Integration Services section, click Add New.
- Enter the following information:
- Name: hpomi20
- Description: Integration service for HP OMi integration
To leverage the latest REST/JSON development from xMatters, install the integration agent version 5.1.4. (There is a known issue with the integration agent version 5.1.5, as explained here.)
To install the integration agent:
- Copy the folder containing the integration components into the integration agent; this process is similar to patching the application, where instead of copying files and folders one by one, you copy the contents of a single folder directly into the integration agent folder (<IAHOME>). The folder structure is identical to the existing integration agent installation, so copying the folder's contents automatically installs the required files to their appropriate locations. Copying these files will not overwrite any existing integrations.
- Modify the integration agent's IAConfig.xml file to include the paths for the new integration service.
- Modify the variables in the omi-config.js file associated with the integration services.
Now that you've configured xMatters and installed the integration agent, it's time to configure HP OMi.
Configuring a connected server allows notification responses to update events appropriately.
To create a connected server:
- In the HP OMi interface, on the Administration tab, in the Operations Management area, click Connected Servers.
- Click the New Item icon.
- HP OMi displays the Create New Server Connection dialog box.
- These values are not validated by the integration; you can use any settings provided they conform to the minimum requirements of HP OMi.
Each deployment of the integration requires a unique event forwarding rule, specific to each deployment, based on the organization's assessment of which events are appropriate to be sent to xMatters. An organization can choose to have more than one event forwarding rule, but for the integration to function correctly, an event forwarding rule must exist and be associated with the xMatters connected server.
The following steps provide an example of how to create a forwarding rule; the rule required for your integration will not be precisely the same.
To create an event forwarding rule:
- In the HP OMi interface, click the Tune Operations Management tab drop-down list, and then click Forwarding Rules.
- On the Event Forwarding Rules page, click the New Item icon.
- HP OMi displays the Create New Event Forwarding Rule dialog box.
- HP OMi returns you to the Select an Event Filter dialog box, with the xMatters Minor Severity Filter selected.
You can use the packaged sendEvent.bat script to inject a test event into HP OMi.
On Windows, this script is located at:
For information on how to use the sendEvent.bat script, please refer to the HP OMi documentation.
To test the integration:
- Create an event via the sendEvent.bat script.
- If your Assigned Group value corresponds with an active group in xMatters, you should see the notifications in the Reports tab.
- Email notifications should resemble the following:
- Respond to the notification with the Work On option to take ownership of this troubleshooting assignment; there will be no further escalation within the test group.
- You can also choose to respond with Resolve if the underline issue is already addressed.
- Log in to HP OMi Web Console.
- On the Event Perspective tab, under Event Browser, locate the event used for testing notifications.
- The Life Cycle State has changed to In Progress, indicating that the event was acknowledged from xMatters.
- An annotation indicates that the event was changed to "In Progress" by responder. For In Progress, Resolved, and Closed responses, the Assigned User is set to the person who responded.