Chapter 4: Install the Gateway
To install the gateway files, select the correct platform for your version of the gateway.
Install
the NLM Gateway Files
Before you can install the gateway, make sure you have access to the
GroupWise* domain database and dirrectory structure. The Install program
copies gateway files to the subdirectories listed under the domain.
To install the NLM* gateway files,
F3: Specify the path on the local server you want to install from.
F4: Specify the path on a remote workstation you want to install from.
Enter: Press Enter to install the files from the A drive of the local server. The disk should already be in the drive.
Do not start the gateway until after you configure it using NetWare Administrator. See Create the Gateway later in this chapter for more information.
Install
the OS/2 Gateway Files
To install the OS/2** version of the gateway, you must install the
gateway files to the domain directory where you want the gateway to
reside. The install program can run only under OS/2.
At this point, the gateway is installed. If you created the folder, the folder appears on your OS/2 desktop.
Do not try to start the gateway at this time. You must first set up the gateway using NetWare Administrator. See Create the Gateway below for more information.
After the gateway files have been installed, you must add the gateway object to the NDS* tree and configure the gateway.
To create the gateway in NDS,
Before you can start the gateway, you must define the gateway information. See Define Gateway Information below for more information.
After creating the gateway object in the NDS tree, you must complete the Gateway Information page in NetWare Administrator.
RSCS Node ID: Enter the RSCS Node ID from item #9 on the Worksheet. In this example, VM1 is used.NWSAA Parameters: Complete the following fields if you are using the NLM version of the gateway or if you are using NetWare for SAA as the communications link.
RSCS APPLID: Enter the RSCS APPLID from item #10 on the Worksheet. In this example, RSCSVM1 is used.
RSCS Link ID Enter the RSCS Link ID from item #11 on the Worksheet. In this example OVVMNJE1 is used.
VTAM Logmode: Enter the VTAM Logmode from item #1 on the Worksheet. In this example RSCSNJE1 is used.
User ID: If you used CSCON to authorize one or more users to administer NetWare for SAA, you must include one of those users in this field. If you did not authorize any users, enter the name of any NetWare user ID.
Password: Enter the NetWare password for the user included in the NetWare User ID field.
Server ID: Enter the name of the NetWare server where the gateway resides.
LU Name: Enter the NWSAA LU name created through CSCON. This name is created by CSCON. Do not confuse this value with the VTAM LU name used in the Major Node Definition on the mainframe.
Start
the NLM Gateway
With the gateway software installed and configured, and the gateway
defined to the mainframe, you are ready to start the gateway. Before
starting the gateway make sure the Message Transfer Agent, is running and
COMMEXEC.NLM, and NWSAA.NLM are loaded on the NetWare server.
Standard SyntaxThe /home option is required. It indicates the location of the gateway directories and files.
To start the gateway, use the following syntax at the NetWare system console. In the following syntax example, the gateway directory is J:\HEADQ\WPGATE\OVVM41, the NLM resides in SYS:\OVVM41, and both reside on the same server.
load sys:\ovvm41\ovvm /home-sys:\headq\wpgate\ovvm41
Reduced Syntax
You can reduce the startup syntax by completing the following:
- Including a search path pointing to the location of OVVM.NLM in AUTOEXEC.NCF
- Copying OVVM.NLM to SYS:SYSTEM
- Copying OVVM.NLM to a search path
The syntax is then reduced to:
load ovvm /home-sys:\headq\wpgate\ovvm41
Simplified Syntax
You can reduce the syntax further by creating a startup file called OVVM.CFG. A startup file is an ASCII file that includes at least one startup option. For a list of startup options, see Appendix B: Startup Switches. Place the startup file in the same directory with the NLM.
When you start the gateway, the file server displays the gateway operation screen. See Chapter 11: Monitor Gateway Operations for more information about the operation screen.
Start
the OS/2 Gateway
Before starting the gateway make sure the Message Transfer Agent is
running. You can start the gateway by using the OS/2 icon or from the OS/2
command line. Regardless of how you choose to start the gateway, you must
use the /home startup switch. For more information about the startup
switches, see Appendix B: Startup
Switches.
Start Gateway Using the OS/2 Icon
- Double-click the GroupWise Gateways folder icon.
- Double-click the OVVM Gateway icon.
When you start the gateway, the file server displays the gateway operation screen. See Chapter 11: Monitor Gateway Operations for more information about the operation screen.
Start Gateway from Command Prompt
- Open an OS/2 window.
- Change to the gateway directory. In this example, C:\OVVM41 is used.
You must use the /home startup switch to run the gateway from the command line. The /home switch points the gateway to the gateway directory \WPGATE on the network. To use the /home switch, the syntax is:ovvm /home-path to gateway directoryThe syntax for the sample system is:ovvm /home-j:\headq\wpgate\ovvm
When you start the gateway, the file server displays the gateway operation screen. See Chapter 11: Monitor Gateway Operations for more information about the operation screen.
* Novell trademark. ** Third-party trademark. See Trademarks for more information.