Notes Gateway Directory Structure under the Domain
The Notes Gateway is installed in a subdirectory of the domain it belongs to.
domain\wpgate\notes directory
The Notes Gateway root directory is the default location for all Notes Gateway files. During installation, you choose the domain where you want to install the Notes Gateway and you choose the name of the root directory. The default directory name is notes.
To improve performance, you can move the queue directories onto the Windows machine where the gateway is running, as described in Reducing Network Traffic.
000.prc directory
The 000.prc directory is where the Notes Gateway processes messages that are passing through the gateway between the GroupWise and Notes systems.
mmddlog.nnn files
The mmddlog.nnn files are the Notes Gateway log files where message routing information is recorded. See Using Notes 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 Notes 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 Notes Gateway Administrator about Bad Messages.
migrate directory
In version 3.0 of the Notes Gateway, the migrate directory is not used because migration tools are not yet available. When the migration tools become available, you will be able to convert Notes mailboxes and archives into GroupWise mailboxes and archives.
uninstnotes directory
The uninstnotes directory contains the Notes Gateway uninstallation program and supporting files.
wpcsin directory
The wpcsin directory is the MTA input queue where the Notes Gateway places messages from Notes 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 Notes 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.
0-7 priority directories
The 0-7 priority subdirectories in the MTA input queue handle different types of messages transferring from the Notes system into the GroupWise system.
0: Busy searches from Notes users on GroupWise users
1: Not used by the Notes Gateway
2: High priority messages from Notes users to GroupWise users
3: Status messages notifying Notes users about the status of high priority messages sent to GroupWise users
4: Normal priority messages from Notes users to GroupWise users
5: Status messages notifying Notes users about the status of normal priority messages sent to GroupWise users
6: Low priority messages from Notes users to GroupWise users
7: Status messages notifying Notes users about the status of low priority messages sent to GroupWise users
Status message correlation must be enabled in order for Notes users to receive status information about messages sent to GroupWise users. See 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 Notes system.
notxxxx directory
The notxxxx 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 Notes system.
0: Busy searches from GroupWise users on Notes users
1: Not used by the Notes Gateway
2: High priority messages from GroupWise users to Notes users
3: Status messages notifying GroupWise users about the status of high priority messages sent to Notes users
4: Normal priority messages from GroupWise users to Notes users
5: Status messages notifying GroupWise users about the status of normal priority messages sent to Notes users
6: Low priority messages from GroupWise users to Notes users
7: Status messages notifying GroupWise users about the status of low priority messages sent to Notes users
Status message correlation must be enabled in order for GroupWise users to receive status information about messages sent to Notes users. See 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.
readme.txt file
The readme.txt file describes issues and limitations of the Notes Gateway.
ngate.exe file
The ngate.exe file is the Notes Gateway executable file. You run this program to start the Notes Gateway. See Starting the Notes Gateway.
notes.cfg file
The notes.cfg file is the Notes Gateway startup file where you can use startup switches to configure the Notes Gateway. See Using Notes Gateway Startup Switches.
access.cfg file
The access.cfg file is the Notes Gateway access control file where you can control access through the gateway. See Controlling Gateway Access.
acct file
The acct file is the accounting file where information about messages passing through the gateway is recorded. See Setting Up Accounting.
stat file
The stat file is the gateway statistics file that contains the statistics information displayed on the Notes Gateway console. See Using the Notes Gateway 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 Notes 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.
wpnames.nsf file
The wpnames.nsf file is the Notes version of the GroupWise Address Book. It is initially created in the domain\wpgate\notes directory during installation and is then copied to the \lotus\domino\data directory (for Lotus Notes 5.x and 6.x) or the \lotus\notes\data directory (for Lotus Notes 4.x) when directory synchronization and exchange are enabled. See Enabling Directory Synchronization and Exchange.
gwmaint.bat file
The gwmaint.bat file is run by the Notes Gateway each night to perform whatever server maintenance tasks you place in it. See Setting Up Daily Maintenance Tasks.
ngwln.mib file
The ngwln.mib file is used if you configure the Notes Gateway for SNMP. See Using SNMP Monitoring Programs.
gwngate.chm file
The gwngate.chm file is the Windows help file that is available from the Notes Gateway console.
novell_ln.hs file
The novell_ln.hs file is the JavaHelp helpset file for the Notes Gateway help available in ConsoleOne®.
map.jhm file
The map.jhm file is the JavaHelp map file that maps contexts to Notes Gateway help topics in ConsoleOne.
*.htm files
The *.htm files are the Notes Gateway help topics that are available in ConsoleOne.
gwsetup.exe file
The gwsetup.exe file is the Notes Gateway Installation program that is automatically called by setuplngw.exe, the self-extracting executable file that you download from the Novel Product Downloads Web site.
setup.inf file
The setup.inf file contains information used by the Installation program.
gwstrs.fil file
The gwtrs.fil file is the strings resource file used by the Notes Gateway console on the Windows machine where the gateway runs.
wp_ga_us.trs file
The wp_ga_us.trs file is the strings resource file used by the Notes Gateway Installation program.
*.dll files
The *.dll files are supporting programs that provide specialized functionality to the Notes Gateway.
Notes Gateway root directory
000.prc 
mmddlog.nnn 
cmd 
