OSI/MHS Orientation Guide

Building Your Message Handling System
OSI/MHS Orientation Guide—424829-001
1-25
Where to Look
To integrate your gateway with the network, you need to know how to perform the
following functions:
•
Set up your MHS environment on the NonStop system, as described in “Setting Up
a Backbone Messaging Network or Hub” earlier in this section
•
Describe the gateway in your MHS configuration, using the Subsystem Control
Facility (SCF) to define the GIP processes, identify the application as a gateway,
and identify its users
•
Specify the names of X.400 recipients, if necessary for a dedicated gateway, using
SCF and possibly tools for the other system
•
Manage the gateway and the GIP
In general, to perform configuration tasks, you must understand the concepts and
components of X.400, especially those pertaining to naming, addressing, and routing. If
your application is an access unit for a type of messaging device, you should be familiar
with Recommendations and agreements with regard to access units. Regardless of your
application, you will also need to know enough about the X.400 protocols and the
characteristics of the remote messaging system to be able to troubleshoot interoperation
problems, should they arise. Finally, although the GPI insulates your application from
the details of ASN.1 encoding and decoding, an understanding of ASN.1 could be
necessary to troubleshoot interoperation problems and verify compliance with specific
standards or agreements.
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 describing the system for which you are writing a gateway, especially
information about its message formats and protocols
•
Copies of the CCITT X.400 series of Recommendations or the corresponding ISO
standards and the XAPIA specification for the GPI
•
Manuals for the C and possibly TAL programming languages, and NonStop
programming manuals
•
X.400 names and addresses (O/R names) of members of your user community
"About This Manual" lists and describes the X.400 Recommendations and related
documents, as well as the NonStop manuals you are likely to find most helpful.
Note. The GPI is one of several interfaces you can use to integrate applications with
OSI/MHS. Table 1-10, in the description of “Integrating EDI Applications,” contrasts the
available interfaces.