OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 30 of 68
10.1.13 Multi Node Directory Server
The Directory server runs as a TSMP server class. The input is an email
address (submission address) or User Name and the output is the users home
node and backup node instances. A Programmatic Interface is provided for
custom applications attempting to use the Directory Server.
Directory Server
Static Data
AMS
Populate User Info
To remote AMS
Query User Info
Omni Client
Add / Delete / Modify
user
Add Node
POP/IMAP/SMTP
(2) Get users current active node
(1) User Request over TCP/IP
is user local to
this node
Remote POP/
IMAP/SMTP
Dynamic Data
10.1.14 OpenSwitch
OpenSwitch monitors the nodes in the OmniMessaging multi node environment.
The OpenSwitch considers a node down if loses all its connections to the
OpenSwitch on the other node. OpenSwitch uses Expand and $receive for all
its communications.
The POP, IMAP, SMTP servers register with the OpenSwitch on the local node.
The POP, IMAP, SMTP servers wishing to communicate with a remote node will
query the OpenSwitch for their counterparts process names on the other nodes.
The OpenSwitch will return the home nodes process name if the home node is