The Notes Gateway is installed in a subdirectory of the domain it belongs to.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 server where the gateway is running, as described in Section 9.4, Reducing Network Traffic.
The 000.prc directory is where the Notes Gateway processes messages that are passing through the gateway between the GroupWise and Notes systems.
The gwwork directory holds temporary files used in message processing.
The mmddlog.nnn files are the Notes Gateway log files where message routing information is recorded. See Section 8.3, Using Notes Gateway Log Files.
The acct file contains information about the messages the Notes Gateway sends each day. It is e-mailed to the accounts each day at midnight. For more information about the accounting files, see Section 7.5, Setting Up Accounting.
The set file stores Notes Gateway console settings such as color, log settings, and so on. For more information, see Section 8.1, Using the Notes Gateway Server Console.
The stat file stores statistics about the Notes Gateway’s functioning. For information about the statistics provided by the Notes Gateway, see Statistics Box.
The proc file is the lock file for the Notes Gateway process. The proc file is opened and locked when the Notes Gateway starts. This prevents multiple Notes Gateways from being started for the same domain.
The pulse.tmp file is re-created by the Notes Gateway every time it completes a cycle (after an idle loop). If you are not at the Notes Gateway server console but need to know if the Notes Gateway is running, you can delete the pulse.tmp file. If the Notes Gateway is running, it re-creates the file.
The gwhold directory is where delayed delivery messages are held until their delivery times arrive.
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 Section 8.5, Notifying the Notes Gateway Administrator about Bad Messages.
In the current version 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.
The uninstnotes directory contains the Notes Gateway uninstallation program and supporting files.
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. For more information, see:
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 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 Section 7.7, 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 Notes system.
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 Section 7.7, 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 readmeen.txt file lists sources of documentation for the GroupWise 7 Gateway for Lotus Notes on the GroupWise Gateways Documentation Web site.
The readmeen.html file lists sources of documentation for the GroupWise 7 Gateway for Lotus Notes on the GroupWise Gateways Documentation Web site.
The ngate.exe file is the Notes Gateway executable file. You run this program to start the Notes Gateway. See Section 6.1, Starting the Notes Gateway.
The notes.cfg file is the Notes Gateway startup file where you can use startup switches to configure the Notes Gateway. See Section 10.0, Using Notes Gateway Startup Switches.
The access.cfg file is the Notes Gateway access control file where you can control access through the gateway. See Section 7.4, Controlling Gateway Access.
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 Section 7.7, Enabling Message Status for Sent Items.
The gwcorr.dc file is the data dictionary file from which the gwcorr.db file is created.
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 when directory synchronization and exchange are enabled. See Section 7.1, Enabling Directory Synchronization and Exchange.
The ngwln.mib file is used if you configure the Notes Gateway for SNMP. See Section 8.4, Using SNMP Monitoring Programs.
The gwngate.chm file is the Windows help file that is available from the Notes Gateway server console.
The novell_ln.hsfile is the JavaHelp helpset file for the Notes Gateway help available in ConsoleOne®.
The map.jhm file is the JavaHelp map file that maps contexts to Notes Gateway help topics in ConsoleOne.
The *.htm files are the Notes Gateway help topics that are available in ConsoleOne.
The gwsetup.exe file is the Notes Gateway Setup program that is called by the Installation program (install.exe).
The setup.inf file contains information used by the Installation program.
The gwtrs.fil file is the strings resource file used by the Notes Gateway server console on the Windows server where the gateway runs.
The wp_ga_us.trs file is the strings resource file used by the Notes Gateway Installation program.
The *.dll files are supporting programs that provide specialized functionality to the Notes Gateway.