Message Flow from Async Gateway to Async Gateway
Stage 1: Sender
The user sends a message to recipients in a post office in a different domain. In this diagram, the delivery mode in the local post office is Use App Thresholds and the threshold is not exceeded.
Stage 2: Sender's GroupWise Client
The GroupWise client performs the following actions for the sender:
- Adds the message to the message database (msg 0-24.db file) assigned to the sender.
- Creates a pointer in the sender's user database (userxxx.db file) so the message appears in the sender's Out Box.
- Places attachments larger than 2 KB in the post office\offiles\fd0-7f subdirectory assigned to the sender 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 copy of the message in the appropriate priority 0-7 subdirectory of the sender's MTA input queue.
If a different delivery mode were in effect in the post office, some or all of these actions would be performed by the POA instead of the GroupWise client.
Stage 3: MTA in Sender's Domain
The MTA in the sender's domain polls its input queue as specified by Scan Cycle in Agent Settings in ConsoleOne®. When it detects a new message, the MTA recognizes that it must be sent through a gateway and places the message in its output queue in the gateway's directory structure:
domain\wpgate\async\wpcsout\asyxxxx\1-3
Stage 4: Async Gateway in Sender's Domain
The Async Gateway in the sender's domain detects the message in the queue, determines the message priority, and places it in the appropriate connection ID directory and in the appropriate priority subdirectory.
domain\wpgate\async\gwout\connnection_ID\1-3
The connection ID directory is used for a specific domain connection (other Async Gateways in other GroupWise systems). There might be several domain connection ID subdirectories for your Async Gateway. The master schedule and calling intervals use the message counts in the priority subdirectories 1-3 to determine when the gateway initiates the modem connection.
Stage 5: Async Gateway in Sender's Domain
When message counts reach levels set in the Async Gateway's master schedule and calling intervals, the gateway dials out on the modem defined for the designated port, reads the message file from the priority directory 1-3, compresses the message, and places it in a compression directory ready for transmission across the modem.
Stage 6: Modem Connection Between Gateways
The sender's Async Gateway establishes a modem connection with a modem defined for another Async Gateway defined at the recipient's GroupWise site. The Async Gateway in the recipient's domain begins to receive the incoming message file. The gateway begins to build the message in its input queue's compressed message directory:
domain\wpgate\async\gwin\connection_ID\cmp
Stage 7: Async Gateway in Recipient's Domain
The message is fully received. The recipient's Async Gateway decompresses the file and moves it into the \gwin\connection_ID directory.
Stage 8: Async Gateway in Recipient's Domain
The recipient's Async Gateway moves the file from the \gwin\connection_ID directory into the MTA input queue in the gateway directory structure:
domain\wpgate\async\wpcsin\0-7
Stage 9: MTA in Recipient's Domain
The MTA in the recipient's domain polls the gateway's MTA input queue as specified by Scan Cycle in Agent Settings in ConsoleOne. When it detects a new message, the MTA picks up the message from its domain input queue and transfers it to its output queue in the recipient's post office. The MTA output queue is the input queue for the POA in the recipient's post office.
Stage 10: POA in Recipient's Post Office
The POA polls its input queue regularly. When it detects a new message, the POA in the recipient's post office performs the following actions:
- Adds the message to the message database (msg 0-24.db file) corresponding to the one assigned to the sender.
- Creates a pointer in the recipient's user database (user xxx.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\fd0-7f subdirectory corresponding to the one assigned to the sender 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 appropriate priority 0-7 subdirectory of the recipient's MTA input queue.
Stage 11: Recipient's GroupWise Client
The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.
Stage 13: Recipient's GroupWise Client
Each recipient's GroupWise client creates an Opened status message in the appropriate priority 0-7 subdirectory of the recipient's MTA input queue.
Stage 14: MTA in Recipient's Domain
The MTA in the recipient's domain polls all its input queues in the domain as specified by Scan Cycle in Agent Settings in ConsoleOne. When it detects a status message in the recipient's post office, the MTA picks it up and transfers it to the MTA input queue in the sender's domain.
Stage 15: Async Gateway in Recipient's Domain
The recipient's Async Gateway picks up the message from the MTA output queue and moves it to the output queue priority subdirectories of the appropriate connection ID directory:
domain\wpgate\async\gwout\connection_ID\1-3
Stage 16: Async Gateway in Recipient's Domain
If the connection to the sender's Async Gateway is still valid, the recipient's Async Gateway compresses the file and moves it to appropriate connection ID directory for sending across the wire:
domain\wpgate\async\gwout\connection_ID
Stage 17: Modem Connection Between Gateways
The recipient's Async Gateway sends the file through the modem connection to the Async Gateway at the sender's GroupWise site. If the connection is terminated, the file waits in the connection_ID directory until a new connection is established. The Async Gateway in the sender's domain begins to receive the incoming message file. The gateway begins to build the message in its input queue, compressed message directory:
domain\wpgate\async\gwin\connection_ID\cmp
Stage 18: Async Gateway in Sender's Domain
The message is fully received. The sender's Async Gateway decompresses the file and moves it into the \gwin\connection_ID directory.
Stage 19: Async Gateway in Sender's Domain
The sender's Async Gateway moves the file from the \gwin\connection_ID directory into the MTA input queue in the gateway directory structure:
domain\wpgate\async\wpcsin\0-7
Stage 20: MTA in Sender's Domain
The MTA in the sender's domain polls all its input queues in the domain as specified by Scan Cycle in Agent Settings in ConsoleOne. When it detects a status message in its gateway input queue, the MTA picks it up and transfers it to its output queue in the sender's post office. The MTA output queue is the input queue for the POA in the sender's post office.