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 AlarmPoint.
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.
You can start or stop a Device Engine at any time.
Device Engines in AlarmPoint 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. |
To assist in troubleshooting MAPI issues, additional logging has been added for the library file used by MAPI Device Engines. Any activity that occurs in alarmpoint_mapi.dll is written to a log file located at:
<AlarmPoint>/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.
You can optimize the throughput of your AlarmPoint 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.
Note that if you want to increase the number of concurrent threads to more than 40, you must edit the configuration file, as described in the following section.
| Note: | Your Active Licenses control the maximum number of threads allowed. |