Planning the Exchange Gateway Installation

Before installing the Exchange Gateway, you should complete the planning tasks listed below. The planning tasks provide concepts and information you need as you install and set up the Exchange Gateway. You can use the Exchange Gateway Installation Worksheet to record your installation and setup information.

• Gathering GroupWise System Information
• Deciding Where to Install the Exchange Gateway
• Choosing a Gateway Name
• Deciding between Windows Application and Windows Service
• Deciding How to Monitor the Exchange Gateway
• Gathering Exchange System Information
• Determining Connections between Systems
• Selecting User Address Type and Format

Gathering GroupWise System Information

The Exchange Gateway needs to access the GroupWise domain where you want to link the gateway into your GroupWise system. You might want to create a new domain specifically for the Exchange Gateway. This keeps Exchange Gateway activity separate from domains where post offices are located. If you create a new domain, you might want to create it on the Exchange server to minimize network traffic.

Deciding Where to Install the Exchange Gateway

You can install the Exchange Gateway on the same machine with the domain that the gateway belongs to, if that domain is located on Windows. You can also install the Exchange Gateway on a separate machine, regardless of the platform where the domain is located. The machine where you install the Exchange Gateway must be an Exchange server.

If you install the Exchange Gateway on a different machine from where the domain is located, you must provide a username and password for the gateway to use when logging in to the machine where the domain is located. The gateway requires Read, Write, Create, Erase, Modify, and File Scan rights in the domain directory.

Choosing a Gateway Name

When you install the Exchange Gateway, a Gateway object is created in the domain where you install the gateway. The default gateway name is exchange.

When you install the Exchange Gateway, a subdirectory for the gateway software and queues is created under the domain directory. By default, the directory name is the same as the object name. If you use the default object name of Exchange, the gateway subdirectory is domain\wpgate\exchange.

Deciding between Windows Application and Windows Service

You can install the Exchange Gateway as a Windows application or a Windows service.

When you install the Exchange Gateway as an application, it can be manually started by a user or it can be added to a user's Startup folder so that it starts automatically when the user logs in to the Windows machine. When running as an application, the Exchange Gateway displays a console on the Windows machine where you can monitor and control the gateway.

When you install the Exchange Gateway as a service, it can be configured to start automatically when the server starts and must run under a specific Windows user account that has rights to run services. When running as a service, the Exchange Gateway does not display a user interface on the Windows machine.

If you want to run the Exchange Gateway as a service and if the domain it belongs to is on a NetWare server (Item 3: Domain Server Type), you must create an eDirectory account with a username and password that match the Windows user account. The eDirectory user must have Read, Write, Compare, Edit, Modify, and File Scan rights to the domain\wpgate\exchange directory.

Deciding How to Monitor the Exchange Gateway

If you install the Exchange Gateway as an application, the Exchange Gateway console is displayed on the Windows machine where the Exchange Gateway is running, which allows you to monitor the Exchange Gateway from that location. If you install the Exchange Gateway as a service, the Exchange Gateway console is not displayed, so you must plan for another way to monitor it.

• Using the Exchange Gateway Web Console
• Using an SNMP Monitoring Program

Using the Exchange Gateway Web Console

The Exchange Gateway Web console enables you to monitor and control the Exchange Gateway from any location where you have access to a Web browser and the Internet. This provides substantially more flexible access than the Exchange Gateway console or an SNMP monitoring program.

Using an SNMP Monitoring Program

If desired, you can monitor the Exchange Gateway from the Management and Monitoring component of Novell ZENworks^® for Servers, ManageWise^®, or any other SNMP management and monitoring program. When properly configured, the Exchange Gateway sends SNMP traps to network management consoles for display along with other SNMP monitored programs.

You must enable SNMP during gateway installation. You cannot add this functionality after installation. In order for the option to be offered during installation, the Windows machine where you install the gateway must have the SNMP service installed.

The SNMP service is usually not included during the initial Windows operating system installation. To add or configure the SNMP service on the machine where you plan to install and run the Exchange Gateway, you must be logged in as a member of the Administrator group.

To add the SNMP service to a Windows NT machine:

1. From the Control Panel, double-click Network.

2. Click Services, click Add, then select SNMP Service.

3. Follow the on-screen prompts. You need your original Windows NT media.

   You are given the opportunity to configure the SNMP service. The only required information for the Exchange Gateway is the Trap Destination and Community Name.

4. After the installation is complete, reboot the Windows NT machine.

   For more information about configuring the SNMP service, see your Windows NT documentation.

To add the SNMP service to a Windows 2000 machine:

1. From the Control Panel, double-click Add/Remove Programs.

2. Click Add/Remove Windows Components.

3. Select Management and Monitoring Tools.

4. Click Details, then select Simple Network Management Protocol.

5. After the installation is complete, reboot the Windows 2000 machine.

   For more information about configuring the SNMP service, see your Windows 2000 documentation.

Gathering Exchange System Information

If you are using Exchange 5.5, you must know the name of the Exchange 5.5 site where you want to create the Exchange mailbox through which messages will flow to and from the GroupWise system.

If you are using Exchange 2000, you must know the name of the Exchange 2000 server, along with the name of the mailbox store where you want to create the Exchange mailbox and the name of the storage group where the mailbox store is located. You must also know the administrative group and routing group that the server belongs to.

In either case, you must have a list of all servers in your Exchange system. The Exchange Gateway needs to be installed on only one Exchange server, but the addressing components must be installed on all Exchange servers. The addressing components generate GroupWise-type addresses for Exchange users.

Determining Connections between Systems

To facilitate addressing of messages between systems, you must set up a representation of the Exchange system in your GroupWise system and a connector to your GroupWise system in your Exchange system.

In GroupWise, non-GroupWise systems are represented by non-GroupWise domains. When you first start the Exchange Gateway, the non-GroupWise domain for the Exchange system is created automatically. By default, it is named after the Exchange organization. Under the non-GroupWise domain for the Exchange system, an external post office is automatically created for the Exchange site or administrative group on the Exchange server. By default, it is given the same name as the Exchange site or administrative group. If necessary, you can specify different names for the non-GroupWise domain and external post office.

In Exchange, non-Exchange systems link to the Exchange system through connectors. On the Exchange side, you might want to call the Exchange Gateway GroupwiseConnector, because it connects the Exchange system to GroupWise.

Selecting User Address Type and Format

By default, every Exchange user will have a GroupWise-type address with the following format:

GWise:domain.post_office.user_ID

GWise is the default Exchange address type created for the GroupWise system. You can change it if needed.

Exchange user addresses are generated automatically when you start the Exchange Gateway, using the format shown above. As described earlier, the Installation program maps the name of the Exchange organization to the GroupWise domain portion of the address, the name of the Exchange site or administrative group on the server to the post office portion of the address, and the Exchange user mailbox name to the GroupWise user ID portion of the address.

The recommendation is to use Exchange mailbox names as GroupWise user IDs. However, if this is not possible for some reason, the following variables can be used to specify the information you want to appear in the GroupWise user IDs:

Preferably, the GroupWise user IDs should include the Exchange mailbox names along with whatever other information you want to provide. For example, "%m_%d" would create GroupWise user IDs that consist of the Exchange mailbox names and users' display names.

Determining Where to Install the Exchange Gateway Administrator Snap-In to ConsoleOne

Exchange Gateway administration is performed through ConsoleOne^®, version 1.3.4 or later. When you install the Exchange Gateway, the Gateway Administrator snap-in files can be copied to a ConsoleOne location that you specify. The Gateway Administrator snap-in files extend the functionality of ConsoleOne to let you administer the Exchange Gateway.

You must install the Gateway Administrator snap-in files to an installation of ConsoleOne on an Exchange server where the GroupWise Administrator snap-ins have already been installed. The Gateway Administrator snap-in cannot be installed to a workstation nor can it be used without the GroupWise Administrator snap-ins.

You can install the Gateway Administrator snap-in files to additional Exchange servers after you have installed the gateway, as described in Installing the Exchange Gateway Administrator Snap-In to ConsoleOne.