B.2 Exchange Gateway Directory Structure under the Domain
The Exchange Gateway is installed in a subdirectory of the domain it belongs to.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Exchange Gateway root directory
B.2.1 domain\wpgate\exchange directory
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 server 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 server where the gateway is running, as described in Section 10.4, Reducing Network Traffic.
000.prc directory
The 000.prc directory is where the Exchange Gateway processes messages that are passing through the gateway between the GroupWise and Exchange systems.
mmddlog.nnn files
The mmddlog.nnn files are the Exchange Gateway log files where message routing information is recorded. See Section 9.3, Using Exchange Gateway Log Files.
gwwork directory
The gwwork directory holds temporary files used in message processing.
gwhold directory
The gwhold directory is where delayed delivery messages are held until their delivery times arrive.
gwprob directory
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 Section 9.5, Notifying the Exchange Gateway Administrator about Bad Messages.
ds directory
The ds directory helps the gateway keep track of whether or not directory synchronization has been performed.
gwds file
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.
dx directory
The dx directory helps the gateway keep track of whether or not directory exchange has been performed.
gwdx file
The gwdx file indicates that directory exchange has taken place. If you delete the gwdx file and restart the gateway, the gateway performs directory exchange immediately and then recreates the file.
uninstexchange directory
The uninstexchange directory contains the Exchange Gateway uninstallation program and supporting files.
wpcsin directory
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. For more information, see:
The MTA input queue contains eight priority subdirectories.
0-7 priority directories
The 0-7 priority subdirectories in the MTA input queue handle different types of messages transferring from the Exchange system into the GroupWise system.
-
0: Not used by the Exchange Gateway
-
1: Not used by the Exchange Gateway
-
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 Section 8.7, Enabling Message Status for Sent Items.
wpcsout directory
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.
excxxxx directory
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.
-
0: Busy searches from GroupWise users on Exchange users
-
1: Not used by the Exchange Gateway
-
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 Section 8.7, Enabling Message Status for Sent Items.
problem directory
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.
api_in directory
The api_in directory is where the Microsoft Calendar Connector places free/busy requests from Exchange users. The Exchange Gateway picks up the free/busy requests and passes them into the GroupWise system so that GroupWise users’ Calendars can be checked for availability. For setup instructions, see Section 5.2.2, Setting Up Bidirectional Busy Search for Exchange 2000/2003.
api_out directory
The api_out directory is where the Exchange Gateway places free/busy requests that have been checked against GroupWise users’ Calendars. The Microsoft Calendar Connector picks up the free/busy requests and the associated GroupWise user Calendar information and passes them into the Exchange system so that Exchange users are able to obtain GroupWise users’ availability information. For setup instructions, see Section 5.2.2, Setting Up Bidirectional Busy Search for Exchange 2000/2003.
readmeen.txt file
The readmeen.txt file lists sources of documentation for the GroupWise 7 Gateway for Microsoft Exchange on the GroupWise Gateways Documentation Web site.
readmeen.html file
The readmeen.txt file lists sources of documentation for the GroupWise 7 Gateway for Microsoft Exchange on the GroupWise Gateways Documentation Web site.
exgate.exe file
The exgate.exe file is the Exchange Gateway executable file. You run this program to start the Exchange Gateway. See Section 7.1, Starting the Exchange Gateway.
gwexch.cfg file
The gwexch.cfg file is the Exchange Gateway startup file where you can use startup switches to configure the Exchange Gateway. See Section 11.0, Using Exchange Gateway Startup Switches.
access.cfg file
The access.cfg file is the Exchange Gateway access control file where you can control access through the gateway. See Section 8.4, Controlling Gateway Access.
acct file
The acct file is the accounting file where information about messages passing through the gateway is recorded. See Section 8.5, Setting Up Accounting.
stat file
The stat file is the gateway statistics file that contains the statistics information displayed on the Exchange Gateway server console. See Section 9.1, Using the Exchange Gateway Server Console.
gwcorr.* files
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 Section 8.7, Enabling Message Status for Sent Items.
The gwcorr.dc file is the data dictionary file from which the gwcorr.db file is created.
ngwexh.mib file
The ngwexh.mib file is used if you configure the Exchange Gateway for SNMP. See Section 9.4, Using SNMP Monitoring Programs.
gwexgate.chm file
The gwexgate.chm file is the Windows help file that is available from the Exchange Gateway server console.
novell_ex.hs file
The novell_ex.hsfile is the JavaHelp helpset file for the Exchange Gateway help available in ConsoleOne.
map.jhm file
The map.jhm file is the JavaHelp map file that maps contexts to Exchange Gateway help topics in ConsoleOne.
*.htm files
The *.htm files are the Exchange Gateway help topics that are available in ConsoleOne.
gwstrs.fil file
The gwtrs.fil file is the strings resource file used by the Exchange Gateway server console on the Windows server where the gateway runs.
*.dll files
The *.dll files are supporting programs that provide specialized functionality to the Exchange Gateway.