OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 28 of 68
Message Transfer Agent servers (MTA):
• # of current incoming sessions
• # of current outgoing sessions
• Send Q length
• # of incoming sessions
• # of messages received
• # of receive recipients
• # of outgoing sessions
• # of messages sent
• # of send recipients
Local Delivery Server (LDS):
• # of messages stored
• # of messages rejected
• # of messages w/NDRs
• # of messages recipients
• # of messages invalid recipient
• # of messages exploded recipients
• # of messages sent
• # of messages Quota violations
• Largest MSG (bytes)
• Max local recipients/MSG
10.1.10 Product Tracing Module
OmniMessaging provides tracing for troubleshooting. You can configure the
trace option to turn on or off selected functional-component trace logs. This
requires special attributes and call Opsol for details.
10.1.11 Queue Files
OmniMessaging makes extensive use of standard HP NonStop Queue files.
The use of queue files enables greater load balancing between server
processes. For example the MTA process creates a queue file entry to trigger
the local delivery of messages by the LDS process. OmniMessaging has the
flexibility to be configured to have many server processes de-queuing records
from a single queue file.