This message flow diagram illustrates how a GroupWise message travels from one user to another in the local post office when the users are accessing their Caching mailboxes.
Figure 1-2 Message Flow in Caching Mode
Table 1-2 Message Flow in Caching Mode Stages
Stage |
Icon |
Description |
---|---|---|
Sender |
|
The user sends a message to recipients in the same post office. The user is in Caching mode. |
Sender’s GroupWise Client |
|
The GroupWise client updates the sender’s Caching mailbox (\novell\groupwise\gwxxxxxxx\rofdata) by performing the following actions:
|
Sender’s GroupWise Client |
|
In Caching mode, sending a message always initiates an immediate connection with the POA in order to send the message. The GroupWise client communicates the message to the POA and deletes the copy in the rofdata\wpcsin\1 priority subdirectory when the POA has processed the message. |
POA for Local Post Office |
|
The POA receives the message from the GroupWise client and performs the following actions for the sender to update the sender’s Online mailbox:
The POA also performs the following actions for the recipients to update their Online mailboxes:
|
POA for Local Post Office |
|
Because the recipients are also in Caching mode, they do not receive immediate notification that a new message has arrived in their Online mailboxes. Based on the option under , each recipient’s GroupWise client sends a request to the POA for items that have arrived in the recipient’s Online mailbox since the last connection with the POA. |
POA for Local Post Office |
|
The POA responds by sending information to update each recipient’s Caching mailbox and communicates to the GroupWise client that a new message has arrived. |
Recipient’s GroupWise Client |
|
Each recipient’s GroupWise client updates the recipient’s Caching mailbox by performing the following actions:
|
Recipient’s GroupWise Client |
|
The Notify component of each recipient’s GroupWise client notifies the recipient that a new message has arrived. |
Recipient |
|
Each recipient opens the message in the GroupWise client. |
Recipient’s GroupWise Client |
|
Each recipient’s GroupWise client generates an Opened status and places it in the rofdata\wpcsin\1 priority subdirectory to await the next connection with the POA. |
Recipient’s GroupWise Client |
|
When each recipient sends a message or the time specified by the option has elapsed, each recipient’s GroupWise client connects with the POA and communicates the Opened status to the POA, along with any other data that needs to be uploaded to the recipient’s Online mailbox. |
POA for Local Post Office |
|
The POA receives the Opened status from the GroupWise client and updates the message in the sender’s message database with the Opened status. |
Recipient’s GroupWise Client |
|
Because the sender is in Caching mode, the sender does not immediately receive the Opened status. Based on the sender’s actions and caching schedule, the sender’s GroupWise client eventually sends a request to the POA for items that have arrived in the sender’s Online mailbox since the last synchronization of the Caching mailbox. |
POA for Local Post Office |
|
The POA responds by sending information to update the sender’s Caching mailbox and communicates the Opened status to the sender’s GroupWise client. |
Recipient’s GroupWise Client |
|
The sender’s GroupWise client updates the sender’s Caching mailbox by performing the following action:
|
Sender |
|
When the sender checks the sent items in his or her mailbox in the GroupWise client, the message displays a status of Delivered and Opened for each recipient. |