OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-23
APPL Objects
Message Store (MS) APPL Object
A message store (MS) APPL object type represents an X.400 user agent (UA) to the
OSI/MHS subsystem. The user application enables the UA to submit messages to,
and retrieve them from, one of the subsystem message stores. When you define a
new APPL object, a user application record is added to the user database, and a copy
goes in the routing database (where, along with ROUTE objects, it helps the
subsystem determine the best route for an outgoing message).
Suppose a remote application (interactive or programmatic) wants to access the
subsystem to submit or retrieve a message. The UA that represents the application
first establishes an association with an RS group. The RS process then compares the
O/R name and password of the UA to those found in the user application records in the
database to check whether the UA is known to the subsystem and has right of access.
If validated, the UA can, for the duration of the association, submit or retrieve
messages using the message store specified in the user application record.
Using the MS APPL object type, you can:
•
Add, delete, and alter the specified user application record.
•
Start, stop, suspend, and reactivate the user application record.
•
Determine the attribute values and operational status of the user application
record.
•
Determine the names of some or all user application records in this OSI/MHS
subsystem.
APPL Object States
An OSI/MHS APPL object does not represent a process, but rather a user application
record used for comparison. Therefore, its states are not process states. Instead, they
reflect the APPL object’s readiness to be used to validate and allow user access
requests. You can use the SCF STATUS command to inquire about the state of an
OSI/MHS user application. Other SCF commands allow you to change its state.