Remote notifications - Metasys - LIT-1201645 - MS-ADSxxx-x - MS-ADXxxx-x - Server - ADS Server - ADX Server

Remote notifications - Metasys - LIT-1201645 - MS-ADSxxx-x - MS-ADXxxx-x - Server - ADS Server - ADX Server - 12.0

ADS/ADX Commissioning Guide

Product

Building Automation Systems > Application Servers > ADX Server

Building Automation Systems > Databases and Data Servers > ADS Server

Document type

Commissioning Guide

Document number

LIT-1201645

Version

12.0

Revision date

2022-09-22

Product status

Active

What is the remote notifications feature?

The Remote Notifications feature in the Metasys UI replaces the Server Destination Delivery Agents (DDAs) in the Site Management Portal (SMP). With the Remote Notifications feature you can configure the routing and filtering of event and audit messages directly in the Metasys UI for each server (ADS, ADX, OAS) or engine, without installing software on client machines.

The Remote Notifications feature is available on both Metasys UI and Johnson Controls System Configuration Tool (JCT).

Note: Metasys UI is not available for sites using Metasys for Validated Environments, so MVE sites cannot use Remote Notifications. DDAs are still available through the Site Management Portal for MVE systems.

Who can access the remote notifications feature?

Any user can access the Remote Notifications feature, but the information within the feature is limited based on a user's permissions. To view the notifications that are configured for a particular Server or Engine, a user needs the View permission for the authorization category of that Server or Engine. To change any notifications for a particular Server or Engine, a user needs the Modify Items permission for the authorization category of that Server or Engine. feature.

How do I access the remote notifications feature?

In the Metasys UI, open the User menu.
Click Feature Management.
Click Remote Notifications.

Which destination types are supported on servers? Which destination types are supported on engines?

For a server you can use the following destination types to configure the routing and filtering of event and audit messages:

Email: event filter only
Simple Network Management Protocol (SNMP): event filter only
Syslog: event filter and audit filter
Printer: event filter only

For each Engine you can use the following destination types to configure the routing and filtering of event and audit messages:

Email: event filter only
Simple Network Management Protocol (SNMP): event filter only
Syslog: event filter and audit filter

The following table describes the available destination types in more detail:

Table 1. Destination types
Destination type	Description
Email	You can configure email addresses as destinations for event messages. The Email destination type supports standard SMTP.
Simple Network Management Protocol (SNMP)	You can configure a SNMP Trap as a destination for event messages. The SNMP destination type supports SNMP Versions 1, 2C, and 3. Note: Metasys does not currently support encryption or authentication when SNMP is used.
Syslog	You can configure a Syslog destination that forwards all system events and audits to your Syslog server. The Metasys system provides the optional capability of sending its configured audit log entries and alarm notifications to an external, industry-standard Syslog server, conforming to Internet published RFC 3164. The Syslog option provides positive indication of each field possible in the Metasys event and audit entries, replacing any blank field with the single character dash (-). Individual fields of each Metasys message are sent to the Syslog server separated by the vertical bar symbol (\|), ensuring the integrity of all data sent to the Syslog server. After the Syslog DDA is configured, all messages sent to the local ADS Repository are also sent immediately to the configured Syslog server. You can apply forensic analysis on the consolidation of all electronic audit and event information at the Syslog server.
Printer	On the server platform, you can define any printer supported by Windows software as a destination for event messages, and a single DDA can print alarms on multiple printers. Printers connected to the server by parallel port or USB are supported, as well as IP-based network printers (if printers are set up with an IP address). This platform does not support Novell NetWare printers. You can configure the Printer DDA for single line printing for a tractor feed printer (also known as tractor feed printing, line printing, and dot matrix printer support). To set up a printer for single line printing for a tractor feed printer (no form feed/tractor printing mode), set the Line Out attribute to 0 when you create a notification. By setting this attribute to 0, when an alarm is sent to the tractor feed printer, it prints the alarm text and then advances a single line, thus waiting to print the next alarm. Note: When using a tractor feed printer (without any form feeds), the Timeout, Printing Priority Threshold, Orientation, Font Face, and Font Size attributes are not used and any values set for them are ignored. You can set the Orientation, Font Face, Font Size, and line wrapping at the printer itself. Tractor feed printing is only intended for tractor feed printers. You may encounter abnormal behavior if you set the Line Out attribute to 0 for other type of printers, such as deskjet and laserjet printers.

Is the remote notifications feature supported on all devices?

The Remote Notifications feature is supported on desktop platforms only. It is currently not supported on tablets or smartphones.