1.2 Caching Mode

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:

  • Adds the message to the message database (rofdata\msg.db) in the Caching mailbox. This database is local equivalent of the msgnnn.db database in the post office.

  • Creates a pointer in the sender’s user database (rofdata\user.db) in the Caching mailbox so the message appears in the sender’s mailbox as a sent item. This database is the local equivalent of the userxxx.db database in the post office.

  • Places attachments larger than 2 KB in the rofdata subdirectory in the Caching mailbox and creates pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.) There is no local equivalent to the offiles subdirectory in the post office, so attachments are placed directly in the rofdata subdirectory in the Caching mailbox.

  • Places a copy of the message in the rofdata\wpcsin\1 priority subdirectory to await the next connection to the POA.

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:

  • Adds the message to the message database (msgnnn.db) assigned to the sender in the post office.

  • Creates a pointer in the sender’s user database (userxxx.db) in the post office.

  • Places attachments larger than 2 KB in one of the post_office\offiles\fd0-F6 subdirectories in the post office and creates pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

The POA also performs the following actions for the recipients to update their Online mailboxes:

  • Creates a pointer in each recipient’s user database (userxxx.db) to the message in the message database (msgnnn.db) in the post office so that the new message appears in each recipient’s mailbox.

  • Updates the message in the message database (msgnnn.db) in the post office with a Delivered status for the recipients.

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 Send/Retrieve All Marked Accounts Every nn Minutes option under Accounts > Account Options > General, 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:

  • Adds the message to the message database (rofdata\msg.db) in the recipient’s Caching mailbox.

  • Creates a pointer in the recipient’s user database (rofdata\user.db) to the message in the message database (rofdata\msg.db) so the new message appears in the recipient’s Caching mailbox.

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 Send/Receive All Marked Accounts Every nn Minutes 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:

  • Updates the message in the message database (rofdata\msg.db) with a Delivered and Opened status for each recipient.

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.