Microsoft KB Archive/899107

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:24, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 899107

Article Last Modified on 10/25/2007


APPLIES TO

  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition


INTRODUCTION

The Novell GroupWise 4.1 Applications Programming Interface (API) gateway is an optional component that you can add to a working Novell GroupWise system. The API gateway provides an open interface to GroupWise 4.1 and to GroupWise 5.0 systems by using structured ASCII text files. These text files are made up of keywords that you can use to perform administrative tasks on your GroupWise system and to communicate with e-mail systems that are not Novell systems.

Before you start, you must install the Novell Netware Client 4.91 (Clnt491e.exe) on the Microsoft Exchange Server 2003 Service Pack 1 (SP1) computer that hosts the Microsoft Exchange Connector for Novell GroupWise. To obtain the Novell NetWare Client, visit the following Novell Web site:

http://download.novell.com/


Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
back to top

MORE INFORMATION

Install and Configure the GroupWise 4.1 API gateway NLM with Patch 5

Install the GroupWise 4.1 API gateway NLM with Patch 2

The GroupWise Patch 2 for API Netware Load Module (NLM) and OS/2 is included with the GroupWise 4.1 API gateway in one downloadable file (Gw41api2.exe file). To obtain the GroupWise 4.1 API gateway NLM with Patch 2, visit the following Novell Web site:

http://support.novell.com/servlet/filedownload/pub/gw41api2.exe


Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

  1. Download and extract the GroupWise 4.1 API gateway NLM with Patch 2 files to a temporary folder on the NetWare server. For example, extract the files to the Sys:Temp\Nlm folder.
  2. In the NetWare System Console, type load path:pinstall. In this step, path is the location of the GroupWise API gateway files.

    For example, type load sys:temp\api\pinstall.
  3. Make sure that the Install From box contains the installation path from which the Pinstall.nlm file was loaded.
  4. In the Domain Path box, type the path of the GroupWise domain in which you want to install the gateway. The domain path uses the following format:

    Volume:Path_to_groupwise_domain

  5. Confirm that the following default values appear.

    Note The following default values are correct for all standard NetWare installations. Do not change these values unless you have a customized installation.
    • The default value for the Gateway Directory box is api.
    • The default value for the Gateway NLMs box is sys:\gwdomain\wpgate\api. This value is the path of the GroupWise domain API folder.
    • The default value for the Shared NLMs box is sys:\system.
    • The default value for the Load Script box is sys:\system.
  6. Click Install to install the gateway.
  7. When the installation of the gateway has completed, press the ESC key until the NetWare System Console is displayed.

    Do not start the gateway before you use the NetWare Administrator tool to configure the gateway.

back to top

Install Patch 5 for the API gateway

To upgrade the API gateway to Patch 5, you must perform a file replacement. To do this, follow these steps:

  1. Download Patch 5 for the API gateway from the following Novell Web site:

    http://support.novell.com/servlet/filedownload/pub/fgwapi5.exe

    Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
  2. Extract the files to a temporary folder on the Novell server.
  3. Establish a connection to the NetWare server, and then copy the Ngwapi.fil file and the Ngwapi.nlm file to the Volume:Domain\Wpgate\Api folder.
  4. Click Replace the files when you are prompted.
  5. Copy the Ngwlib.nlm file to the Sys:\System folder.
  6. Click Replace the files when you are prompted.

back to top

Enable GroupWise distribution list expansion

  1. Locate the Ngwapi.prm file in the API folder of the GroupWise domain in which the API gateway was installed. For example, the Ngwapi.prm file may be located in the Sys:\Gwdomain\Wpgate\Api folder.
  2. Use either Notepad in Microsoft Windows or Edit in NetWare to open the Ngwapi.prm file.
  3. Find the line that contains the following text:

    ;/group

  4. Remove the semicolon from this text.
  5. Save the file.

back to top

Add and configure the API gateway object

After the installation of the GroupWise API Gateway NLM files has completed, use the NetWare Administrator tool to configure an API gateway object in your GroupWise system:

  1. Start the NetWare Administrator tool, and then click the GroupWise domain in which you want to install the connector.
  2. On the Object menu, click Create.
  3. In the Class of new object list, click GroupWise Gateway/Internet Agent, and then click OK.
  4. In the Create GroupWise Gateway/Internet Agent dialog box, configure the following settings:
    1. At the top of the dialog box, click Gateway.
    2. In the Gateway Name box, type a name that is unique in your GroupWise domain. For example, type ExchangeLink.
    3. In the Gateway Home Directory list, click the name of the gateway.
    4. In the Language list, click English-US.
    5. In the Time Zone list, click the correct time zone.

      By default, the gateway assumes the time zone of its domain. However, you can select a different time zone if the gateway is installed on a computer that is in a different time zone.
    6. In the Version list, click the version number of the API gateway. For example, click 4.X.
    7. In the Platform list, click the correct platform. For example, click NetWare Loadable Module.
    8. In the Gateway Type list, click the correct gateway type. For example, click API.
    9. Click to select the Define additional properties check box, and then click Create.
  5. In the GroupWise Gateway/Internet Agent:API dialog box, confirm the following settings:
    1. Make sure that Information is selected (it is selected by default).
    2. In the Database Version list, make sure that 4.X is selected.
    3. In the Platform list, make sure that NetWare Loadable Module is selected.
    4. In the Gateway Type list, make sure that API is selected.
    5. In the Gateway Alias Type box, accept the default setting. By default, the Gateway Alias Type box is blank.
    6. In the Foreign ID box, accept the default setting. By default, the Foreign ID box is blank.
    7. In the UNC Path box, accept the default path.
  6. Click Optional Gateway Settings, and then click Exchange in the Directory Sync/Exchange list. Leave the default settings in the remaining boxes.
  7. Click Required Parameters.
  8. Under Gateway File Paths, view the paths that are listed in the Root Directory for Gateway Messages box and in the Root Directory for Directory Services Messages box. These paths use the mapped drive format. Change these paths to absolute paths that use the Volume:\Path format. For example, change one path to Sys:\Groupwisedomain\Wpgate\Api.

    Note The paths must use the Volume:\Path format. And, you must change the paths in both boxes.
  9. In the Addressing Format list, click Component.

    To verify that this value has been set, quit the NetWare Administrator tool, restart the NetWare Administrator tool, and then review the properties of the API gateway object.
  10. Click Gateway Time Settings, and then configure the following settings:
    • In the Idle Sleep Duration box, set the value to 5 seconds or less.
    • Accept the default values for the remaining boxes, and then click OK.
  11. Verify that the /home switch setting in the Ngwapi.prm file is correct.

    The Ngwapi.prm file is an ASCII text file that contains the parameters for starting the API gateway. Use any text editor to open the file. All the options in this file are commented out except for the /home switch. The /home switch contains the path of the gateway home directory. Make sure that the path uses the following format:

    /Home-volume:\GroupWise_domain\Wpgate\API

    For example, the switch contains the following path:

    /Home-sys:\GroupWise_domain\Wpgate\Api

back to top

Load the API gateway

Start a Server Console on the NetWare server that hosts the API gateway. To do this, use the load' command to start the API gateway. The load statement takes an argument in the following form: '

volume:\groupwise_domain\wpgate\api\ngwapi @ngwapi.prm


For example, use the following load' command: '

load sys:\groupWise_domain\wpgate\api\ngwapi @ngwapi.prm


To view the running processes on the server after the API gateway starts, press CTRL+ESC, and then type the number for the process at the prompt.

We recommend that you add the load command to the Grpwise.ncf file that is located in the Agents folder of the GroupWise post office. When you do this, the gateway automatically starts when the server restarts.

back to top

Add an external foreign domain for the Exchange system

The GroupWise system requires a means to route to the foreign system and to route from the foreign system. In this case, the GroupWise system routes to the Exchange system. Exchange is represented as a non-GroupWise domain. An instance of the API gateway is used to route mail between the foreign domain and the GroupWise domain that is used as the gateway to the GroupWise system.

Add a non-GroupWise domain

  1. In ConsoleOne, right-click GroupWise System, and then click New Non GroupWise Domain.
  2. Type a name to represent the Exchange system.


The external domain name must match the domain part of the GroupWise proxy address in the recipient policy that is used to provide GroupWise addresses to the Exchange system. The domain part is the first part of the GroupWise proxy address. You can change the name of the domain by editing the GroupWise proxy address on the E-Mail Addressing tab of the recipient policy. The default domain for the Exchange organization is "Exchange".

  1. In the Domain Type box, click External Foreign.
  2. In the Database Version box, click 4.x. This value must match the API gateway version.
  3. Confirm that the value in the Time Zone box is set to the same time zone that is used by the Exchange computer that is running the Connector for Novell GroupWise.
  4. Click Create.
  5. Right-click the non-GroupWise domain, and then click New External Post Office.
  6. Type a name in the Post office name box.


This name must correspond to the second part of the GroupWise proxy address that is used in the Exchange recipient policy. The Exchange recipient policy default name is “First Administrative Group”. This name can be simplified. For example, you can type EXPO in the Post office name box.

back to top

Configure the link table

  1. In ConsoleOne, click the GroupWise domain that will act as the GroupWise system link to the Exchange system. This domain contains the API gateway.
  2. Right-click GroupWise System, and then click GroupWise Utilities Link Configuration.
  3. Click the GroupWise domain, and then double-click the Exchange domain.
  4. In the Link Type box, click Gateway.
  5. In the Gateway Link box, click the API gateway that you added to service the Exchange system.
  6. Leave all other settings set to the default setting, close the Link Configuration Tool, and then save changes when you are prompted.

back to top

Add a NetWare account for the Exchange Router for GroupWise

The Connector for Novell GroupWise must have Read, Write, Execute, Create, Modify and Filescan rights to the API folder and to all the subfolders of the API folder. The Microsoft Exchange GroupWise Router service uses this NetWare identity when the service sends and retrieves mail to the GroupWise API gateway.

  1. Open ConsoleOne, right-click the context in which the GroupWise API gateway resides, and then click New User.
  2. In the Name box, type a name for the Exchange account.
  3. In the Surname box, type a value. We suggest that you type Service.


A surname is required to save the object.

  1. Click to select the Define additional properties check box, and then click OK.
  2. Type a password for the account, and then click OK.
  3. In the Properties dialog box, click the Rights to Files and Folders tab.
  4. Click Show, and then click the volume in which the API gateway is installed.
  5. Click Add, and then locate the API folder.
  6. Click to select the following check boxes:
    • Write
    • Execute
    • Create
    • Modify
    • Filescan
  7. Click Apply, and then click OK.

back to top

Configure the Connector for Novell GroupWise to use the NetWare account

  1. Start Exchange System Manager, right-click Connector for Novell GroupWise, and then click Properties.
  2. In the API Gateway Path box, type the UNC path to the API gateway on the NetWare server.

    The path uses the following format:

    \\server\volume\groupwise_domain\wpgate\api

  3. Click Modify, and then type the NetWare account that is made for the Connector for Novell GroupWise.
  4. Type and then confirm the password for the NetWare account.
  5. Configure the Import container to point to the organizational unit in which the objects that represent GroupWise users will be added.
  6. Configure the Export container to point to the organizational units that contain Exchange Users objects that will be exported to the GroupWise system.
  7. In the Address space box, type a wildcard character (*).
  8. Click Apply, and then click OK.
  9. Close the Connector for Novell GroupWise properties, and then start the following services:
    • Microsoft Exchange Connectivity Controller
    • Connector for Novell GroupWise
    • Microsoft Exchange Router for Novell GroupWise

back to top

Keywords: kb3rdparty kbconfig kbexpertiseadvanced kbhowtomaster KB899107



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/899107&oldid=214769’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki