Managing Ensemble Productions - InterSystems Documentation

Maintenance
-1
10
}
}
This is the production for receiving and collating message bank submissions from one or more client Ensemble
namespaces and for maintaining a local repository of production status information about each client namespace. You
can view the gathered information on the Enterprise Monitor page on the same machine that is hosting this production.
For testing purposes, you can put the message bank production on the same machine and instance as your regular
productions, but it should be in a separate namespace from any production you plan to monitor. The Message Bank
production uses the following services:
• Ens.Enterprise.MsgBank.TCPService — to accept inbound data from the client productions
• Ens.Enterprise.MonitorService — to gather status of client productions
2. Message Clients — In each regular production for which you want to collect messages, add a new business operation
using the Ens.Enterprise.MsgBankOperation class. This operation and its configuration control archiving of events via
TCP to a near real-time Ensemble server running the Message Bank production. See Adding a Message Bank Business
Operation for the detailed procedure.
3. Navigate to the [Ensemble] > [Maintenance] > [Enterprise Message Bank] page to view the collected messages in the
message bank. The first time you enter the Enterprise Message Bank page from the Maintenance menu, it requires you
to enter the following information about the Message Bank:
• Enterprise Message Bank Webserver IP Address
• Enterprise Message Bank Webserver IP Port number
• Enterprise Message Bank Webserver execution Namespace
• Use SSL to connect to the Enterprise Message Bank Webserver
Ensemble caches the information and does not display it again unless you clear this cache by performing a Kill on the
^Ens.MsgBank global.
4. Once you enter the proper information, you see the Ensemble Enterprise Monitor: Client Systems List page. From here
you can click Message Bank Browser to display a list of archived messages.
Important characteristics of the Message Bank:
• The Message Bank has no synchronization dependencies for message body classes with the contributing productions;
therefore, it receives a serialized form of each message. For virtual document message bodies (HL7, for example) it
reparses the serialized document into an object, and receives and stores the search table entries from the contributing
production as well. You can perform almost the same search for HL7 messages as on the original machine; however,
the same is not true for other types of message bodies.
To search by HL7 custom schema properties in the Message Bank, the custom schema definition must be in the Message
Bank production namespace.
• For uniqueness, the Message Bank production prepends the numeric identifier of client productions to the message
IDs.
• The Message Bank page also serves as a portal for viewing the state of multiple client productions and for invoking a
resend service on them. For these extra features to work the Message Bank needs to know the web addresses of the
client productions.
112 Managing Ensemble Productions