The Exchange Gateway is installed in a subdirectory of the domain it belongs to.
Exchange Gateway root directory |
|
000.prc |
Directory for message processing |
gwhold |
Directory for retaining delayed delivery messages |
Directory for undeliverable messages |
|
Directory for directory synchronization files |
|
Directory for directory exchange files |
|
Directory for the Exchange Gateway uninstallation program |
|
MTA input queue directory |
|
MTA output queue directory |
|
Readme file |
|
Exchange Gateway program |
|
Accounting file |
|
Gateway maintenance batch file |
|
Exchange Gateway MIB file |
|
Windows help file for the Exchange Gateway console |
|
Exchange Gateway resource file |
|
Supporting Windows DLL programs |
The Exchange Gateway root directory is the default location for all Exchange Gateway files. During installation, you choose the domain where you want to install the Exchange Gateway and you choose the name of the root directory. The default directory name is exchange.
To improve performance if you installed the Exchange Gateway on a Windows machine remote from the domain directory (for example, if the domain directory is located on a NetWare® server), you can move the queue directories from the domain directory to the Windows machine where the gateway is running, as described in Reducing Network Traffic.
The 000.prc directory is where the Exchange Gateway processes messages that are passing through the gateway between the GroupWise and Exchange systems.
The mmddlog.nnn files are the Exchange Gateway log files where message routing information is recorded. See Using Exchange Gateway Log Files.
The gwwork directory holds temporary files used in message processing.
The gwhold directory is where delayed delivery messages are held until their delivery times arrive.
The gwprob directory is where the Exchange Gateway places incoming message files that it cannot process. Using the /badmsg switch, you can configure the gateway to retain bad messages, delete bad messages, or send bad messages to the gateway postmaster. See Notifying the Exchange Gateway Administrator about Bad Messages.
The ds directory helps the gateway keep track of whether or not directory synchronization has been performed.
The gwds file indicates that directory synchronization has taken place. If you delete the gwds file and restart the gateway, the gateway performs directory synchronization immediately and then recreates the file.
The dx directory helps the gateway keep track of whether or not directory synchronization has been performed.
The gwdx file indicates that directory synchronization has taken place. If you delete the gwds file and restart the gateway, the gateway performs directory exchange immediately and then recreates the file.
The uninstexchange directory contains the Exchange Gateway uninstallation program and supporting files.
The wpcsin directory is the MTA input queue where the Exchange Gateway places messages from Exchange users for transfer into the GroupWise system. When a new message arrives, the MTA for the domain where the gateway is installed routes it to the appropriate destination. The wpcsin directory in the Exchange Gateway directory is parallel to the wpcsin directory in the domain. See "Domain Directory" in the GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure for more information.
The MTA input queue contains eight priority subdirectories.
The 0-7 priority subdirectories in the MTA input queue handle different types of messages transferring from the Exchange system into the GroupWise system.
2: High priority messages from Exchange users to GroupWise users
3: Status messages notifying Exchange users about the status of high priority messages sent to GroupWise users
4: Normal priority messages from Exchange users to GroupWise users
5: Status messages notifying Exchange users about the status of normal priority messages sent to GroupWise users
6: Low priority messages from Exchange users to GroupWise users
7: Status messages notifying Exchange users about the status of low priority messages sent to GroupWise users
Status message correlation must be enabled in order for Exchange users to receive status information about messages sent to GroupWise users. See Enabling Message Status for Sent Items.
The wpcsout directory is the MTA output queue where the MTA for the domain where the gateway is installed places messages for transfer over to the Exchange system.
The excxxxx directory contains eight priority subdirectories.
0-7 priority directories
The 0-7 priority subdirectories in the MTA output queue handle different types of messages transferring from the GroupWise system into the Exchange system.
2: High priority messages from GroupWise users to Exchange users
3: Status messages notifying GroupWise users about the status of high priority messages sent to Exchange users
4: Normal priority messages from GroupWise users to Exchange users
5: Status messages notifying GroupWise users about the status of normal priority messages sent to Exchange users
6: Low priority messages from GroupWise users to Exchange users
7: Status messages notifying GroupWise users about the status of low priority messages sent to Exchange users
Status message correlation must be enabled in order for GroupWise users to receive status information about messages sent to Exchange users. See Enabling Message Status for Sent Items.
The problem directory is where the MTA places message files that it cannot deliver into one of the eight priority subdirectories, perhaps because the message files have been damaged.
The readme.txt file describes issues and limitations of the Exchange Gateway.
The exgate.exe file is the Exchange Gateway executable file. You run this program to start the Exchange Gateway. See Starting the Exchange Gateway.
The gwexch.cfg file is the Exchange Gateway startup file where you can use startup switches to configure the Exchange Gateway. See Using Exchange Gateway Startup Switches.
The access.cfg file is the Exchange Gateway access control file where you can control access through the gateway. See Controlling Gateway Access.
The acct file is the accounting file where information about messages passing through the gateway is recorded. See Setting Up Accounting.
The stat file is the gateway statistics file that contains the statistics information displayed on the Exchange Gateway console. See Using the Exchange Gateway Console.
The gwcorr.db file is the message status correlation database that enables message status information to be exchanged between GroupWise users and Exchange users. See Enabling Message Status for Sent Items.
The gwcorr.dc file is the data dictionary file from which the gwcorr.db file is created.
The gwmaint.bat file is run by the Exchange Gateway each night to perform whatever server maintenance tasks you place in it. See Setting Up Daily Maintenance Tasks.
The ngwexh.mib file is used if you configure the Exchange Gateway for SNMP. See Using SNMP Monitoring Programs.
The gwexgate.chm file is the Windows help file that is available from the Exchange Gateway console.
The novell_ex.hs file is the JavaHelp helpset file for the Exchange Gateway help available in ConsoleOne®.
The map.jhm file is the JavaHelp map file that maps contexts to Exchange Gateway help topics in ConsoleOne.
The *.htm files are the Exchange Gateway help topics that are available in ConsoleOne.
The gwtrs.fil file is the strings resource file used by the Exchange Gateway console on the Windows machine where the gateway runs.
The *.dll files are supporting programs that provide specialized functionality to the Exchange Gateway.