OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS

OSI/MHS Configuration and Management Manual—424827-003

1-9

Roles of OSI/MHS

OSI/MHS provides interfaces to allow local or remote UAs to access a message store.

A remote UA uses the P7 protocol and the Remote Operations Service Element

(ROSE) protocol. A local UA uses the P7 Application Programmatic Interface (P7 API).

Using OSI/MHS as an ADMD

In the network, OSI/MHS can function as an administration management domain

(ADMD), as a private management domain (PRMD), or as an MTA within a domain.

An ADMD is managed by an administration, such as a government or a public service.

ADMDs can send, receive, and provide intermediate routing for messages. Each

ADMD can have multiple MTAs. Each MTA can be in a separate NonStop node, or you

can have multiple MTAs on the same node. An OSI/MHS subsystem behaves as one

MTA.

Using OSI/MHS as a PRMD

A PRMD is managed by a private organization, such as a corporation. PRMDs can

send and receive messages, but they cannot relay messages to other management

domains. A PRMD must be either the originating or the receiving domain for a

message. In addition, according to the X.400 recommendations, PRMDs are located

within a single country. An international corporation, for example, defines at least one

PRMD for each country in which it operates. (The ISO MHS standards do not include

this restriction.) OSI/MHS can function as a PRMD in a network of privately owned

interconnected MTAs.

Figure 1-6. Message Store Function of OSI/MHS

007VST .VS D

NonStop System

MTA

OSI/MHS

Message

Store

Re mote

Local