OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 20 of 68
8 Multi-Node Architecture Overview
In a multi-node OmniMessaging system; the message store is partitioned into
several HP NonStop™ nodes. The pop/imap/smtp request from outside can
come to a server at any node. The recipient server will make sure that the
message retrieval/storage occurs in the message store on the primary node
that is assigned to the user/submission-address transparent to the client,
whenever the primary node is up.
For high availability, each user/submission-address is assigned one primary
node and two or more backup-nodes. If the primary node is down, the client
should be able to use the OmniMessaging system. New messages can be sent
or stored. The older messages will be inaccessible. Once the primary node is
up all (new and old) messages will be accessible.
A particular node can be brought down by the operator; this is termed as
scheduled outage. A node could go down due other reasons; this is termed as
unscheduled outage. Once a node is down the action taken by the
OmniMessaging system remains same as that in the case of scheduled outage.
8.1 OmniMessaging Multi Node characteristics
1. OmniMessaging Node: NonStop™ node with OmniMessaging software.
2. OmniMessaging users are distributed across the nodes.
3. Multiple OmniMessaging Pathmons can be started on a single
OmniMessaging node.
4. The OmniMessaging Message Store is shared by all the
OmniMessaging Pathmons.
5. The OmniMessaging application components are exact replicas on each
node.
6. Some data is replicated across the OmniMessaging instances. This
information is used to route the user to his home node.