InterChange Server requires a database and can use several databases
depending on how you partition the database activity.
This section includes configuration information for:
- Note:
- In this guide, references to a database name refers to the SID name in a UNIX
environment.
This section provides information about the installation and configuration
of IBM DB2 for use with InterChange Server:
- Important:
- If the DB2 Server is not installed on the same machine as InterChange Server,
you must install a DB2 client.
This section describes pre-installation tasks for DB2 server. These
instructions represent a suggested way to set up DB2. Refer to DB2
documentation for the complete detailed instructions on performing these
pre-installation steps.
- Note:
- There are no required group or user names, but IBM recommends the following
names for user groups and users. DB2 has an 8-character database name
limit.
Before you install DB2 server, you must:
- Create the following DB2 user groups:
- Instance user group - db2iadm
- Fenced administrative user group - db2fadm
- DAS administrative user group - db2asadm
- Create the following DB2 users and assign each to the appropriate group as
shown:
- db2i81 - Assign to the instance user group
- db2f81 - Assign to the fenced administrative user
group
- dasinst - Assign to the DAS administrative user
group
This guide does not provide installation instructions for the DB2
server. For information about the DB2 installation process, read the
DB2 product documentation.
Notes:
- Building DB2 stored procedures requires a DB2-supported C or C++
compiler. This compiler is not supplied with the DB2 product and must
be obtained separately. For information about working with stored
procedures, read the DB2 documentation.
- If you are using DB2 as your database, the InterChange Server requires the
version of the db2java.zip file listed in Table 5, Table 6, Table 7, or Table 8 depending
on platform. This driver must be on the same server as the one that
will run the InterChange Server. If you choose DB2 as your database
during installation, the InterChange Server installation GUI will ask for the
location of this file.
During the installation, an administrative instance and a database instance
are created. The administrative instance is transparent and lets you
perform remote administration on your database instance.
After installing the DB2 Server:
- Run the db2profile script for the db2i81
and admin users to set the environment variables shown in Table 15..
Notes:
- The db2profile script is located in the sqllib
directory of the database instance owner, for example,
/db2i81_home_dir/db2i81/sqllib
where db2i81_home_dir is the path for the
db2i81 user's home directory.
- It is important to run the db2profile script before starting
the
System Monitor.
Table 15.
Environment variables for DB2 users
Environment variable
| Description
|
DB2INSTANCE
| The database instance name.
|
PATH
| Include the following paths:
- /db2i81_home_dir/
DB2_instance_name/sqllib/bin
- /db2i81_home_dir/DB2_instance_name/sqllib/adm
- /db2i81_home_dir/DB2_instance_name/sqllib/misc
- /db2i81_home_dir/DB2_instance_name/sqllib/java12
- Any other paths in the system's existing PATH environment variable
($PATH)
|
CLASSPATH
| Include the following paths:
- /db2i81_home_dir/DB2_instance_name/sqllib/function
- /db2i81_home_dir/DB2_instance_name/java/db2java.zip
- /db2i81_home_dir/DB2_instance_name/sqllib/
java/runtime.zip
- Any other paths in the system's existing CLASSPATH environment
variable ($CLASSPATH)
|
LIBPATH (AIX)
LD_LIBRARY_PATH
(Solaris)
SHLIB_PATH (HP-UX) LIBPATH or
LD_LIBRARY_PATH (Linux)
| Include the path of the DB2 libraries:
- /db2i81_home_dir/DB2_instance_name/sqllib/lib
- /db2i81_home_dir/DB2_instance_name/sqllib/lib/libdb2jdbc.so
Any other paths in the system's existing LIBPATH, LD_LIBRARY_PATH, or
SHLIB_PATH environment variable
|
- Run the env command to verify that the environment variables
shown in Table 15 are set for each user.
- Note:
- Be sure to verify that the DB2INSTANCE variable is set to the
proper value. If the DB2 client is installed on the computer where
InterChange Server is installed but the DB2INSTANCE variable is not
set or is set to an incorrect value, InterChange Server cannot start.
This is true even if DB2 is not the database platform that is used by
InterChange Server. For instance, if Oracle is used as the database but
the DB2 client is installed without the DB2INSTANCE variable being
set properly, InterChange Server will not be able to start.
- Run the usejdbc2 script, (located in /sqllib/java12)
to append each path with the correct driver for DB2.
- Note:
- This script must be run for each user, each time they log in. You can
add this script to the personal profile file (such as
.profile) of the WebSphere business integration
administrator account to automatically run the script during log in.
- Add the following line to the to the user profile file (such as
.profile):
EXTSHM=ON; export EXTSHM
- Log in as the DB2 user and issue the following command:
db2set DB2ENVLIST=EXTSHM
- Restart DB2.
- Confirm that the Java Runtime Environment (JRE) version
1.4.2 is installed and set in your path. You cannot
access the DB2 tools if it is not installed.
- Confirm that the DB2 client libraries are functioning; see the DB2
product documentation for how to do this. If these libraries are not
functioning it will not be possible to establish a DB2 connection.
This section provides the information for configuring DB2.
If you are configuring DB2 on any device except the system console, you
need to set the
DISPLAY environment variable, which provides the IP address of the machine on
which to display these windows. The following lines set the DISPLAY
environment variable to the IP_Address from a Bourne
shell:
DISPLAY=IP_Address:0.0
export DISPLAY
Use the syntax appropriate to your shell to set the DISPLAY environment
variable.
- Note:
- Your Windows computer must run X Window client emulation software (such as
Reflection X or Hummingbird Exceed). The DISPLAY environment
variable of the UNIX computer must be set to the IP address of the Windows
client computer.
Opening the Control Center
The Control Center is
the main DB2 graphical tool for administering your database. It also
provides an overview of all the systems and database objects being
managed. You use the Control Center to configure DB2 for your specific
IBM WebSphere InterChange Server environment.
To access the Control Center:
- Log on as the database instance owner.
- Run the db2cc command to open the Control Center.
- Note:
- In order to run db2cc, X Window server software must be
installed.
Creating the database
This section describes
how to create the repository database for your InterChange Server
environment.
- Important:
- If you are using InterChange Server in an internationalized environment, set
the DB2 environment variable as follows:
db2codepage = 1208
- Right-click the DB2_instance_name folder in the left
pane of the Control Center and select Attach.
The Attach screen appears.
- Enter the database instance User ID and Password that you created during
the DB2 installation process. Click OK.
- Expand the DB2_instance_name folder, right-click the
Databases folder and select Create > Database Using Wizard.
The Create Database Wizard screen appears.
- Enter the new Database name and Alias. For example, type
icsrepos for both.
- Note:
- There is no required name, but it is recommended that you use the name
icsrepos. DB2 has an 8-character database name limit.
- Click Finish.
The Progress screen appears showing that the new database is being
created.
- Note:
- The new database is automatically cataloged during this process.
Configuring the database instance
This section describes
how to configure the database instance for your InterChange Server
environment.
- Right-click the DB2_instance_name folder in the left
pane of the Control Center and select Configure.
The Configure Instance screen appears.
- Select the Applications tab, scroll to the maxagents parameter
and enter a minimum of 50 in the Maximum number of agents field. Click
OK.
Configuring the repository database
This section describes
how to configure the repository database for your InterChange Server
environment.
- Expand the Instances, DB2 instance, and Databases folders in the left pane
of the Control Center, right-click on the database_name
(for example, icsrepos) and select Configure.
The Configure Database screen appears.
- Select the Performance tab, scroll down to the applheapsz
parameter and input 4096 into the Application heap size field.
- Select the Applications tab, scroll down to the maxappls
parameter and input a minimum of 50 into the Maximum number of active
applications field. Click OK.
- Close the Control Center.
- Disable the next key locking mechanism by entering the following command
at the command line:
db2set DB2_RR_TO_RS=yes
- Restart the database for the modified configuration parameters to take
effect. To do this, enter the following commands at the command
line:
Testing the client-server connection
To test that a DB2 connection has been established between the client and
the server, issue the command:
db2 connect to database_name user logon
followed by password.
Adding database authorities
An authorization allows
a user or group to perform a general task such as connecting to a database,
creating tables, or administering a system.
The database manager requires that a user be specifically authorized to use
each database function. Thus, to create a table, a user must be
authorized to create tables; to alter a table, a user must be authorized
to alter tables; and so on.
This section describes how to add database authorizations to a specified
user.
- Run the db2cc command to open the Control Center.
- Expand the Instances, DB2 instance, and Databases folders in the left pane
of the Control Center, right-click the database_name
(for example, icsrepos) and select Authorities.
The Database Authorities screen appears.
- Click the Add User button and select the name of the WebSphere business
integration administrator account created in Creating the IBM WebSphere business integration administrator account. The name recommended was
admin.
- Click the Grant All button to give the selected user all
authorizations.
- Click Apply, then OK.
Cataloging the system
After you create and configure your
database, you must catalog the system on which you have installed your server
and the database instance created during the installation process to add them
to your DB2 environment.
- Right-click the Systems folder in the left pane of the Control Center and
select Add System.
- Issue the following commands:
db2 catalog tcpip node catalog_name_of_the_node remote host_name server
service_name
db2 catalog database_name as alias_name_of_database at node
catalog_name_of_the_node
db2 set DB2_RR_TO_RS=yes
- Note:
- For AIX installation only. If you are using AIX as your
operating system, there is an additional step required. Since DB2 uses
shared memory segments for its local communication and AIX has some
limitations on shared memory, any attempt to process more than 10 concurrent
database connections from a single DB2 client application will result in DB2
connection errors.
The solution is to configure the local connection to route to TCP/IP rather
than the default shared memory segments. When defining the loopback
node and the database, use of TCP/IP as the transport protocol allows ICS to
connect to the loopback node and loopback database without problems.
To add the loopback node and database use the following
command:
db2 catalog tcpip node LOOPBACK remote localhost server 50000
After the node is cataloged you can catalog the database with the
following command:
db2 catalog database icsrepos as icsdb at node LOOPBACK
Now icsrepos should be accessible as icsdb via a
remote connection using TCP. Use icsdb as the Database name
in your InterchangeSystem.cfg file.
This guide does not provide installation instructions for Oracle
Server. For a description of the Oracle installation process, read the
appropriate manuals from among the following list for your version of
Oracle:
- Oracle8 Installation Guide
- Oracle8 Administration Guide
- Oracle 9i Installation Guide Release 2
(9.2.0.1.0)
- Oracle9i Administrator's Reference Release 2
(9.2.0.1.0)
- Important:
- These documents are very helpful in resolving Oracle installation
issues. It is strongly recommended that you review these
documents.
This section provides the following information about installing and
configuring the Oracle Server:
- Note:
- This section includes suggestions for installing Oracle Server and
configuration requirements for use with InterChange Server software.
These instructions represent one way to set up Oracle. Refer to Oracle
documentation for more detailed instructions.
This section describes pre-installation tasks for Oracle Server.
Before you install Oracle Server, you must:
- Create a unique operating system user for the Oracle administrator
account.
This administrator account is usually called
oracle. It is the oracle user who installs the
Oracle software.
- Create a unique operating system group for Oracle administration.
This administration group is usually called dba. The
Oracle administrator account (oracle) is usually required to be a
member of the dba group.
- Note:
- For the
WebSphere business integration administrator (admin by default) to
be able to perform database administration, it must also be a member of the
dba group. Adding the WebSphere business integration
administrator (admin by default) to the dba group is
optional. However, IBM recommends this addition so that the WebSphere
business integration administrator can perform administration of Oracle
Server.
- Set the Oracle
environment variables shown in Table 16 for the Oracle administrator account.
Table 16.
Environment variables for Oracle administrator account
Environment variable
| Description
|
ORACLE_BASE
| Path to the home directory of the Oracle administrator account
Recommended value: /home_dir where
home_dir is the path for the Oracle administrator user
account
|
ORACLE_HOME
| Path to the directory where Oracle Server is installed.
|
ORACLE_SID
| Set to the name of the
InterChange Server database instance (cwld by default). You
can choose any name. However, it should be four or fewer alphanumeric
characters to avoid problems with filename length restrictions on some
platforms.
|
ORACLE_TERM
| Set to vt100.
|
PATH
| Include the following paths:
- $ORACLE_HOME/bin
- Any other paths in the system's existing PATH environment variable
($PATH)
Additional paths might be required on your system. Make sure
duplicate paths do not exist.
|
CLASSPATH
| Include the path $ORACLE_HOME/jlib. Additional paths
might be required on your system.
|
LIBPATH
(AIX)
LD_LIBRARY_PATH
(Solaris)
SHLIB_PATH
(HP-UX) LIBPATH or LD_LIBRARY_PATH (Linux)
| Include the path of the Oracle libraries:
$ORACLE_HOME/lib. Additional paths might be required on your
system.
|
TMPDIR
| Set to the path of a temporary Oracle directory.
Example: /tmp/oracle
|
These environment variables are usually included in this profile of the
Oracle administrator account. Use the syntax that is appropriate for
the profile. For example, the default shell, sh, uses the
following syntax to set the ORACLE_BASE environment variable:
ORACLE_BASE=/home_dir/oracle
export ORACLE_BASE
- Assign a password to the Oracle administrator account.
Make sure that you give this password to the Oracle database administrator
at your site.
- Note:
- Installation of Oracle Server can involve design decisions that require
detailed knowledge of Oracle Server. To achieve an optimal
configuration of Oracle Server, IBM recommends that you coordinate with your
Oracle database administrator to perform this portion of the
installation.
The following recommendations can help you install
Oracle Server to run with InterChange Server. Your environment might
have different requirements:
The InterChange Server system has certain requirements for the database
server. This section describes how to set up Oracle database instances
for use with InterChange Server.
Database table
configurations
--The InterChange Server database contains four groups of
tables:
-
Event Management
Event Management tables store business objects that are being
processed.
-
Transaction
Transaction tables store the status of each transaction being processed,
which can include the action and compensation business objects, depending on
the transaction level.
-
Repository
Repository tables store information about the collaborations, business
objects, connectors, maps, and relationships that you can configure in the
InterChange Server system.
-
Flow Monitoring
Flow Monitoring tables store event information for flows which are traced
from IBM WebSphere MQ Workflow (MQWF) through the InterChange Server. A
Flow Monitoring table should be configured only if the user includes MQWF in
the business process and is tracing events through the InterChange
Server. The database administrator should reserve at least 20 MB for
this tablespace.
For load-balancing purposes, you can optionally configure four individual
databases, one each for these groups of tables. However, the
recommended approach is to configure all four table categories in a single
InterChange Server database, which is the default used by Installer.
You can specify different databases in the InterChange Server Configuration
screen.
- Note:
- In the remainder of this chapter, all references to the InterChange Server
database assume that the Event Management, Transaction, Repository, and Flow
Monitoring tables are included in one database. For information on how
to configure four individual databases, see Setting up InterChange Server databases.
General repository
database characteristics
--The InterChange Server database (also referred to as
InterChange Server repository database) must have the following
characteristics:
- Size: A starting size of at least 300 MB for the
repository tablespace is recommended.
- Tablespace file names for Oracle Server: There are no
required names, but IBM recommends cwrepos1_cwld, cwtemp1_cwld, and
cwrbs1_cwld.
User connections--InterChange Server requires at least 15 user
connections. This number is configurable. For more information,
see Setting up database connections.
DBMS access
account--InterChange Server requires a special account to log in to
the database (stored as one or more Oracle databases). The database
administrator must create an ICS database user account with update, create,
and delete privileges, to access tables, indexes, synonyms, stored procedures,
and constraints, and to add tablespace as needed.
General
relationship database characteristics for mapping--Some mapping
implementations require the use of
relationship tables. By default, the relationship tables are contained
in the InterChange Server
repository. You can optionally create one or more separate relationship
databases for the relationship tables. If you do so, consider the
following points:
- If you use one database for all of the relationship tables:
- Set the initial size of that database to about the same size as your
InterChange Server database (a recommended starting size of at least 300
MB).
- Set the JDBC path of the relationship database in the Global Default
Settings dialog of Relationship Manager.
- If you use more than one database for the relationship tables (such as one
database for each relationship table), make sure that the value of the
MAX_CONNECTION_POOLS parameter in the
InterchangeSystem.cfg file is set high enough to accommodate all
the databases. See the System Administration Guide for details about this parameter.
After a successful installation, the Oracle Server is installed in the
$ORACLE_HOME directory. The default location is usually
/var/opt/oracle.
- Note:
- This section outlines the configuration steps for Oracle Server to work with
the InterChange Server system. However, configuration of Oracle Server
can involve design decisions that require detailed knowledge of Oracle
Server. To achieve an optimal configuration of Oracle Server, it is
recommended that the Oracle database administrator perform these configuration
steps.
This section provides information about configuring the Oracle
Server.
Preparing for the
configuration--The
Oracle administrator account (usually called oracle) must configure
Oracle Server for support of InterChange Server software. To prepare
for this configuration:
- Log in as the Oracle administrator.
The UNIX system administrator (or database administrator) should have
created this administrator account as part of the installation of Oracle
Server (see "Oracle Server installation recommendations"). Therefore, this account should already have a profile
file to initialize your environment. If you do not have the password
for the Oracle administrator account, contact the UNIX system
administrator.
- Verify that your environment contains the appropriate settings for Oracle
environment variables.
Table 16 shows the main environment variables for use with Oracle
Server. Check with your site and Oracle administrators for possible
additional environment variables. You can use the env
command to list environment variable settings.
- Important:
- If any of these environment variables is not correctly set, notify
the UNIX system administrator that corrections must be made in the profile of
the oracle user account. Do not proceed with the
configuration if the environment variables (listed in Table 16) are not correct.
Creating the new database--You must create the
database that InterChange Server uses for its
repository, event management, transactions, and flow monitoring. By
default, these four categories of database tables reside in a single
InterChange Server database. For information on how to configure these
table categories into separate databases, see Setting up InterChange Server databases.
- Important:
- If you are using InterChange Server in an internationalized environment, set
the NLS_LANG environment variable as follows:
NLS_LANG = language_territory.UTF-8
Where language is the name of your locale's language and
territory is the name of your locale's territory. For
example, the NLS_LANG setting for the US locale is NLS_LANG =
AMERICAN_AMERICA.UTF-8.
To create the InterChange Server database:
- Create an Oracle database with the following characteristics:
- A unique server ID (SID). It is recommended that you use
cwld as the database SID.
- Two groups of log files, each 500 KB
- Run the following Oracle scripts on the InterChange Server database:
- standard.sql
- catalog.sql
- catproc.sql
These scripts are usually located in the
$ORACLE_HOME/rdbms/admin directory.
- Add an entry for the new database SID in the following Oracle system
files:
- tnsnames.ora
- listener.ora
These files are usually located in the
$ORACLE_HOME/network/admin directory.
- IBM recommends the following initialization parameters for the database
instance:
open_cursors=1200
sequence_cache_hash_buckets=89
sequence_cache_entries=100
db_file_multiblock_read_count=32
processes=300
Creating
tablespaces and rollback segments--In the new InterChange Server
database, you must add the following database objects:
- Tablespaces for the repository, rollback spaces, and a temporary
tablespace
- Rollback segments
- Note:
- In this section, the variable dbname represents the
name of your InterChange Server database (cwld is the name
suggested in this guide). The dbname database
name must be the value indicated by the ORACLE_SID environment
variable.
To create the tablespaces and rollback segments:
- Create a tablespace for the InterChange Server
repository that has the following characteristics:
- Suggested tablespace name: cwrepos1_dbname
- Tablespace size: minimum of 300 MB
- Create a tablespace for the database rollback segments that has the
following characteristics:
- Create a tablespace for the database temporary sort space that has the
following characteristics:
- Suggested tablespace name: cwtemp1_dbname
- Tablespace size: minimum of 300 MB
Creating the DBMS
access account--InterChange Server software requires a special
DBMS access account to allow login to the repository. This database
account must be created with insert, update, create, and delete privileges, to
access tables, indexes, synonyms, stored procedures, and constraints, and to
add tablespace as needed.
Create the DBMS access account with the following characteristics:
- Account name: wicsadmin
- Account password: admin
- Default tablespace: cwrepos1_dbname
- Default temporary tablespace: cwtemp1_dbname
- Privileges: connect, resource, and
unlimited tablespace
- Note:
- If you create another user to access the database, you must create a separate
tablespace for that user.
Verifying the database
creation--After creating the database, verify that the Oracle
connection between the client and the server is functioning correctly.
- Note:
- In this procedure, the variable dbname represents the
name of the InterChange Server database (cwld by default).
To test the Oracle connection between the client and the server:
- Start the database and verify it using dynamic performance views.
- Ensure that there is an entry for the
Oracle Net8 Listener in the /etc/services
system file.
The default
port number for the Listener is usually 1521. Therefore, its entry in
/etc/services might appear similar to the following line:
listener 1521/tcp # Oracle Net8 Listener
If no line for the Listener exists in this file, contact your UNIX system
administrator to add this line.
- Run the tnsping command to verify that the Oracle instance
resolves to the current machine.
- Verify that the Oracle server processes are running at the
operating-system level.
Oracle processes include ora_pmon_dbname,
ora_dbw0_dbname, ora_lgwr_dbname,
and ora_ckpt_dbname. The following command is one
way to list the Oracle server processes:
ps -ef | grep ora_*
- Verify that the Oracle Net8 Listener is running at the operating-system
level.
The following command is one way to determine if the Listener is
running:
ps -ef | grep LISTENER
Check the output of this command for the following process:
tnslsnr LISTENER -inherit
- Connect to the new database using the SQL command-line processor.
Execution of the SQL command-line processor generally has the form:
sqlplus username/password@dbdbname
where username and password are
the name and password of the DBMS access account. Using the default
DBMS access account and Oracle server ID, the preceding line appears as:
sqlplus wicsadmin/admin@dbcwld
If this program is able to connect, the database server is up and running
and the database is available.
