Novell Documentation: GroupWise 6.5 - Mapped/UNC Link between the Domain and the Post Office

Mapped/UNC Link between the Domain and the Post Office

This message flow diagram illustrates how an administrative message, such as a database update request, passes from ConsoleOne to the agents so that databases are updated throughout the GroupWise system. In this diagram, the MTA writes the administrative message into the POA input queue in the post office.

Administrative message flow through a mapped or UNC link

Stage	Actor	Action
GroupWise Administrator		The administrator uses GroupWise Administrator in ConsoleOne to add, modify, or delete a GroupWise object in a single-domain, single-post office GroupWise system. An object could be a GroupWise user, resource, distribution list, post office, secondary domain, and so on.
ConsoleOne		ConsoleOne performs the following actions: Updates the domain database (wpdomain.db) to reflect the addition, modification, or deletion performed in GroupWise Administrator. Creates an administrative message in the priority 2 subdirectory of the domain's MTA input queue (wpcsin) to replicate the update.
MTA for Domain		The MTA for the domain transfers the administrative message to the MTA "in progress" (gwinprog) queue. From there, the MTA transfers the administrative message to the output queue in the post office. The MTA output queue is the input queue for the POA in the post office. The administrative message notifies the POA a GroupWise object has been added, modified, or deleted. Historical Note: In earlier versions of GroupWise, this function of the POA was handled by a separate agent, the Administration Agent (ADA). The ADA no longer exists in GroupWise.
POA for Post Office		The POA picks up the message from its administrative input queue in the post office, then updates the post office database (wphost.db) to reflect the addition, modification, or deletion performed in GroupWise Administrator.