This is a one-way xMatters integration with ManageEngine.
- This integration was designed with ManageEngine ServiceDesk Plus version 9.4
- A server to configure the xMatters Integration Agent
From within ManageEngine a Custom Trigger will invoke a batch file and pass a Work Order ID. Once this batch file is invoked, the Work Order ID is passed to the Integration Agent via the APClient.bin command execution. From within the Integration Agent the integration service is designed to retrieve the ManageEngine request details through a web service call using the Work Order ID received. The full request details are retrieved from ManageEngine in XML format. The XML is then submitted to the xMatters Integration Builder via a POST web service call. From within the xMatters Integration Builder the XML request is converted to JSON, any existing xMatters events matching the Work Order ID are terminated, a recipient is assigned to the event using the ManageEngine Technician Login Name, and then an xMatters event is created to notify the recipient.
The installation requires Administrative access into ManageEngine to configure the Custom Trigger.
- Create a REST Web Service User in xMatters
- Navigate to the Workflows page and import the ManageEngineWorkflow.zip
- Configure the Form for Web Services and add the REST Web Services role for Sender Permissions
- Navigate to the Integration Builder tab and update the xMatters Endpoint to include the new REST Web Service user
- Select the Inbound Integration link to update the Inbound Integration for Basic Authentication
- Navigate to the ManageEngine Server
- From within the ManageEngine server configure xMatters Integration Agent
- Once configured extract the manageengine.zip to the IAHOME/integrationservices folder
- Open the
IAHOME/integrationservices/configuration.js
in a text editor and insert the needed values - Update the IAConfig.xml to reflect this new integration service
- Navigate to Admin > Custom Triggers
- From within Custom Triggers configure a new Trigger with the following:
- Action Name: xMattersEvent
- Criteria: Per the requirement
- Perform Action:
- Action Type: Execute Script
- Script file to run:
cmd /c xMattersEvent.bat "$WORKORDERID"
- Navigate to
[SDP_HOME]/integration/custom_scripts/
directory and add the xMattersEvent.bat - Open the xMattersEvent.bat and update the file paths and versioning to reflect the location of the Integration Agent.
Create a ManageEngine request matching the criteria of the Custom Trigger condition. If a condition is matched, the action will invoke the process and an event will create in xMatters.
There are four potential points of failure:
-
Custom Trigger executing the xMattersEvent.bat.
- If the xMattersEvent.bat is successfully executed, the batch file will create a xMattersLog.txt in the
[SDP_HOME]/integration/custom_scripts/
directory.
- If the xMattersEvent.bat is successfully executed, the batch file will create a xMattersLog.txt in the
-
xMattersEvent.bat executing the Integration Agent.
- If the xMattersEvent.bat is successfully being invoked, the xMattersLog.txt will display the submission to the Integration Agent. The command to be executed will be echoed to the xMattersLog.txt. The command from the xMattersLog.txt can be pasted into the CMD or executed by right-clicking the batch file. This will require updating the batch file to contain a miscellaneous work order id.
-
Integration Agent communicating with ManageEngine to retrieve the full request details
- This can be observed and resolved be reviewing the Integration Agent logging
-
Integration Agent communicating with the xMatters
- Ensure that the xMatters REST Web Service user has access to the xMatters Endpoint