OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 24 of 68
10.1 Provisioning System – NAM, Listener,
Translator
Users are provisioned on the system using the provisioning server. The
following method can re are three interfaces
• Java Provisioning client – PC based. The Java Administrator Client
allows an Administrator to manage the entire configuration of the
OmniMessaging application. It is portable and can execute on any
system that supports Java. It is used to add domains, users, blacklists
etc. For details refer to the OmniMessaging Java Provisioning Client
Manual.
• Provisioning batch load – Server based. This method is ideal to migrate
a large number of users in a short time. 10,000 users can be provisioned
per hour. We export the user information from the existing email server
and transform the data to the OmniMessaging format. This batch load is
then provided to the Provisioning Server. Following that the emails are
migrated from the old system to the OmniMessaging system. With this
approach we can migrate 100,000 users within a weekend. This method
is used by our Professional Services Team.
• Custom built provisioning using Message Store API interface. This
method is used by accounts that have special provisioning needs. This
method is not normally used as all features are provided via the
Provisioning system.
In a Multi Node environment the Provisioning server will populate the address
book and make corresponding entries on all nodes to support a large multi node
cluster.
10.1.1 Message Transfer Agent (MTA)
The OmniMessaging MTA consists of receiving MTA, sending MTA and
distributor NonStop™ TS/MP server classes. NonStop™ TS/MP software
provides management of the NonStop™ TS/MP processes by means of the
PATHMON process. There can be multiple MTA and distributor processes.
The distributor process allows for monitoring of multiple local IP addresses.
Each MTA process instance implements SMTP functionality and interacts with
ZLEMAIL ADAPTER gateway applications.
When a receiving MTA process is started, the MTA process registers itself with
the distributor process. When the distributor process receives a message from
TCP/IP, it uses an internal scheme to distribute requests to an MTA process
registered with the distributor process.