OSI/MHS Orientation Guide

Building Your Message Handling System
OSI/MHS Orientation Guide—424829-001
1-20
What You Need to Do
What You Need to Do
The procedures and considerations for integrating an existing messaging system with
OSI/MHS vary according to whether the system:
•
Is a native X.400 messaging system or a non-X.400 system with an X.400 gateway,
running outside the NonStop system
•
Uses a gateway application on the NonStop system
Figure 1-6 illustrates these options.
To integrate an existing X.400 messaging system or another type of messaging system
with an X.400 gateway, you describe the MTA or gateway when you define your
OSI/MHS configuration.
What You Need to Know
What you need to know to perform this task depends on the characteristics of the other
messaging applications or systems and whether OSI/MHS will provide the X.400
backbone network or connect certain users and applications to another X.400 network.
To integrate any other X.400 messaging system or service, you must know how to
perform the following functions:
Note. If you wish to integrate an application that runs as an X.400 remote user agent (RUA),
see the discussion on “Writing or Integrating a Remote User Agent,” later in this section. If you
wish to integrate an application that does not have an X.400 gateway, see the discussion on
“Writing and Integrating Your Own Messaging System With an X.400 Network.”
Figure 1-6. Integrating Other Messaging Systems With OSI/MHS
006CDT .CDD
Non-X.400
Messaging
System;
e.g., Telex Network
OSI/MHS
P1
GW
X.400
Messaging
System
GW
P1
Legend
GW = User-developed Gateway
GPI = Gateway Programmatic
Interface
GPI
Non-X.400
Messaging
System;
e.g., Facsimile