Novell GROUPWISE 7 ASYNC GATEWAY - INSTALLATION AND ADMINISTRATION, Руководство по установке и администрированию

Страница: 134 / 140

134
GroupWise 7 Async Gateway Installation and Administration Guide
Novell Confidential Manual (ENU) 21 December 2004
domain \wpgate\async\wpcsout\asy xxxx \ 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.