Device engines are components that deliver notifications to different types of devices and, where applicable, receive and process two-way replies and relay them to xMatters.
Each device engine implements a different protocol, and each protocol requires a dedicated device engine. When the device engine is started, the protocol will be passed as a parameter and the device engine runs in that protocol mode.
- Click the Administration tab.
- In the Administration menu, click Nodes & Device Engines.
- In the All Nodes table, click the Device Engines link in the View Components column for the Node you want to modify.
- The Node Components page displays a list of any device engines assigned to that node.
- In the All Components for Node list, do any of the following:
- To modify an existing device engine, click the name of the device engine in the list to view its details.
- To remove a device engine from the list, select the check box next to the device engine you want to remove, and then click Remove Selected.
- To add a new device engine, click the Add New link, and then select the type of device engine you want to add from the drop-down list. Click Continue to specify the details for the new device engine.
You can start or stop a device engine at any time.
To start or stop a device engine:
- On the Nodes & Device Engines page, in the All Nodes table, click the Device Engines link for the node you want to modify.
- In the All Components for Node table, select the check boxes beside the components you want to stop or start.
- You can see the current status of each component in the Activity State column.
- Do one of the following:
- Click Start Selected Components.
- Click Stop Selected Components.
Device engines in xMatters can create separate log files with details of all their transactions and communications.
You can specify the logging settings for each device engine independently, and set the logging details when you add a device engine or modify the details for an existing device engine. The settings explained in the following table are available on the Details page for each device engine:
Generate Separate Log File
Generates a separate log file for the current device engine.
Level of detail required for the log files.
Note that more detailed log levels produce log files that cover a smaller window of time.
Expanded MAPI Logging
To assist in troubleshooting MAPI issues, additional logging has been added for the library file used by MAPI device engine. Any activity that occurs in this library file is written to a log file located at:
The maximum size for this log file is 10MB, after which it is rolled over into a single backup file named mapi_dll_log1.txt.
You can optimize the throughput of your xMatters node deployment by configuring the Concurrent Threads settings of the device engines. By distributing threads based on the amount of notification traffic each protocol receives, you can balance the workload across the device engines that handle the most notifications. For example, if email is the most common notification method, allocate the most threads to your email device engines.
Your Active Licenses control the maximum number of threads allowed.