Message Flow from the GroupWise Windows Client in Remote Mode to the Async Gateway
Stage 1: Remote User
The GroupWise user, who is not currently connected to the network, sends a message to another GroupWise user or creates a request for items from the Master Mailbox.
Stage 2: Remote User's GroupWise Client
When the Remote user sends a message to another GroupWise user, the GroupWise client performs the following actions:
- Adds the message to the Remote message database (msg.db file) on the user's remote computer.
- Creates a pointer in the Remote user database (user.db file) so the message appears in the Out Box on the user's remote computer.
- Places attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments on the user's remote computer. (For database efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
- Creates a copy of the message in the priority 1 subdirectory of the Remote input queue on the user's remote computer.
When the Remote user sends a request for items from the Master Mailbox, the GroupWise client places the request in the priority 1 subdirectory of the Remote input queue on the user's remote computer.
Stage 3: Remote User's GroupWise Client
When the user initiates the modem connection, the GroupWise client on the remote computer polls the wpcsin\1 subdirectory and compresses the outgoing messages and/or requests into a file. If the compressed file totals over 50 KB, additional compressed files are created. The GroupWise client next moves the compressed files into the wpgwsend directory, then dials in to the gateway and logs in.
Stage 4: Remote User's GroupWise Client (Modem Connection)
When the login process is completed, the GroupWise client on the remote computer transmits the compressed message/request files across the modem connection to the system where the user's Master Mailbox is located.
Stage 7: MTA in Remote User's Domain
The MTA in the Remote user's domain polls its input queues as specified by Scan Cycle in Agent Settings in ConsoleOne. When it detects the new message or request from the Remote user, the MTA picks it up from its domain input queue and transfers it to its output queue in the post office where the Remote user's Master Mailbox is located.
The MTA output queue is the input queue for the POA in the post office where the Remote user's Master Mailbox is located. This message flow diagram illustrates only the simplest case, where the recipient is in the same post office as the Remote user's Master Mailbox. If the Remote user sends a message to a user in any other post office, the MTA would route the message to the appropriate destination.
Stage 8: POA in Remote User's Post Office
The POA polls its input queue regularly to quickly detect the new message or request from the Remote user. When the Remote user sends a message, the POA performs the following actions:
- Adds the message to the Remote user's message database (msg0-24.db file). This updates the Remote user's Master Mailbox.
- Creates a pointer in the recipient's user database (userxxx.db file) so the message appears in the recipient's In Box, and updates the notification information in the user database so the recipient can be notified of the message.
- Places attachments larger than 2 KB in the post_office\offiles\fd 0-7f subdirectory in the Remote user's post office and creates pointers from the message to its attachments. (For database efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
- Creates a Delivered status message in the priority 1 subdirectory of the Remote user's MTA input queue.
When the Remote user sends a request for items from the Master Mailbox, the GroupWise client performs the following actions:
- Gathers the requested items from the Remote user's Master Mailbox (msg 0-24.db file).
- Gathers any attachments for requested items from the post_office\offiles\fd0-7f subdirectory in the Remote user's post office.
- Compiles the information into a response file and places it in the priority 1 subdirectory of the MTA input queue for return to the Remote user.
Stage 9: MTA in Remote User's Domain
The MTA in the Remote user's domain polls its input queues as specified by Scan Cycle in Agent Settings in ConsoleOne. When it detects the new response for the Remote user, the MTA picks it up from its post office input queue and transfers it to its output queue in the Async gateway directory under wpgate in the Remote user's domain. The MTA output queue in the Async gateway directory is the input queue for the Async gateway.
Stage 10: Async Gateway
The Async gateway picks up the response file and moves it to the priority 1 subdirectory of its output queue.
Stage 11: Async Gateway
If the connection to the Remote user is still active, the Async gateway compresses the response files and moves them to the CMP directory. If the connection is no longer available, the response files wait in the connection_ID\1 subdirectory until a new connection is established by the Remote user.
Stage 12: Async Gateway (Modem Connection)
The Async gateway transmits the response files through the modem connection to the GroupWise client on the remote computer.
Stage 13: Remote User's GroupWise Client
The GroupWise client on the remote computer decompresses the response files and places them in its input queue on the Remote user's computer.
Stage 14: Remote User's GroupWise Client
Taking the items from its input queue, the GroupWise client performs the following actions for the Remote user:
- Updates the Remote message database (msg.db file) with any items requested from the Remote user's Master Mailbox.
- Creates pointers in the Remote user database (user.db file) so the messages gathered from the Master Mailbox appear in the Remote user's In Box and Out Box.
- Places any requested attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments. (For database efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
The Remote user's Remote mailbox now contains current copies of requested items from the user's Master Mailbox, plus any messages received in the user's Master Mailbox from other GroupWise users.