OSI/MHS Administrative Utility (AU) Manual

OSI/MHS Administrative Utility (AU) Manual—424826-001
Glossary-1
Glossary
ADMD (administration management domain). An X.400 domain managed by an
administration, such as a government or a public service. ADMDs can send, receive, and
provide intermediate routing for messages.
administrative management domain. See ADMD
class. A grouping or category of objects, based on their shared purpose and internal structure.
In OSI/MHS, groups of processes fall into classes, depending on the functions the
groups perform; for instance, the MS (message store) class consists of all the MS
processes and associated data in an OSI/MHS subsystem.
content. One of two basic parts of a message or report, containing the information to be
conveyed to the recipients. The other part is called the “envelope.” Probes contain a
description of the content rather than the content itself.
entry manager process. A queue manager process that you must specify when configuring
the Transfer X400 gateway. You can specify up to five entry manager processes.
envelope. The part of a message that contains information needed to transfer the message and
to deliver it to its intended recipients. The envelope takes different forms from the time
the message is submitted to the time it is delivered or retrieved, and depending on
whether it is submitted or retrieved directly through a message transfer agent (MTA) or
through a message store.
group. A collection of one or more processes and databases that provide a defined set of
services.
HTML (HyperText Markup Language). The tagging language used to format hypertext
documents on the World Wide Web. HTML is built on top of the Standard Generalized
Markup Language (SGML).
HTTP (HyperText Transfer Protocol). The communications protocol used for transmitting
data between servers and clients (browsers) on the World Wide Web.
HyperText Markup Language. See HTML
HyperText Transfer Protocol. See HTTP
interprocess communications. See IPC
IPC (interprocess communications). The request to or reply from a message transfer agent
(MTA). The IPC contains a header and one or more units-of-work.
master user. The master user is recognized as the user who owns the AU-SRVR (AU server)
process and should be the user that the OSI/MHS subsystem was installed under. The
master user performs all options defined in the user permissions database and enters the
permissions for all other users.