OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-46
GATEWAY Objects
exit gateway before OSI/MHS decodes or routes them. Typically, an exit gateway is
configured in cases where messages received from remote systems are to be
examined or modified by an external GPI-based application prior to normal processing
by OSI/MHS.
GW-PNAME specifies the name of the entry manager process(es). GW-PNAME is a
list of up to five entry manager process names. These multiple processes allow for
fault tolerance and load balancing between MR groups.
This attribute is required for both Transfer X400 and general user gateways. For a
Transfer X400 gateway, GW-PNAME must also be defined in the Transfer
configuration file DEFINE4, attribute X4EntryServNames.
GW-AUX-PNAME specifies the process name of the wait manager associated with the
gateway process. For a Transfer gateway, this attribute is for information purposes
only. For a non-Transfer X400 gateway, it is required.
Using the GATEWAY object type, you can:
•
Define and control the Transfer X400 gateway or general user gateway
•
Add, delete, and alter the GATEWAY object
•
Determine the names of all the attribute values configured in the gateway
•
Select a normal or P1-EXIT (special exit) gateway
GATEWAY Object States
GATEWAY objects do not have summary states.
Naming GATEWAY Objects
A GATEWAY object name has the form:
system
is the name of the system (node) that runs the MHS manager process for this
OSI/MHS subsystem.
manager-process
is the name of the MHS manager (the MON object).
Note. You must configure and start the entry managers—and, for general user gateways, the
wait manager—before you can start a GI group. For information on configuring and starting
entry and wait managers, see Section 6, Starting, Stopping, and Updating Your OSI/MHS
Subsystem.
[\system.]$manager-process.#gateway