-
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 it reparses the serialized document into an object, and receives and stores the search table entries from the contributing production as well.
To enable searching by custom schema properties in the Message Bank, make sure to place the custom schema definition 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. For details, see Configuring the Enterprise Message Bank’.
-
The Message Bank mechanisms do not delete the messages from the originating production; you should handle that function with a separate purge process.
-
It is possible to replay messages from the Message Bank back into the originating production or another client production. See Using the Enterprise Message Bank’ in Monitoring Productions.
