OSI/MHS Administrative Utility (AU) Manual

Introducing the Administrative Utility
OSI/MHS Administrative Utility (AU) Manual—424826-001
1-3
Overview of the AU Design
in Section 2, Installing and Configuring the Administrative Utility, for more information
about the Pathway parameters used for the AU.
The following events occur before a the URL for the AU is opened or anytime the Web
browser sends a request to the AU-DISTRIBUTOR class:
•
After detecting the request, the AU-DISTRIBUTOR class performs a Pathsend
procedure call to the AU-SERVER class. The AU-DISTRIBUTOR class remains
available to process any subsequent requests.
•
The AU-SERVER class replies to the Pathsend procedure call.
•
An instance of the AU-SERVER class creates a link through TCP/IP to the Web
browser, and the HTTP/HTML response is sent by the AU-SERVER class directly
to the Web browser through TCP/IP.
When a request involves user permissions, such as at logon or when any user
permissions require modification, the AU-SERVER class writes and reads user
permissions data to and from the AU user permissions internal database.
When a request involves PDU data, the AU-SERVER class writes and reads PDU data
to and from the OSI/MHS internal database.
In the case of gateway-queued PDUs, the AU-SERVER class also writes and reads PDU
data to and from one or more message transfer agents (MTAs), and reads PDU data
from the entry manager message queue file through an entry manager process. When a
user wants to remove a message from a gateway queue, the AU sends an interprocess
communication (IPC) to the appropriate MTA requesting the removal. The MTA
receives the IPC, schedules the work to be done, and replies to the AU. The AU then
displays the PDUs that have been queued for removal by the MTA.