Novell Home

Cluster Enabling The GroupWise API Gateway

Novell Cool Solutions: Feature
By Stuart Park

Digg This - Slashdot This

Posted: 21 Jul 2005
 

Introduction

Some time ago we embarked on a VoIP (Voice over IP) project that ties into our email system, being GroupWise 6, at the software end we chose Topcall as our preferred solution. Part of this project involved setting up the GroupWise API Gateway (GWAPI) as the link from Topcall to GroupWise and back.

We run our GroupWise environment in a NetWare cluster and were therefore looking to cluster enable the GWAPI to gain the benefits that Cluster Services provide. A search through the Novell TIDs produced this hit: http://support.novell.com/cgi-bin/search/searchtid.cgi?/10068085.htm

Being told it cannot be done means we will try and make it happen. This document is a result of research and testing into making this possible, it also includes settings that are needed for a specific Topcall install.

Prerequisites

First set up a clustered GroupWise domain as the GWAPI ties in with the domain directory structure. This document doesn't cover the setting up of a clustered domain; see Novell's documentation for this.

For this document the following names and directory paths have been used:


Vitrual server CLQANDOMAIN
Volume DOMAIN
Domain root \\CLQANDOMAIN\DOMAIN\QAGWDOM\
GWAPI root \\CLQANDOMAIN\DOMAIN\QAGWDOM\WPGATE\API\
Domain name QAGWDOMAIN
GWAPI name QAGWAPI
MTA IP 10.1.200.24

Files, Utilities & Links

GW41API2 - GWAPI install
http://support.novell.com/servlet/filedownload/pub/gw41api2.exe

FGWAPI5 - GWAPI patch
http://support.novell.com/servlet/filedownload/pub/fgwapi5.exe

GW55API.PDF - GWAPI documentation
http://www.novell.com/documentation/gw55/pdfdoc/gw55api/gw55api.pdf

GWAPI online documentation
http://www.novell.com/documentation/gw55/index.html?page=/documentation/gw55/gw55api/data/a20gkue.html

Stuffkey utility
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2948742.htm

GWAPI NLM Installation

Make sure the volume is mounted and the cluster resource is online.

Copy the GWAPI install files to the clustered volume:

DOMAIN:\API-INST\41API2\API.S01
DOMAIN:\API-INST\41API2\API.SPN
DOMAIN:\API-INST\41API2\API41SCN.TXT
DOMAIN:\API-INST\41API2\GW41API2.TXT
DOMAIN:\API-INST\41API2\INSTALL.DAT
DOMAIN:\API-INST\41API2\PINSTALL.FIL
DOMAIN:\API-INST\41API2\PINSTALL.NLM

Run the PINSTALL.NLM from the console:

DOMAIN:\API-INST\41API2\PINSTALL.NLM

Once loaded the default screen will look as follows:

Complete the screen with the necessary directory paths. The Shared NLM and Load Script directories have been made the same to save on NetWare search paths.

If errors occur recheck the directory paths are correct on the install screen and by browsing the file system. Once successful check the contents of:

\\CLQANDOMAIN\DOMAIN\QAGWDOM\WPGATE\API\

This should now contain some files and directories that were not present before.

Next the GWAPI will need to be set up and configured. This in theory should be performed through NWAdmin however I'd rather configure what I can with ConsoleOne then finish with NWAdmin what ConsoleOne doesn't allow.

Patch GWAPI With FGWAPI5

Once installed replace the following files with the files included in the patch:

\\CLQANDOMAIN\DOMAIN\QAAPI\NGWLIB.NLM
\\CLQANDOMAIN\DOMAIN\QAGWDOM\WPGATE\API\NGWAPI.FIL
\\CLQANDOMAIN\DOMAIN\QAGWDOM\WPGATE\API\NGWAPI.NLM

ConsoleOne Configuration

Load ConsoleOne (with GroupWise snapins) and connect to the Domain where the GWAPI will be installed. Browse to the Domain object through the DS view (not the GroupWise view).

Create GWAPI

Right-click the Domain object, select, New > Object?
Select, GroupWise Gateway and hit OK.

Select Gateway, click OK and complete the details required:

  • Choose a name for the Gateway
  • The Gateway Home Directory should be what was set during the install, the default is API
  • Select, API as Gateway Type
  • Make sure 4.x is selected for the version, regardless of the main GroupWise system, for example, this is being installed into a GroupWise 6 system
  • Select, Define additional properties

Identification Settings

The Identification options should reflect some of the options chosen in the previous set up screen. Description, Alias Type, etc maybe added if wished.

Gateway Time Settings

The Gateway Time Settings have been left as defaults, down to user preferences.

Log Settings

It is highly recommended to set up logging. Given the cluster volume contains ample space I would recommend saving logs into the API directory (a LOGS directory will have to be created first). Also the Log File Age and Log Disk Space may need to be increased to capture a greater period of logs.

Optional Gateway Settings

Within the Optional Gateway Settings make sure the following are set. These settings are specific to the Topcall interface, set as necessary.


Directory Sync/Exchange None
Convert Status to Message No
Outbound Status Level Full
Enable Recovery Yes
Correlation Enabled Yes
Correlation Age 31

Other Settings

Other properties within the GWAPI that can be set, but are not required are:

  • Gateway Administrators
  • Gateway Aliases
  • SSL

Select OK the save the changes made.

NWAdmin Configuration

There are two options screen that do not feature within ConsoleOne, for these NWAdmin will need to be used. Launch NWAdmin (with GroupWise snapins) and browse to the GWAPI object from the DS view.

Required Parameters Settings

Within the details of the GWAPI select Required Parameters. In the Root Directory boxes enter the following path (note that a UNC path will not work, only a path from the volume):

DOMAIN:\QAGWDOM\WPGATE\API\

Set the Addressing Format to Component (Not GroupWise), this is another specific Topcall setting.

Output Conversions Settings

Under Output Conversions confirm the Output Character Set is ASCII Text, this should be set by default.

Select OK to confirm these settings. The GWAPI configuration should now be complete.

Stuffkey Configuration

One problem with the GWAPI is the fact it prompts the user for conformation when trying to unload. To introduce this into a cluster environment the process will have to be fully automated. Novell's Stuffkey utility can be used to automatically force characters onto the System Console to answer prompts.

Copy the STUFFKEY.NLM to the cluster volume:

\\CLQANDOMAIN\DOMAIN\STUFFKEY\STUFFKEY.NLM

Create a file for the Stuffkey utility to use, this will run the necessary commands and respond to the prompts that the GWAPI will produce. The file will looks as follows:

# Auto unload GWAPI
<screen=System Console>
unload address space = qagwdom ngwapi<cr>
Y
# Wait for 2 seconds
<2000 pause>
unload address space = qagwdom ngwlib<cr>
# Wait for 1 seconds
<1000 pause>

Save this file into the following location:

\\CLQANDOMAIN\DOMAIN\STUFFKEY\ULDGWAPI.TXT

Cluster Script Configuration

Load Script

The following is the original cluster script to load the MTA, the lines in blue are added to load the GWAPI. Note the MTA and GWAPI loads into the same address space.

nss /poolactivate=QANDOMAIN
mount DOMAIN VOLID=252
CLUSTER CVSBIND ADD CLQANDOMAIN 10.1.200.24
NUDP ADD CLQANDOMAIN 10.1.200.24
AFPBIND ADD CLQANDOMAIN 10.1.200.24
add secondary ipaddress 10.1.200.24

search add domain:\system
search add domain:\qaapi
load address space = qagwdom domain:\system\gwmta @qagwdoma.mta
load address space = qagwdom domain:\qagwdom\wpgate\api\ngwapi @ngwapi.prm
protection restart qagwdom

Unload Script

domain:\stuffkey\stuffkey domain:\stuffkey\uldgwapi.txt
delay 6

unload address space = qagwdom
del secondary ipaddress 10.1.200.24
CLUSTER CVSBIND DEL CLQANDOMAIN 10.1.200.24
NUDP DEL CLQANDOMAIN 10.1.200.24
AFPBIND DEL CLQANDOMAIN 10.1.200.24
nss /pooldeactivate=QANDOMAIN /overridetype=question

Complete Configuration

Offline and online the cluster resource, it should load as follows:

The System Console showing the MTA and GWAPI loading without errors:


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell