Virtual Device Engines enable xMatters to send notifications to and receive responses from the virtual Devices included with xMatters. These Devices are intended for demonstration and testing purposes only.
|
Detail |
Description |
|
Name |
Name used to identify this Device Engine. |
|
Description |
Brief description of this Device Engine (optional). |
|
Notification Polling |
How often (in seconds) the Device Engine polls the notification node for new alerts. Must be a whole number greater than or equal to 10 and less than or equal to 300. |
|
Concurrent Threads |
Number of requests or tasks that this Device Engine can run at the same time. Your Active Licenses control the maximum number of available threads. |
|
Logging |
For an explanation of Device Engine logging, see Enabling Device Engine logging. |
|
Incoming Port |
The port for the Virtual Device Engine to receive incoming requests. |
|
Email Notification Key |
String included in the body of the notification that identifies the original alert or notification to which the User is responding. Normally this key is enclosed with delimiting characters; e.g., the default value, <%Notification Key%>. If the delimiting character sequence is not guaranteed to be unique, the Device Engine may make an incorrect match, causing an exception and response failure. If no delimiters are present, the first word of the response will be used as the notification key. If the delimiters occur more than once in the body of the notification, the first instance is used as the notification key. |
|
Email Response Key |
String included in the body of the notification that identifies the beginning of the response portion of the User’s return message. |
|
Email Default Message |
Default notification message displayed to the recipient. |
|
Email Choice Message |
Portion of the notification message that defines User options. |
|
Email Response Message |
Portion of notification message describing response instructions. |
|
Text Phone Notification Key |
String included in the body of the notification that identifies the original alert or notification to which the User is responding. Normally this key is enclosed with delimiting characters; e.g., the default value, <%Notification Key%>. If the delimiting character sequence is not guaranteed to be unique, the Device Engine may make an incorrect match, causing an exception and response failure. If no delimiters are present, the first word of the response will be used as the notification key. If the delimiters occur more than once in the body of the notification, the first instance is used as the notification key. |
|
Text Phone Response Key |
String included in the body of the notification that identifies the beginning of the response portion of the User’s return message. |
|
Text Phone Default Message |
Default notification message displayed to the recipient. |
|
Text Phone Choice Message |
Portion of the notification message that defines User options. |
|
Text Phone Response Message |
Portion of notification message describing response instructions. |