OSI/MHS Configuration and Management Manual

Configuring Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
5-5
Format of Configuration Descriptions
5. A similar process occurs at MTA2. MTA2 determines that the message needs to
be relayed to MTA3. An association initiated by MTA2 is established to MTA3, and
the message is relayed.
6. MTA3 checks the recipient name and determines that the message is for a local
MS user specified by APPL object #TerryJones. The message is then delivered
and stored in the mailbox for that local MS user. If the message is for a user of the
Transfer X400 gateway, the message is sent through the gateway.
7. A UA retrieves the message from the user mailbox. A Transfer application
receives the message from the gateway.
Format of Configuration Descriptions
The following subsections describe the configurations of the three sample MTAs,
starting with MTA2 because it is the simplest. The format used in this section to
describe each configuration is the same and consists of:
•
Topology and major features of the MTA.
•
A configuration diagram, showing the OSI/MHS objects and attributes that define
the MTA. (The attributes are described briefly in the next few pages.)
•
Detailed considerations for each MTA.
•
A sample installation file.
Appendix A, Examples of Configuration Files, contains:
•
The installation files for each MTA.
•
A sample configuration file containing SCF commands to configure each MTA
(OSI/MHS subsystem).
•
An overview of the OSI addresses for each MTA.
•
A sample configuration file containing SCF commands to configure OSI/AS and
OSI/TS for each MTA.
The OSI/MHS object types relevant to this configuration are the following:
APPL
CLASS
CUG
CUGMEMBER
DLIST
DLISTMEMBER
GATEWAY
GROUP
MTA
PROCESS