6.0 Administrative Database Update

ConsoleOne and the agents handle database updates throughout the GroupWise system.

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.

Figure 6-1 Administrative Message Flow through TCP/IP

Table 6-1 Administrative Message Flow through TCP/IP Stages

Stage	Actor	Action
GroupWise Administrator		The administrator uses the GroupWise Administrator snap-in 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 ConsoleOne. 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 communicates the administrative message to the POA in the post office by way of TCP/IP. The administrative message notifies the POA that 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 creates a copy of the administrative message in the priority 2 subdirectory of the administrative input queue (wpcsout\ads) in the post office. After the update is made successfully, the copy is deleted.
POA for Post Office		The POA updates the post office database (wphost.db) to reflect the addition, modification, or deletion performed in ConsoleOne and deletes the administrative message from its administrative input queue.