Configuring a TCP/IP Connection to the Database

Status

If you are...

This task is...

Installing a new iProcess Engine Version 11.8.0

Required

Upgrading from an iProcess Engine Version 11.0 or later

N/A

Database

DB2

Description

iProcess Engine needs to communicate with the database over a TCP/IP connection. This applies whether the database is hosted on a local or remote machine.

Shared memory connections cannot be used for communication with the DB2 server.

Procedure

To configure a TCP/IP connection:

1. Add a TCP/IP node entry to the DB2 node directory. This entry defines that the TCP/IP communications protocol is used to access the specified DB2 node. To do this, use the following DB2 command:

db2 catalog tcpip node nodename remote hostname server svcename

where:

— nodename is the name you want to use for this entry.
— hostname is the TCP/IP host name or IP address of the node where the iProcess Engine database resides. If you are using a local database, hostname is the localhost address (127.0.0.1).
— svcename is the Connection Service name used by the DB2 instance where the iProcess Engine database resides.

This name defines the TCP/IP port used by the instance to listen for client requests, and is defined in the /etc/services file. For example:

db2c_db2inst1    50000/tcp   # Connection port for DB2

                             # instance db2inst1

2. Add an alias for the iProcess Engine database to the system database directory. This alias uses the TCP/IP node entry you specified above. To do this, use the following DB2 command:

db2 catalog database db_name as alias at node nodename

where:

— db_name is the name of the iProcess Engine database you created earlier (see Creating a DB2 Database).
— alias is an alternative name for this database. You will use this name to identify the database when you run the installer (see DB2 Database Connection and Account Details Menu).
— nodename is the TCP/IP node entry you defined above.
3. If the database manager configuration file for this DB2 instance is not already using the svcename Connection Service name you specified above, update it so that it does by using the following command.

db2 update database manager configuration using svcename svcename

 

Note 

You can use the db2 get database manager configuration command to check what Connection Service name the DB2 instance is currently using.
4. Enable the use of the TCP/IP protocol for the instance using the following command:

db2set DB2COMM=protocol

where protocol is either TCPIP or, if the instance needs to use multiple communication protocols, a comma-separated list of the appropriate keywords. See your DB2 documentation for more information.

5. Stop and restart the DB2 instance to apply the configuration changes. Use the following commands:

db2stop force

db2start

Example 1: Using a Local Database

The following example shows the commands needed to set up TCP/IP connections to an iProcess Engine database called swnod501 that is on the same computer as the iProcess Engine.

The alias r_sw501 will be used to identify this database to the iProcess Engine.

db2 catalog tcpip node loopfix remote 127.0.0.1 server db2c_db2inst1
db2 catalog database swnod501 as r_sw501 at node loopfix 
db2 update database manager configuration using svcename db2c_db2inst1
db2set DB2COMM=TCPIP
db2stop force
db2start

Example 2: Using a Remote Database

The following example shows the commands needed to set up TCP/IP connections to an iProcess Engine database called swnod502 that is installed on a remote computer called llama3.

The alias r_sw502 will be used to identify this database to the iProcess Engine.

db2 catalog tcpip node db24sw1 remote llama3 server db2cdb2inst2
db2 catalog database swnod502 as r_sw502 at node db24sw1 
db2 update dbm cfg using svcename db2cdb2inst2
db2set DB2COMM=TCPIP
db2stop force
db2start