Device engines

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.

Enable device engine logging

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:

Detail

Description

Generate Separate Log File

Generates a separate log file for the current device engine.

Log Level

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:

<XMHOME>/logs/mapi_dll_log.txt
 

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.

Configure concurrent threads

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.