Rules and Formatter Extension for IBM WebSphere Message Broker for
Multiplatforms and z/OS V7.0
Welcome to the Rules and Formatter Extension for IBM WebSphere Message Broker. This README file contains information that you need to complete installation for multiplatforms and z/OS.
Contents
Installing Rules and Formatter Extension for WebSphere Message Broker
1. · Prerequisites
2. · Server Installation
3. · Client Installation
4. · Verifying Database Connectivity
5. · Console or Silent Installation
6. · Console or Silent UnInstallation
7. · z/OS Installation
8. · Installing the Database Schema
9. · Database Migration
Note: For all installation instructions, <install_dir> refers to the default installation directory.
IBM WebSphere Message Broker for Multiplatforms V7.0
DBMS listed in supported platforms
Note: z/OS installation instructions can be found at the end of this document.
Server
|
Operating System |
DBMS |
|
Windows XP - sp2 32bit & 64bit 2003 32bit & 64bit 2003 R2 32bit & 64bit Vista 32bit and 64bit 2008 32bit & 64bit |
Microsoft SQL Server 2005 Microsoft SQL Server 2008 Oracle 10g R2 Oracle 11g R1 Sybase ASE 15 DB2 v9.1 DB2 v9.5 |
|
Solaris 9 – 64bit Solaris 10 – 64bit |
Oracle 10g R2 Oracle 11g R1 Sybase ASE 15 DB2 v9.1 DB2 v9.5 |
|
AIX 5.3 - 64bit (plus TL7 and SP1) AIX 6.1 |
Oracle 10g R2 Oracle 11g R1 Sybase ASE 15 DB2 v9.1 DB2 v9.5 |
|
Linux 32bit & 64bit SUSE SLES v9 + compat-libstdc++lsb-4.0.2 SUSE SLES v10 RedHat EL v4.0 update 2 RedHat EL v5.0 or later |
Oracle 10g R2 Oracle 11g R1 Sybase ASE 15 DB2 v9.1 DB2 v9.5 |
|
Z/OS V1R8 - minimum (RSU 0812) |
DB2 v9.1 (z/OS) (RSU 0812) + UK42466 + APAR AK83072 |
|
|
|
Disk Space and Memory Requirements
Installation Media: CD-ROM
Disk Space: 140 MB for Rules and Formatter; 140 MB for temporary directory used during installation.
Memory: 512 MB for product files
Install Rules and Formatter
Runtime Engine
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.
1. Insert the CD-ROM and go to the setup for your operating system.
2. Start the installer
a. On Windows
If your machine is configured to autorun from the CD-ROM, the InstallShield Wizard automatically starts.
If your machine is not configured to autorun from the CD-ROM, do the following:
1. Select Start > Run from the Windows Start menu.
2. In the Run dialog box, browse
to locate the setup file:
<CD-ROM drive>:\setup.exe
3. Click OK.
The Installer Welcome window appears.
b. On Solaris and Linux
Note: The repository file containing installation information is created under the home directory of the person installing the product. Therefore only the person who installs the product can uninstall it.
1. Mount the CD-ROM.
For example:
pfs_mount <CD DEVICE> /mnt_point
2. Set the IP address:
export DISPLAY=<IP address:0:0>
3. To change to the /mnt_point
directory, enter:
$cd mnt_point
4. To start the installer, enter:
$ ./setupsolaris or $ ./setuplinux
The Installer Welcome window appears.
c. On AIX:
1. Mount the CD-ROM.
For example:
pfs_mount <CD DEVICE> /mnt_point
2. Set the IP address:
export DISPLAY=<IP address:0.0>
3. To change to the /mnt_point
directory, enter:
$cd mnt_point
4. To start the installer, enter:
$ ./setupaix
The Installer Welcome window appears.
Note: You might get a NULL error message at the end of the installation. Ignore the message.
3.
To initiate the installation process, click Next on the Installer
Welcome window.
The License Agreement window appears.
4. Click the radio button for I accept the terms of the license agreement.
Note: If you do not have IBM WebSphere Message Broker components installed, follow the instructions on the InstallShield Wizard screen.
5.
Click Next.
The Installation Directory Window appears.
6. To specify an installation directory, select one of the following:
1. To accept the default directory, click Next.
2. To use a different directory, enter the directory name or click Browse, select a directory, and click Next.
3. If WebSphere
Message Broker is installed, but InstallShield is not detecting it, enter the
location (default is /opt/IBM/rf47).
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. Click Finish and * reboot the machine.
* (Windows only).
The Rules and Formatter Runtime Engine is located in the specified installation directory.
Note: Documentation files are installed under <install_dir>\rfdt\eclipse. You can view them through the main WebSphere help browser.
The Windows server sets the PATH environment variable to <install_dir>\rfdt\bin.
The installation places an uninstall program in the <install_dir>\rfdt\_uninstaller.
This section describes how to install the components required to run Rules and Formatter design-time tooling for Windows along with the Rules and Formatter Toolkit Extension on Linux x86.
|
Operating System |
DBMS |
|
Linux x86 |
Not Applicable |
|
Windows XP - sp2 32bit & 64bit 2003 32bit & 64bit 2003 R2 32bit & 64bit Vista 32bit and 64bit 2008 32bit & 64bit |
Microsoft SQL Server 2005 Microsoft SQL Server 2008 Oracle 10g R2 Oracle 11g R1 Sybase ASE 15 DB2 v9.1 DB2 v9.5 |
Linux x86 Disk Space and
Memory Requirements
Installation Media: CD-ROM
Disk Space: 40 MB for Rules and Formatter Nodes in Message Broker Toolkit. 60 MB for temporary directory used during installation.
Memory: 512 MB for product files
Windows Disk Space and Memory
Requirements
Installation Media: CD-ROM
Disk Space: 140 MB for Rules and Formatter Client; 140 MB for temporary directory used during installation.
Memory: 512 MB for product files
Verifying Database 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.
Grant the ‘system’ user permissions:
Due to internal security updates starting in oracle 9i, the user needs to make a change
prior to running inst_db.
Do the following:
1. Run sqlplus as sys user.
2. Issue the following command
inside sqlplus:
GRANT
SELECT on dba_role_privs to system with grant option
3. To create a new rulfmt
database schema, run inst_db as the system
rather than as the sys
account
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 MSSQL2005: \Microsoft SQL Server\90\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.
Preparing the Windows Installation Environment
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 on the default temporary directory.
· Launch the installer using a different temporary directory.
To install on a temporary directory other than the default directory:
· For Windows, enter the following
setup -is:tempdir <full path to alternate temp directory>
Administrative Rights on Client
Machine
When installing on Rules and Formatter Extension for WebSphere Message Broker on a workstation, the user performing the install must have administrator privileges. These privileges are specifically required to properly install the Rules GUI. If the user does not have administrator privileges, the registry is not updated and the Rules GUI will not run.
Install Rules and Formatter
Toolkit Extension for Windows
Rules and Formatter Toolkit Extension can be installed only on a Windows workstation. These instructions assume you are logged on to the client workstation with administrative rights.
(Note: If installing Rules and Formatter Toolkit Extension without installing the Websphere Message Broker Toolkit first, you will need to repeat these steps after installing the Websphere Message Broker Toolkit in order to have access to the Rules and Formatter nodes.)
To install Rules and Formatter Toolkit Extension using the InstallShield Wizard
1. Insert the CD-ROM.
2. Choose Start>Run from the Windows Start menu.
3. In the Run dialog
box, browse to locate the following file:
<CD-ROM drive>:\setup.exe
4. Click OK.
The Installer Welcome window appears.
5. To initiate the
installation process, click Next on the Installer Welcome window.
The License Agreement window appears.
6. Click the radio button for I accept the terms of the license agreement.
Note: If you do not have IBM WebSphere Message Broker components installed, follow the instructions on the InstallShield Wizard screen.
7. Click Next.
The Installation Directory Window appears.
8. To specify an installation directory, select one of the following:
1. To accept the default directory, click Next.
2. To use a different directory, enter the directory name or click Browse, select a directory, and click Next.
3. If WebSphere Message Broker is installed, but InstallShield is not detecting it, enter the location (default is C:\Program Files\IBM\rf47).
9. The Installation Summary window displays the products to be installed and the approximate required disk space.
10. Click Next.
The Installation Summary window displays installation progress.
11. Click Finish and reboot the machine.
12. Restart the Websphere Message Broker Toolkit with the "-clean" option. This can be done from the command line, or by modifying the menu shortcut. The "-clean" option should be used whenever any changes are made to user-defined extensions, to make sure they are picked up by the message flow node palette.
The subdirectories added to the <install_dir>\rfdt\gui
for the client installation are:
|
Subdirectory |
Description |
|
examples |
Contains example files. |
|
NNSYCatalogues |
Contains catalogue files for language support. |
Note: Documentation files are installed under <install_dir>\rfdt\eclipse. You can view them through the main WebSphere help browser.
The installation places an uninstall program in the <install_dir>\rfdt\_uninstaller.
Preparing the Linux x86
Installation Environment
Temporary Installation Directory
The installer uses a temporary location during the installation process. The default temporary location on Linux x86 is /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 on the default temporary directory.
· Launch the installer using a different temporary directory.
To install on a temporary directory other than the default directory:
· For Linux x86, enter the following
setuplinux -is:tempdir <full path to alternate temp directory>
Administrative Rights on Client
Machine
When installing on Rules and Formatter Toolkit Extension for WebSphere Message Broker on a workstation, the user performing the install must have administrator privileges.
Install Rules and Formatter
Toolkit Extension for Linux x86
These instructions assume you are logged on to the client workstation with administrative rights.
(Note: If installing Rules and Formatter Toolkit Extension without installing the Websphere Message Broker Toolkit first, you will need to repeat these steps after installing the Websphere Message Broker Toolkit in order to have access to the Rules and Formatter nodes.)
To install Rules and Formatter Toolkit Extension using the InstallShield Wizard
1. Mount
the CD-ROM.
For example:
pfs_mount <CD DEVICE> /mnt_point
2. Set
the IP address:
export DISPLAY=<IP address:0.0>
3. To
change to the /mnt_point directory, enter:
$cd mnt_point
4. To
start the installer, enter:
$ ./setuplinux
The Installer Welcome window appears.
5. To
initiate the installation process, click Next on the Installer Welcome window.
The License Agreement window appears.
6. Click the radio button for I accept the terms of the license agreement.
Note: If you do not have IBM WebSphere Message Broker components installed, follow the instructions on the InstallShield Wizard screen.
7. Click
Next.
The Installation Directory Window appears.
8. To specify an installation directory, select one of the following:
1. To accept the default directory, click Next.
2. To use a different directory, enter the directory name or click Browse, select a directory, and click Next.
3. If WebSphere Message Broker is installed, but InstallShield is not detecting it, enter the location (default is /opt/IBM/rf47).
9. The Installation Summary window displays the products to be installed and the approximate required disk space.
10. Click Next.
The Installation Summary window displays installation progress.
11. Click Finish.
12. Restart the Websphere
Message Broker Toolkit with
the "-clean" option. The "-clean" option should be used
whenever any changes are made to user-defined extensions, to make sure they are
picked up by the message flow node palette.
The subdirectories added to the <install_dir>/rfdt/gui
for the client installation are:
|
Subdirectory |
Description |
|
examples |
Contains example files. |
|
NNSYCatalogues |
Contains catalogue files for language support. |
Note: Documentation files are installed under <install_dir>/eclipse. You can view them through the main WebSphere help browser.
The installation places an uninstall program in the
<install_dir>/rfdt/_uninstaller.
Console or silent install:
The console install follows the same procedures as the GUI, but instead of
using Java Swing GUI, all the install panels/prompts are printed to the console
screen. Numerical inputs are substituted for clicking "next",
"previous" and "finish."
Run "setup-console"
ISMPE sets up java VM
1.
Info screen (product information)
press
"1" to continue
2. License agreement
ENTER
to scroll through agreement, "q" to complete
"1" to select "accept the terms"
"0"
to continue
3. Input install directory (just enter to accept default)
"1" to continue
4. (if toolkit not found)
"1"
to continue without IBM toolkit integration
NOTE: This won't happen on Linux, since the Linux installer's only purpose is
to add our
plugins to the toolkit. Windows allows for install of R&F GUIs even if the
toolkit isn't found.
5. Disk space check and summary information
Displays install location, features selected and disk space required
"1" to continue
6. Progress indicator
Counts up % completion in increments of 10%
7. Completion page
"3" to finish
Console uninstall:
Go to {install directory}/uninstaller
Run "uninstall-console"
ISMP configures java VM
1. Info screen (product information)
press
"1" to continue
2. Summary page: Features to be uninstalled
"1" to continue
3. Uninstallation (pretty quick)
4. Success/failure page
"3" to finish
This section describes how to install Rules and Formatter Extension for WebSphere Message Broker for Multiplatforms on the z/OS platform.
1. 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.
o Create the same HighLevelQualifiers for both PDS data sets.
o Create a LowLevelQualifier of SBIPJCL for one PDS.
o
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.
2. In the installation directory /usr/lpp/wmqi/nnsy/install.sql/scripts/db250, copy NnsyConfigFile.MSTR to a new data set named NnsyConfigFile.in.
3. 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. |
4. Replace all tokens with parameters and enclose them in single quotation marks.
5. 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.
6. To set the environment variables, choose one of the following:
1. Add each variable to your profile using the command syntax in the following table.
2. 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/<Rules/Formatter install directory>/nnsy/ |
|
NNSY_CATALOGUES |
export NNSY_CATALOGUES= /usr/lpp/<Rules/Formatter install
directory>/nnsy/ |
|
NNSY_ROOT |
export NNSY_ROOT= /usr/lpp/<Rules/Formatter install directory>/nnsy |
|
PATH |
export PATH= /usr/lpp/<Rules/Formatter install directory>/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
7. 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.
Installing the Database Schema
The inst_db application creates the physical resources and schema required to successfully run the Rules and Formatter extension.
To install the database schema, begin with the following procedure. At step 6 of this procedure, continue the installation process using the instructions at the bottom of each installation screen.
After the installation is complete, return to step 7 of this procedure.
To install the database schema:
1. To change to the inst_db directory, type the following from your command pompt and press ENTER:
cd
<install_root_dir>/rfe/install.sql_rulfmt47/inst_db
Notes: inst_db for DB2 on Windows platforms must be run in a DB2 command window; not from a windows command prompt.
2. To configure the command window size, use the following minimum dimensions:
_ 80 (column)
_ 60 (row)
If this configuration is not possible, add scrolling capability to the command window to provide access to the entire user interface.
3. To begin the database schema installation, type the following and press ENTER:
inst_db
The following screen appears.
New Era of Networks Database Installation
Enter type of database ( 1 = DB2;
3 = Microsoft 2000;
4 = Oracle;
5 = Sybase;
1. · 1 = Exit ):
4. Select the database type and press ENTER.
The following screen appears.
New Era of Networks Database Installation
Enter type of installation <1 = Basic; 2 = Advanced; -1 = Exit>:
5. Select the type of installation and press ENTER:
_ Basic (1)
Performs the installation based on the database size that you select during the installation process. Basic mode allows for three database sizes:
_ small database (10MB)
_ medium database (20 MB)
_ large database (60 MB)
_ Advanced (2)
Adjusts the database size based on options that you select throughout the installation process.
The appropriate database screen appears based on your database selection.
6. Follow the procedures at the bottom of each installation screen. After you have completed the installation, continue with step 7 in this procedure.
7. When the installation successfully completes, the following message appears:
Installation completed SUCCESSFULLY.
8. To review installation details, view the inst_db.log file in the current directory.
For Windows and Linux x86-32 no rules & formats database migration is required. Go to ‘Environment Migration’.
For AIX, Solaris and zOS the NEON nodes now require 64bit client access to the rules & formats database. This is because when you migrate from WMBv6 or v6.1 to WMBv7 on these platforms any 32bit execution groups (which may have NEON flows deployed) will become 64bit execution groups when mqsimigratecomponents is used to migrate your broker.
See your database manager documentation for more details. If your current Rules & Formats database supports 64bit client access then there is no need to migrate the database. If your database does not support 64bit client connections then create a new rules & formats database on a configuration that does and export rules & formats from the old database and import them into the new database. See the Chapter 4 in the System Management Guide for instructions on migrating your data.
Environment Migration
When you install the Rules & Formatter Extension it extends the WMB command console environment (mqsiprofile). In addition users are required to set NN_CONFIG_FILE_PATH in this environment to point to a nnsyreg.dat file which specifies sessions for connecting to the database. In v7 the values which should be used in the nnsyreg.dat file are:
Table showing session information for each DBM
|
Database Type
|
NNOT_SHARED_LIBRARY
|
NNOT_FACTORY_FUNCTION
|
|
Microsoft SQL server |
dvdb47sql |
NNSesMS6Factory |
|
Oracle |
dvdb47ora |
NNSesOra8Factory |
|
Sybase CTLIB |
dvdb47syb |
NNSesSybCTFactory |
|
DB2 |
dvdb47db2 |
NNSesDB2Factory |
Here is an example for DB2
Session. MQSI_PLUGIN
NNOT_SHARED_LIBRARY = dvdb47db2
NNOT_FACTORY_FUNCTION = NNSesDB2Factory
NN_SES_SERVER =
EVEIN
NN_SES_USER_ID =
db2admin
NN_SES_PASSWORD =
db2admin
The
'MQSI_PLUGIN' session must be defined to allow the broker to connect to the New
Era of Networks Rules and Formats database.
The 'MQSI_CONFIG' session must be defined to allow the Configuration Manager to
connect to the New Era of Networks Rules and Formatter database.
Your
environment may also require modifications to allow the correct 32 or 64bit
client connection to the Rules & Formats database required by the NEON
nodes. See your database manager documentation for details.
When you migrate your broker using
mqsimigratecomponents you should ensure, if you have NEON nodes deployed to it,
that you have installed the RFE v7 product and configured the v7 environment in
the above ways before restarting your broker. Otherwise your existing NEON
flows may fail to start or function correctly until these steps have been
completed.