Configuring the IBM Traveler High Availability pool on IBM® i
This section describes how to configure the IBM Traveler server to use IBM® i DB2®. Use this section when creating a High Availability (HA) pool or adding a server to an existing HA pool.
V6R1 5761JC1 jt400.jar directory: /QIBM/ProdData/HTTP/Public/jt400/lib
V7R1 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib
V7R2 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib
Configuring IBM Traveler for enterprise database on IBM® i
- Create a DB2® user profile that has
*ALLOBJ
and*SECADM
authority. - IBM® i DB2® servers
only: Copy the
jt400.jar
file to the directory/qibm/proddata/lotus/domino901/traveler/lib/
. Thejt400.jar
file is located here:V6R1:/QIBM/ProdData/HTTP/Public/jt400/lib; V7R1 & V7R2:/QIBM/Proddata/OS400/jt400/lib
- Stop the IBM Traveler servers that you want to configure for HA.
- From an IBM® i command line, run the following command to
start the QShell Interpreter:
QSH
- Navigate to the traveler utility directory:
cd /<domino data>/traveler/util
- Run
travelerUtil
to configure IBM Traveler in the following format:./travelerUtil db set url=jdbc:as400://<server.ibm.com>/LNT user=<username> pw=<password>
server.ibm.com
is the DB2® location system's IP address.User
andpw
use the user profile and password created in step 1. For example, if the DB2® location system is192.168.1.1
, the command would be:./travelerUtil db set url=jdbc:as400://192.168.1.1/LNT user=<username> pw=<password>
- Exit the
qsh
session and restart the IBM Traveler server. The console will display a message indicating the server is in HA mode. - When you have configured all HA servers, issue the command
tell traveler hadr show
from any console. It will display all IBM Traveler servers in the HA pool. Issue the commandtell traveler hadr ping *
to make sure all servers give a response.Note: If you have multiple IBM Traveler servers in the pool, ensure one server starts successfully in HA mode before starting the other servers.
Configuring IBM Traveler DB2® manually using the DDL on IBM® i (optional)
LNT
conflicts
with the system's existent schema. You should change the schema name
in the DDL To configure DB2® on IBM® i using DDL, perform the following
procedure:- Unzip the IBM Traveler DDL in
<domino data dir>/traveler/cfg/db/TravelerSQL.zip
to the current directory. - For IBM® i, run the following
command:
RUNSQLSTM SRCSTMF('/QIBM/Proddata/lotus/traveler901/data/traveler/cfg/db/AS400/createDb.sql') PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)
You can also copy the
createDb.sql
to a local directory on your workstation. Then, using System i Navigator > Databases > Run SQL Scripts, load thecreateDb.sql
and run it. - For IBM® i, grant the necessary permissions to the DB Login
user to the IBM Traveler DB, using the following
command:
RUNSQLSTM SRCSTMF('/QIBM/Proddata/lotus/traveler900/traveler901/data/traveler/ cfg/db/AS400/appGrants.sql') PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)
You can also copy the
appGrants.sql
to a local directory on your workstation. Then, using System i Navigator > Databases > Run SQL Scripts, load theappGrants.sql
and run it. - Create an Operating System User that matches the DB2® user specified in the
appGrants.sql
file. - Update the
notes.ini
to add the following property to tell the system the IBM Traveler DB and its objects were created:NTS_AUTO_DBSCHEMA=false
- If you changed the schema name in the DDL files, you must set
the following property in the
notes.ini
, where<schemaname>
is the schema name used in the DDL files:NTS_DB2_SCHEMA=<schemaname>
For additional information, refer to Configuring the Lotus Notes® Traveler High Availability Pool.