OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Introduction
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
1-6
Queue Manager
fundamental part of an OSI/MHS subsystem. The MRP, together with the RTS, is
responsible for routing communications into and out of the gateway. When the MR
group starts, the gateway access unit (GAU), which is within the MRP, establishes a
connection with the entry manager process in the queue manager. This connection is
used for subsequent inbound operations.
MR groups are configured and managed by the OSI/MHS manager process. For details
on configuring and managing OSI/MHS MR groups, refer to the OSI/MHS
Configuration and Management Manual.
Queue Manager
The queue manager is associated with but not part of the OSI/MHS subsystem. The
client program requires elements of the queue manager to connect to the OSI/MHS
subsystem. Those elements include the queue file, the entry manager process, and the
wait manager process.
The queue file contains two logical queues: the ADMIN queue and the MESSAGE
queue. The GAU within the MRP sends configuration information about the PDU store
and MHS manager process name to the ADMIN queue. For each X.400 message to be
transferred to the GPI, the GAU sends a message entry to the MESSAGE queue.
The entry manager is used by both the MRP and GIP. The MRP needs an entry
manager process to send PDU IDs to be stored on the MESSAGE queue. The GIP
needs the entry manager to access MRP administrative data and enqueued PDU IDs.
The wait manager is also used by the GIP. During inbound processing, the wait
manager is used to notify the GIP of an inbound root object. The names of the wait
manager and entry manager are configured as attributes of the OSI/MHS GATEWAY
object. Note that, when starting gateway components, the queue manager should be
started before either the MRP or the GIPs. In addition, the MAXLINKS parameter of
the queue manager must be large enough to support the number of MRPs and GIPs.
For details on queue manager operation, refer to the Queue Manager Manual. For
details on configuring the queue manager for the GPI gateway, refer to the OSI/MHS
Configuration and Management Manual.
GPI Operation
Following is a basic description of the operation of the GPI gateway. The GPI gateway
performs three distinct types of actions.
•
NORMAL outbound information processing
•
NORMAL inbound information processing
•
P1-EXIT processing
For all three of these actions, the outbound direction is from the Client to the MTA.
The inbound direction is from the MTA to the Client (Figure 1-5
).