Introduction - Metasys - LIT-12011279 - General System Information - Metasys System - 10.1

Network and IT Guidance Technical Bulletin

Brand
Metasys
Product name
Metasys System
Document type
Technical Bulletin
Document number
LIT-12011279
Version
10.1
Revision date
2019-12-20
Language
English

As implemented in the Metasys system, MSMQ supports trending and Site Management Portal UI navigation tree features. The Site Director queue receives trend data and navigation tree changes from other system devices. When the Site Director is busy, the messages remain in the queue until the Site Director is available to process them. Using MSMQ allows the system to avoid bottlenecks by separating the actions of receiving and processing data. All message queuing functions happen within the server itself; no messages from MSMQ broadcast over the network between the server and other devices.

MSMQ must be installed on all computers where ADS, ADX, OAS, or ODS software is installed. Once installed, do not stop or disable MSMQ. If MSMQ is stopped or disabled, the Site Director does not receive or process messages. Lost trending data may be irrecoverable. The queue fills at a rate determined by your site configuration and system use; for example, trend frequency or number of additions, changes, or deletions made to the navigation tree.

Note: Each Site Director contains all the navigation information for an entire site in a cache. This cache allows the Site Management Portal UI to display quickly without repeated requests to system devices. Updates received through the MSMQ queue keep the information current.
An alarm is generated in the Metasys system when any trend or alarm sample remains in the MSMQ for more than 10 minutes. This alarm usually indicates a problem with the Microsoft SQL Server® or that a remote forwarding destination is offline. See Figure 1 for an example of the Metasys alarm.
Figure 1. MSMQ Alarm

At Release 6.5.5 and later, an alarm is generated in the Metasys system when trend samples remain in the queue after failing two bulk inserts and then fall back to a single insert mode. An alarm is generated for each trend sample that falls back to a single insert mode. XML files are created for each trend object that has a sample that cannot be processed. The XML files are located in the JCIHistorian database.