Rules and Formatter Extension for WebSphere Business Integration Message Broker for Multiplatforms and z/OS V5

Rules and Formatter Extension for WebSphere Business Integration Message Broker for Multiplatforms and z/OS V5.0

Welcome to the Rules and Formatter Extension for WebSphere Business Integration Message Broker (WBI). This install guide contains information you need to successfully install and uninstall Rules and Formatter Extension for WBI on multiplatforms and z/OS.

Contents

¨ Special Instructions and Information

¨ Installing Rules and Formatter Runtime Engine (Server)

- Prerequisites

- Supported Platforms

- Disk Space and Memory Requirements

- Preparing the Installation Environment

- Installation Instructions

¨ Installing Rules and Formatter Design-Time Tooling (Client)

- Prerequisites

- Supported Platforms

- Disk Space and Memory Requirements

- Preparing the Installation Environment

- Verifying Connectivity

- Installation Instructions

¨ Launching the Rules and Formatter Extension for WBI GUIs

¨ Uninstalling Rules and Formatter Runtime Engine (Server)

- Locating the Uninstall Application

- Uninstallation Instructions

¨ Uninstalling Rules and Formatter Design-Time Tooling (Client)

- Locating the Uninstall Application

- Uninstallation Instructions

¨ Console (Non-GUI) Mode Installation and Uninstallation

- Installation Instructions

- Uninstallation Instructions

¨ Silent Mode Installation and Uninstallation

- Installation Instructions

- Uninstallation Instructions

¨ z/OS Installation and Uninstallation

- Installation Instructions

- Uninstallation Instructions

Special Instructions and Information

You should read the “ReadMe” file provided on the Rules and Formatter Extension for WBI install CD-ROM prior to installing the product. The ReadMe is located at the root (or top) level directory of the CD-ROM and contains the latest information about the Rules and Formatter Extension for WBI product. The information contained in the ReadMe may contain product installation and uninstallation related material.

On all platforms, you should install WebSphere Business Integration Message Broker for Multiplatforms and z/OS V5.0 (WBI) before installing the Rules and Formatter Extension for WBI.

You should install Rules and Formatter Extension for WBI as a user with “administrator” privileges on Windows and as the root user on all other platforms.

Rules and Formatter Extension for WBI consists of a separately installable client and server. The proper name of the client is Rules and Formatter Design-Time Tooling. The proper name of the server is Rules and Formatter Runtime Engine. The terms client, server, and the corresponding proper names are used interchangeably throughout this document.

When the term “Linux” is used in this guide, it refers to all supported types of Linux. When addressing a specific type of Linux, the text will be more descriptive. For example, “Linux(s390)” is used to refer to platforms running the Linux operating system on the s390 architecture and “Linux(Intel)” is used to refer to platforms running Linux on an Intel-based architecture.

Throughout this guide, <install_directory> refers to the default installation directory.

On HP-UX, Solaris, and Linux, the default installation directory is /opt/mqsi. The installation does not allow you to install to a location other than the default for these platforms.

On AIX, the default installation directory is /usr/opt/mqsi. The installation does not allow you to install to a location other than the default on AIX.

On z/OS, the default installation directory is /usr/lpp/wmqi/nnsy

On Windows, the Rules and Formatter Extension for WBI client and server install applications will detect where you chose to install WebSphere Business Integration Message Broker for Multiplatforms. The default install location for WebSphere Business Integration Message Broker for Multiplatforms is “C:\Program Files\IBM\WebSphere Business Integration Broker”. Therefore, the default install location for Rules and Formatter Extension for WBI should be “C:\Program Files\IBM\WebSphere Business Integration Broker” as well.

However, if the Rules and Formatter Extension for WBI install application cannot determine that WebSphere Business Integration Message Broker for Multiplatforms is installed on the machine and its location, then the default install location for Rules and Formatter Extension for WBI will be set to the directory from which the install application (setup.exe) was launched.

In this case, you should exit if WebSphere Business Integration Message Broker for Multiplatforms is not installed on the machine, install WebSphere Business Integration Message Broker for Multiplatforms, and then restart the Rules and Formatter Extension for WBI install application.

In the unlikely case where the Rules and Formatter Extension for WBI install application sets the default location to the directory from which the install application (setup.exe) was launched – even though WebSphere Business Integration Message Broker for Multiplatforms is installed on the machine, then change the default location to the location where WebSphere Business Integration Message Broker for Multiplatforms is installed and continue with the installation process.

Installing Rules and Formatter Runtime Engine (Server)

Note: z/OS installation instructions can be found at the end of this document.

Prerequisites

· WebSphere Business Integration Message Broker for Multiplatforms V5.0

· DBMS listed in supported platforms

Supported Platforms

Operating System

DBMS

Compiler

Windows NT 4.0 (Service Pack 6A)

Windows 2000 (Service Pack 2)

Windows XP Pro (Service Pack 1)

Microsoft SQL Server 7.0 (SP 4)

Microsoft SQL Server 2000 (SP3)

Oracle 9i r.2

Sybase ASE 12.5

DB2 UDB 7.2 (Fix Pack 8)

DB2 UDB 8.1 (Fix Pack 2)

Microsoft Visual C++
Version 6.0 (Service Pack 5)

Solaris 2.8

Oracle 9i r.2

Sybase ASE 12.5

DB2 UDB 7.2 (Fix Pack 8)

DB2 UDB 8.1 (Fix Pack 2)

Sparcworks C++

Compiler Version 6.0

(update 1)

HP-UX 11

HP-UP 11.11

Oracle 9i r.2

Sybase ASE 12.5

DB2 UDB 7.2 (Fix Pack 8)

DB2 UDB 8.1 (Fix Pack 2)

HP11aC++

Version A.03.27

HP11 C Compiler

Version B11.01.20

(Bundle B3901BA)

AIX5.1 (plus Maintenance Level 3)

Oracle 9i r.2

Sybase ASE 12.5

DB2 UDB 7.2 (Fix Pack 8)

DB2 UDB 8.1 (Fix Pack 2)

VisualAge C++ Professional for AIX Version 5.0.2.2

z/OS 1.4

DB2 7.1

OS/390C/C++ Compiler

Linux (Intel)

Linux Z Series (s390)

DB2 7.2

DB2 8.1

gcc Compiler 2.9.5.4

Disk Space and Memory Requirements

Installation Media: CD-ROM

Main Memory: 512 MB

Hard Disk Space:

Windows: 165 MB

Solaris: 260 MB

HP-UX: 420 MB

AIX: 270 MB

Linux (Intel): 250 MB

Linux (s390): 200 MB

Note: Half of hard disk space requirement identified above is needed for the installation target directory/drive to hold program files. The other half of the disk space requirement is for the installer to use as a temporary directory/drive

Preparing the Installation Environment

Common Information Model (CIM) Repository

Previous releases used an ASA database for the common information model (CIM) repository that shares installation information across Sybase and New Era of Networks products. The method this release uses to track version and path information for each product installation is the CIMRepository.xml file. This information is used to install patches and to uninstall previous versions of the product. The ASA CIM repository is ignored for the installation of this release. However, uninstall applications from previously released products must start and use the ASA CIM repository.

Temporary Installation Directory

The installer uses a temporary location during the installation process. The default temporary location on Windows is defined in the system environment variables and is usually set to C:\temp. On the other platforms, this is most often /tmp. If enough space is not available in the default temporary location, the installer might not start, or it might start, but notify you that sufficient space is not available. Either case requires providing sufficient space in the temporary directory. You can do one of the following:

· Move or delete files to provide space in the default temporary directory.

· Launch the installer using a different temporary directory.

To install using a temporary directory other than the default:

· For Windows, enter the following

setup -is:tempdir <full path to temp directory on alternate drive>

· For all other platforms, enter the following

setup -is:tempdir <full path to alternate temp directory>

Installation Instructions

The following installation instructions assume you are logged onto the server with administrative rights. When installing on UNIX, it is best to perform the install directly on the target machine in the Common Desktop Environment (CDE) single window mode and as root. Use the CD-ROM to install the Rules and Formatter Runtime Engine.

Insert the CD-ROM.
Start the installer

a. On Windows

1) If installing on Windows NT

· Select Start > Run from the Windows Start menu.

· In the Run dialog box, browse to locate the Microsoft Visual C 6.0 Runtime installer:

<CD-ROM drive>:\msvc-6_0\vcredist.exe

· Click OK and follow the MSVC installation instructions displayed.

2) Select Start > Run from the Windows Start menu.

3) In the Run dialog box, browse to locate the setup file:

<CD-ROM drive>:\setup.exe

4) Click OK.

The Installer Welcome window appears.

b. On Solaris

1) Set the LD_LIBRARY_PATH variable to include:

/opt/mqsi/rfe/bin

2) Create an NNSY_CATALOGUES variable and set it to:

/opt/mqsi/rfe/NNSYCatalogues

3) Mount the CD-ROM.

For example:

pfs_mount <CD DEVICE> /mnt_point

4) Set the DISPLAY.

For example:

export DISPLAY=<IP address:0:0>

5) To change to the /mnt_point directory, enter:

%cd mnt_point

6) To start the installer, enter:

$ ./setupsolaris

The Installer Welcome window appears.

c. On AIX

1) Set the LIBPATH variable to include:

/usr/opt/mqsi/rfe/bin

2) Create an NNSY_CATALOGUES variable and set it to:

/usr/opt/mqsi/rfe/NNSYCatalogues

3) Mount the CD-ROM.

For example:

pfs_mount <CD DEVICE> /mnt_point

4) Set the DISPLAY.

For example:

export DISPLAY=<IP address:0:0>

5) To change to the /mnt_point directory, enter:

%cd mnt_point

6) To start the installer, enter:

$ ./setupaix

The Installer Welcome window appears.

d. On HP-UX

1) Set the SHLIB_PATH variable to include:

/opt/mqsi/rfe/bin

2) Create an NNSY_CATALOGUES variable and set it to:

/opt/mqsi/rfe/NNSYCatalogues

3) Mount the CD-ROM.

Some of the files installed might have names longer than 31 characters or have mixed-case file and directory names, so you must enter the following mount commands:
nohup pfs_mountd &
nohup pfsd &
pfs_mount <CD DEVICE> /mnt_point

4) Set the DISPLAY.

For example:

export DISPLAY=<IP address:0:0>

5) To change to the /mnt_point directory, enter:

%cd mnt_point

6) To start the installer, enter:

$ ./setuphpux

The Installer Welcome window appears.

e. On Linux

1) Set the LD_LIBRARY_PATH variable to include:

/opt/mqsi/rfe/bin

2) Create an NNSY_CATALOGUES variable and set it to:

/opt/mqsi/rfe/NNSYCatalogues

3) Mount the CD-ROM.

For example:

pfs_mount <CD DEVICE> /mnt_point

4) Set the DISPLAY.

For example:

export DISPLAY=<IP address:0:0>

5) To change to the /mnt_point directory, enter:

%cd mnt_point

6) To start the installer, enter:

$ ./setuplinux

The Installer Welcome window appears.

3. To initiate the installation process, click Next on the Installer Welcome window.
The License Agreement window appears.

4. Click the radio button to accept the terms of the license agreement.

Note: If you do not have IBM WebSphere Business Integration Broker components installed, a warning message will appear (on Windows only) to remind you to install WBI before installing Rules and Formatter Extension for WBI.

5. Click Next.
On Windows only, the Installation Directory Window appears.

6. To specify an installation directory on Windows, select one of the following:

· To accept the default directory (the directory in which you installed WBI) click Next.

· If WebSphere Business Integration Broker is installed, but InstallShield is not detecting it, enter the location (default is C:\Program Files\IBM\WebSphere Business Integration Broker) and click Next.

· If you did not install WebSphere Business Integration Broker before starting the Rules and Formatter Extension for WBI, then exit the installation, install WebSphere Business Integration Broker, and then install Rules and Formatter Extension for WBI.

7. The Installation Summary window displays the products to be installed and the approximate required disk space.

8. Click Next.
The Installation Summary window displays installation progress.

9. An Installation Summary window should appear indicating Rules and Formatter Runtime Engine was successfully installed. Click Finish.

Note: The Windows server sets the PATH environment variable to <install_directory>\rfe\rfre\bin.

Installing Rules and Formatter Design-Time Tooling (Client)

This section describes how to install the components required to run Rules and Formatter Design-Time Tooling.

Prerequisites

· WebSphere Business Integration Message Broker for Multiplatforms V5.0

· Rules and Formatter Extension for WBI

· DBMS listed in supported platforms

Supported Platforms

Operating System

DBMS

Windows 2000 (Service Pack 2)

Windows XP Pro (Service Pack 1)

Microsoft SQL Server 7.0 (SP 4)

Microsoft SQL Server 2000 (SP3)

Oracle 9i r.2

Sybase ASE 12.5

DB2 UDB 7.2 (Fix Pack 8)

DB2 UDB 8.1 (Fix Pack 2)

Disk Space and Memory Requirements

Installation Media: CD-ROM

Main Memory: 512 MB

Hard Disk Space: 230 MB

Preparing the Installation Environment

Common Information Model (CIM) Repository

Temporary Installation Directory

The installer uses a temporary location during the installation process. The default temporary location on Windows is defined in the system environment variables and is usually set to C:\temp. If enough space is not available in the default temporary location, the installer might not start, or it might start, but notify you that sufficient space is not available. Either case requires providing sufficient space in the temporary directory. You can do one of the following:

· Move or delete files to provide space in the default temporary directory.

· Launch the installer using a temporary directory on another drive.

To install using a temporary directory other than the default:

· For Windows, enter the following

setup –is:tempdir <full path to temp directory on alternate drive>

Verifying Connectivity

Use the following database checklists to verify connectivity to the new database.

To a Sybase ASE Database

Have the following information available:

· Database name

· Server name

· Name of Sybase ASE user created during the database installation

· Password of Sybase ASE user created during the database installation

Verify the following:

· Database software installation was successfully completed.

· Database server is running in the target environment.

· Connection to the target database server using a Sybase ASE interactive tool (isql) and the account is established.

To an Oracle Database

Have the following information available:

· Service name

· Name of Oracle user created during the database installation

· Password of Oracle user created during the database installation

Verify the following:

· Database software installation was successfully completed.

· Database server is running in the target environment.

· ORACLE_HOME environment variable is set to the root directory of the Oracle installation.

· PATH environment variable points to the $ORACLE_HOME/bin.

· Connection to the target database server using an interactive query tool (sqlplus) and the account is established.

To a Microsoft SQL Server Database

Have the following information available:

· Database name

· Server name

· User name created during the database installation

· Password for user created during the database installation

Verify the following:

· Database software installation was successfully completed.

· Database server is running in the target environment.

· The PATH environment variable includes:

· For MSSQL7: the MSSQL7\BINN directory

· For MSSQL2000: \Microsoft SQL Server\80\tools\binn

· Connection to the target database server using an interactive SQL tool (ISQL) and the account is established.

To a DB2 Database

Have the following information available:

· Database name

· Database owner name

· Database owner password

Verify the following:

· Database software installation was successfully completed.

· Database server is running in the target environment.

· PATH environment variable includes the lib directory for DB2.

· User account that owns objects in the new DB2 database added.

Connection to the database using the DB2 CLP program is established.

Installation Instructions

Rules and Formatter Design-Time Tooling can be installed only on a Windows workstation. The following installation instructions assume you are logged onto the client workstation with administrative rights. These privileges are specifically required to properly install the Rules GUI. If you does not have administrator privileges, the registry is not updated and the Rules GUI will not run. Use the CD-ROM to install the Rules and Formatter Design-Time Tooling.

1. Insert the CD-ROM.

2. Start the installer

3. Select Start > Run from the Windows Start menu.

4. In the Run dialog box, browse to locate the setup file:

<CD-ROM drive>:\setup.exe

5. Click OK.

The Installer Welcome window appears.

6. To initiate the installation process, click Next on the Installer Welcome window.
The License Agreement window appears.

7. Click the radio button to accept the terms of the license agreement.

Note: If you do not have IBM WebSphere Business Integration Broker components installed, a warning message will appear to remind you to install WBI before installing Rules and Formatter Extension for WBI.

8. Click Next.
The Installation Directory Window appears.

9. To specify an installation directory, select one of the following:

· To accept the default directory (if it matches the directory in which you installed WBI) click Next.

· If WebSphere Business Integration Broker is installed, but InstallShield is not detecting it, enter the location where you installed WebSphere Business Integration Broker (the default is C:\Program Files\IBM\WebSphere Business Integration Broker). Click Next. Or, if you have not already installed WebSphere Business Integration Broker, then follow the instructions below.

10. The Installation Summary window displays the products to be installed and the approximate required disk space.

11. Click Next.
The Installation Summary window displays installation progress.

12. An Installation Summary window should appear indicating Rules and Formatter Design-Time Tooling was successfully installed. Click Finish.

13. Reboot the machine.

Note: You can view documentation files through the main WebSphere help browser.

The Windows client sets the PATH environment variable to <install_directory>\rfe\rfdt\gui.

Launching the Rules and Formatter Extension for WBI GUIs

From the Endeavor Broker Perspective menu bar, select NNSY Menu > Formatter or NNSY Menu > Rules. Alternatively, you can open the Formatter or Rules GUIs using the toolbar buttons.

Uninstalling Rules and Formatter Runtime Engine (Server)

The uninstall program removes Rules and Formatter Runtime Engine, but does not remove the folder and miscellaneous files, such as log files and user-created files from the installation directory. After performing the uninstall, you will need to delete the directory and its contents from your machine. The parent directory you should delete is <install_directory>/rfe on platforms other than Windows. On Windows, the parent directory you should delete is <install_directory>\rfe\rfre. Only delete the <install_directory>\rfe directory on Windows if the client is no longer (or never was) installed.

Locating the Uninstall Application

The uninstall program (uninstall.exe on Windows and uninstall on all other platforms) is located in the following directory:

Windows: <install_directory>\rfe\rfre\_uninst

AIX: <install_directory>/rfe/_uninst

Solaris: <install_directory>/rfe/_uninst

HP-UX: <install_directory>/rfe/_uninst

Linux (Intel): <install_directory>/rfe/_uninst

Linux (s390): <install_directory>/rfe/_uninst

Where <install_directory> is /usr/opt/mqsi on AIX and /opt/mqsi on Solaris, HP-UX, and Linux. For Windows, <install_directory> is C:\Program Files\IBM\WebSphere Business Integration Broker, by default, but may be some other location set by you.

Note If, during product installation, the directory containing the uninstall application already exists from a previous install, a numbered directory is created for the uninstall application belonging to the more recent installation. For example, if the product has been installed to the same location twice, on a Windows system you will find: <install_directory>\rfe\rfre\_uninst2

If the product has been installed three times, there will be an _uninst3 directory – and so on. In any case, you should run the uninstall application from the highest numbered directory, if a numbered directory exists.

Uninstallation Instructions

Before uninstalling, move any custom or other files that you want to save from the product directory into another directory.

1. Initiate the InstallShield Wizard for Rules and Formatter Runtime Engine.

a) On Windows, do one of the following:

1) Uninstall using the command prompt

· Change directory (cd) to <install_directory>\rfe\rfre\_uninst

· Type the following and press Enter

.\uninstall.exe

2) Uninstall using Add/Remove Programs

· Open Add/Remove Programs from the Control Panel

· Select Rules and Formatter Runtime Engine

· Select Change/Remove

b) For all other platforms

1) Change directory (cd) to <install_directory>/rfe/_uninst

2) Type the following and press Enter

./uninstall

2. The InstallShield Wizard starts the uninstall process.

3. To initiate the uninstallation process, click Next on the Installer Welcome window.

4. The window displays what you have selected for removal.

5. Click Next to confirm that you want to uninstall.

6. Click Finish when the uninstallation summary window appears.

Note On platforms other than Windows, only the user account used to install the product can properly uninstall the product since the repository file containing product installation/uninstallation information is created at install time in the home directory of the user account used to install the product. This should be the root user account.

Uninstalling Rules and Formatter Design-Time Tooling (Client)

The uninstall program removes Rules and Formatter Design-Time Tooling, but does not remove the folder and miscellaneous files, such as log files and user-created files from the installation directory. After performing the uninstall, you will need to delete the directory and its contents from your machine. The parent directory you should delete is <install_directory>\rfe\rfdt. Only delete the <install_directory>\rfe directory if the client is no longer (or never was) installed.

Locating the Uninstall Application

The uninstall program (uninstall.exe) is located in the following directory:

<install_directory>\rfe\rfdt\_uninst

Where <install_directory> is C:\Program Files\IBM\WebSphere Business Integration Broker, by default, but may be some other location set by you.

If the product has been installed three times, there will be a “3” directory – and so on. In any case, you should run the uninstall application from the highest numbered directory, if a numbered directory exists.

Uninstallation Instructions

Before uninstalling, move any custom or other files that you want to save from the product directory into another directory.

1. Initiate the InstallShield Wizard for Rules and Formatter Design-Time Tooling.

2. Do one of the following:

a) Uninstall using the command prompt

1) Change directory (cd) to <install_directory>\rfe\rfdt\_uninst

2) Type the following and press Enter

.\uninstall.exe

b) Uninstall using Add/Remove Programs

1) Open Add/Remove Programs from the Control Panel

2) Select Rules and Formatter Design-Time Tooling

3) Select Change/Remove

3. The InstallShield Wizard starts the uninstall process.

4. To initiate the uninstallation process, click Next on the Installer Welcome window.

5. The window displays what you have selected for removal.

6. Click Next to confirm that you want to uninstall.

7. Click Finish when the uninstallation summary window appears.

Console (Non-GUI) Mode Installation and Uninstallation

Product installation and uninstallation through normal, GUI mode methods described above are strongly recommended. In fact, console (or Non-GUI) mode installation and uninstallation is recommended only for users experiencing difficulties performing these tasks in the normal, GUI mode.

Installation Instructions

· Read and follow the installation instructions above for normal, GUI mode installation. However, when starting the install application, use the console mode command-line options described below:

· For Windows client or server, enter the following on the command-line:

<CD DEVICE>\setup.exe -is:javaconsole -console

· For all other platforms, enter the following on the command-line:

<CD MNT POINT>/setup -is:javaconsole -console

Uninstallation Instructions

· Read and follow the uninstallation instructions above for normal, GUI mode uninstallation. However, when starting the uninstall application, use the console mode command-line options described below:

· For Windows client or server, enter the following on the command-line:

uninstall.exe -is:javaconsole -console

· For all other platforms, enter the following on the command-line:

uninstall -is:javaconsole -console

Silent Mode Installation and Uninstallation

Product installation and uninstallation through normal, GUI mode methods described above are strongly recommended. In fact, silent mode installation and uninstallation is recommended only for users experiencing difficulties performing these tasks in the normal, GUI mode.

Installation Instructions

· Read and follow the installation instructions above for normal, GUI mode installation. However, when starting the install application, use the silent mode command-line options described below:

· For Windows client or server, enter the following on the command-line:

<CD DEVICE>\setup.exe -silent

· For all other platforms, enter the following on the command-line:

<CD MNT POINT>/setup -silent

Uninstallation Instructions

· Read and follow the uninstallation instructions above for normal, GUI mode uninstallation. However, when starting the uninstall application, use the silent mode command-line options described below:

· For Windows client or server, enter the following on the command-line:

uninstall.exe -silent

· For all other platforms, enter the following on the command-line:

uninstall -silent

Z/OS Installation

This section describes how to install Rules and Formatter Extension for WBI for Multiplatforms on the z/OS platform.

To create two PDS data sets, do the following:
PDSs should be FB 80. If you use half-track blocking, 120 blocks and 10 directory blocks are sufficient.

· Create the same HighLevelQualifiers for both PDS data sets.

· Create a LowLevelQualifier of SBIPJCL for one PDS.

· Create another LowLevelQualifier of SBIPSQL for the other PDS.

For example, if you create a HighLevelQualifier of IBM.NEWERA, the LowLevelQualifiers would be IBM.NEWERA.SBIPJCL and IBM.NEWERA.SBIPSQL.

In the installation directory /usr/lpp/wmqi/nnsy/install.sql/scripts/db250, copy NnsyConfigFile.MSTR to a new data set named NnsyConfigFile.in.
In the NnsyConfigFile.in, locate the following tokens. Tokens are enclosed in angle brackets "<>":

Token	Description
<auth-id>	SQLID database owner.
<database-name>	Database in which all table spaces are created.
<storage-group-name>	DB2 storage group in which databases are created.
<vcat-dataset-name-prefix>	Storage group IntegratedCatalogFacility.
<volume-list>	Storage group volumes.
<db2smprl>	Library that contains DB2 sample program.
<db2mpdl>	Library in which the sample program is located.
<db2inhlq>	High-level DB2 library qualifiers.
<db2ssysn>	DB2 subsystem name.
<db2locan>	DB2 location name.
<pgmname>	DB2 sample program name.
<planname>	DB2 sample plan name.
<NNHLQ>	Data set High Level Qualifiers created in step 1 of this procedure.

Replace all tokens with parameters and enclose them in single quotation marks.
From the installation directory, run the script NNInstallDriver.sh.

Notes: If you install the NnsyConfigFile.in file in a directory other than /usr/lpp/wmqi/nnsy/install.sql/scripts/db250, you must specify the -c parameter followed by the directory which contains the NnsyConfigFile.in file to ensure that the install script searches the proper directory.

If you installed the product under a directory other than /usr/lpp/wmqi/nnsy/install.sql/scripts/db250, you must specify the -i parameter followed by the high-level directory of your installation to ensure that the install script searches the proper directory.

To set the environment variables, choose one of the following:

· Add each variable to your profile using the command syntax in the following table.

· Enter the command syntax on the command line each time you start an executable.

New Era of Networks Product Environment Variables

Variable	Command Syntax
DSNAOINI	export DSNAOINI=<path to dsnaoini file>
LIBPATH	export LIBPATH= /usr/lpp/wmqi/nnsy/ lib:$LIBPATH
NNSY_CATALOGUES	export NNSY_CATALOGUES= /usr/lpp/wmqi/nnsy/ NNSYCatalogues/<locale name>
NNSY_ROOT	export NNSY_ROOT= /usr/lpp/wmqi/nnsy
PATH	export PATH= /usr/lpp/wmqi/nnsy/bin:$PATH

Warning: When you are making changes to the paths, type the following to prevent overwriting all data currently in the path:

For LIB_PATH:
export LIBPATH=$NNSY_ROOT/lib:$LIBPATH

For PATH:
export PATH=$NNSY_ROOT/bin:$PATH

From the JCL PDS created in step 1 of this procedure, run the following jobs:

· CRSTOGRP

· CRDB

· CRTSPACE

· CRTABS

· GRANTS

· META

If these jobs run successfully, the New Era of Networks Rules and Formatter database is installed.

Executable and Catalogue File Location

To ensure the best performance, the executable and catalogue files of the New Era of Networks product should be placed on your local HFS drive.

If you place the product on a NFS drive, you must also mount these drives as binary. Failure to mount NFS drives as binary may result in unexpected product behavior as NFS attempts to translate the data.