OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 29 of 68
10.1.12 LDAP3 interface / Directory Server (optional)
The Directory Server provides user information for local OmniMessaging
components via the Server class send APIs. Applications on other platforms
desiring access to the OmniMessaging User profile can use a socket interface
or an LDAP3 interface. The Directory Server runs as a NonStop™ TSMP
Server class for persistence and scalability.
The figure below describes the flow for the directory server.
Directory Server
Omni User Profile
Home Location
Service Entitlements
AMS
Populate User Info
To remote AMS
Query User Info
Provisioning Interface
POP/IMAP/SMTP
(1) Outlook / Netscape clients
is user local to
this node
REMOTE
LOCAL
Remote POP/
IMAP/SMTP
(2) Get User active home node
Socket Interface
(2) Get service entitlements
Requests from other network elements
(2) Get User information
LDAP3 Interface
(1) LDAP3 Interface
does user have
Cellular / Email
access
To Email components
To Celluller components