OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-6
Roles of OSI/MHS
As Figure 1-3 shows, an OSI/MHS subsystem consists of the following groups
(collections of processes):
•
MR groups (one or more), which provide the MTA function
•
RS groups (zero or more), which provide the remote operations service
•
GI groups (zero or more), which provide gateway interfaces
•
LO groups (zero or more), which provide local operations services
•
MS groups (zero or more), which provide long-term storage of messages
You can also provide password servers or use the Master Password Server to provide
security services, but a password server is considered external to the subsystem and
is not managed with the same set of tools.
A user or application accesses the subsystem in any of several ways:
•
Through a remote UA, which implements the P7 protocol and communicates with
OSI/MHS through an RS group
•
Through a local UA, which implements the P7 protocol and communicates with
OSI/MHS through an LO group
•
Through a Transfer application, which communicates with OSI/MHS through the
Transfer X400 gateway
•
Through a general user gateway created with the Gateway Programmatic Interface
(GPI), which communicates with OSI/MHS through a GI group
Roles of OSI/MHS
OSI/MHS can function in several ways. You can use it for adjacent MTA message
transfer, as a gateway, as a message store, or as any combination of these.
Using OSI/MHS for Adjacent MTA Message Transfer
OSI/MHS can serve as the center of a messaging network. Figure 1-4 shows a
OSI/MHS subsystem used for adjacent MTA message transfer.