InterSystems IRIS Data Platform 2019.2  /  Developing Productions

Developing Productions
Defining an Enterprise Message Bank
Previous section           Next section
InterSystems: The power behind what matters   

This chapter describes how to define an optional, specialized kind of production called the Enterprise Message Bank. It includes the following sections:
After you have defined the Enterprise Message Bank, see “Configuring the Enterprise Message Bank”’ in Configuring Productions.
The Enterprise Message Bank is an optional remote archiving facility where you can collect messages, Event Log items, and search table entries from multiple client productions. It consists of the following components:
The following shows a conceptual example:
So that you can conveniently see the messages in the Message Bank, InterSystems IRIS™ provides the following additional options:
The following shows an example:
Defining the Message Bank Server
To define the Message Bank server, do the following on the server machine, in an interoperability-enabled namespace:
  1. Create a subclass of the Ens.Enterprise.MsgBank.Production abstract class.
  2. Copy its ProductionDefinition XData block into your class.
  3. Compile your new class.
The following shows an example:
Class MyMessageBank Extends Ens.Enterprise.MsgBank.Production

XData ProductionDefinition
<Production Name="Ens.Enterprise.MsgBank.Production" TestingEnabled="false" LogGeneralTraceEvents="false">
  <Description>Production for receiving and collating message bank submissions from one or more client 
   interoperability-enabled namespaces and for maintaining a local repository of production status information about each
   client namespace, for display on the Enterprise Monitor page. Open the the Monitor page on the same
   machine that that is hosting this Production.</Description>
  <Setting Target="Production" Name="ShutdownTimeout">120</Setting>
  <Setting Target="Production" Name="UpdateTimeout">10</Setting>
  <Item Name="MonitorService" Category="" ClassName="Ens.Enterprise.MonitorService" PoolSize="1"
        Enabled="true" Foreground="false" InactivityTimeout="0" Comment="Populates global 
        ^IRIS.Temp.Ens.EntMonitorStatus by polling namespaces from Systems List every CallInterval seconds"
        LogTraceEvents="false" Schedule="">
    <Setting Target="Host" Name="AlertGracePeriod">0</Setting>
    <Setting Target="Host" Name="AlertOnError">0</Setting>
    <Setting Target="Host" Name="ArchiveIO">0</Setting>
    <Setting Target="Adapter" Name="CallInterval">10</Setting>
  <Item Name="MsgBankService" Category="" ClassName="Ens.Enterprise.MsgBank.TCPService" PoolSize="100"
        Enabled="true" Foreground="false" InactivityTimeout="20" Comment="" LogTraceEvents="true" Schedule="">
    <Setting Target="Host" Name="AlertGracePeriod">0</Setting>
    <Setting Target="Host" Name="AlertOnError">0</Setting>
    <Setting Target="Host" Name="ArchiveIO">0</Setting>
    <Setting Target="Adapter" Name="Endian">Big</Setting>
    <Setting Target="Adapter" Name="UseFileStream">0</Setting>
    <Setting Target="Adapter" Name="JobPerConnection">1</Setting>
    <Setting Target="Adapter" Name="AllowedIPAddresses"></Setting>
    <Setting Target="Adapter" Name="QSize">100</Setting>
    <Setting Target="Adapter" Name="CallInterval">5</Setting>
    <Setting Target="Adapter" Name="Port">9192</Setting>
    <Setting Target="Adapter" Name="StayConnected">-1</Setting>
    <Setting Target="Adapter" Name="ReadTimeout">10</Setting>
    <Setting Target="Adapter" Name="SSLConfig"></Setting>

This production has the following services:
This production receives this data and maintains a local repository.
For testing purposes, you can put the Message Bank production on the same machine and instance as your regular productions, but it must be in a separate namespace from any production you plan to monitor.
Adding a Message Bank Helper Class
By default, the message bodies are not indexed and cannot be searched. You can add a helper class to implement the search capability in the Message Bank. To do so:
  1. Create a subclass of Ens.Enterprise.MsgBank.BankHelperClass and implement its OnBankMsg() method. See the InterSystems Class Reference for details on the method.
    The OnBankMsg() method specifies any custom processing to perform when inbound messages include a message body.
    In your implementation of this method, you should decide whether to handle messages in process (and possibly reduce the input capacity), or whether the method should asynchronously forward the messages to a secondary process to balance the work more effectively.
  2. In the Message Bank production, select the Ens.Enterprise.MsgBank.TCPService business service and specify the Bank Helper Class setting. For the value, use the name of your helper class.
Notes about the Message Bank
Note the following important characteristics of the Message Bank:

Previous section           Next section
Send us comments on this page
View this book as PDF   |  Download all PDFs
Copyright © 1997-2019 InterSystems Corporation, Cambridge, MA
Content Date/Time: 2019-10-17 05:24:18