OSI/MHS Orientation Guide

Building Your Message Handling System
OSI/MHS Orientation Guide—424829-001
1-21
Where to Look
•
Set up your MHS environment on the NonStop system, as described in “Setting Up
a Backbone Messaging Network or Hub.”
•
Describe the remote MTA in your MHS configuration, using the Subsystem Control
Facility (SCF). Specifically, define the MTA, the route or routes that connect
OSI/MHS to the MTA, and the gateway (if the gateway for your application runs on
the NonStop system).
•
Describe the Compaq MTA (OSI/MHS) to the other system, using tools provided for
that implementation.
•
Specify the names and addresses of X.400 users. You use X.400 addresses to define
routes and gateways and, in some cases, to specify the single user of a dedicated
connection. If you use a directory service, you load this information into its
database.
•
Manage the X.400 gateway.
If the X.400 gateway runs on the NonStop system, it uses a component called the
Gateway Programmatic Interface (GPI). In this case, you must be familiar with the
components of the GPI and know how to install and manage them. (See “Integrating
Your Own Messaging System With OSI/MHS” earlier in this section.)
To perform most configuration tasks, you must understand the concepts and components
of X.400, especially those pertaining to naming, addressing, and routing. You will also
need to know enough about the X.400 protocols, the underlying OSI products, and how
the standards are implemented on both sides of the connection to be able to troubleshoot
interoperation problems, should they arise.
In general, a connection between OSI/MHS and a large X.400 service provider is simple
to plan and describe, because there is usually one OSI/MHS MTA connected to one
MTA in the network of the service provider: thus, routing is straightforward. By
contrast, where OSI/MHS is the service provider, configuration is more complex
because the OSI/MHS MTA is connected to numerous other MTAs; not only are there
more options for routing, but different MTAs might use different X.400 name formats
and underlying network services.
Where to Look
In addition to manuals and educational materials from Compaq, you are likely to need
information of the following types:
•
Policy statements from your own company, from networking service providers with
whose networks yours must communicate, and from government or international
organizations whose rules you must follow.
•
Manuals and conformance statements (PICS) from other vendors whose X.400
products will communicate with OSI/MHS, and manuals describing applications,
gateways, and X.400 services with which OSI/MHS must communicate.
•
Copies of the CCITT X.400 series of Recommendations.
•
X.400 names and addresses (O/R names) of members of your user community.