Configuring the HCL Traveler High Availability pool on IBM® i

This section describes how to configure the HCL 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.

CAUTION: When you configure a stand alone server to use an enterprise database, the server will migrate existing user and security information to the enterprise database. However, if you are moving from an enterprise database to another database, enterprise or standalone, no user or security data is migrated.

Make sure the IBM® Toolbox for Java™ is installed on the IBM® i system with the latest PTF:

V7R2 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib
V7R3 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib
V7R4 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib
V7R5 5770SS1 option 3 jt400.jar directory: /QIBM/Proddata/OS400/jt400/lib

Perform the following procedures for each HCL Traveler server that is part of the pool, depending on your configuration.

Note: Configuring HCL Traveler to use a High Availability (HA) Pool on IBM® i requires special IBM® i commands.

Configuring HCL Traveler for enterprise database on IBM® i

This section describes how to configure the HCL Traveler server to use the IBM® i native database. Use this section when creating a High Availability (HA) pool or adding a server to an existing HA pool 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 Domino product directory. The file is located here:
```
/QIBM/Proddata/OS400/jt400/lib
```
For Domino 9.0.1, copy jt400.jar to:
```
/qibm/proddata/lotus/domino901/traveler/lib
```
For Domino 10.0.1, copy jt400.jar to:
```
/qibm/proddata/lotus/domino100001/traveler/lib
```
For Domino 11.0.0, copy jt400.jar to:
```
/qibm/proddata/lotus/domino110000/traveler/lib
```
For Domino 11.0.1, copy jt400.jar to:
```
/qibm/proddata/lotus/domino110001/traveler/lib
```
For Domino 12.0.0, copy jt400.jar to:
```
/qibm/proddata/lotus/domino120000/traveler/lib
```
For Domino 12.0.1, copy jt400.jar to:
```
/qibm/proddata/lotus/domino120001/traveler/lib
```
For Domino 12.0.2, copy jt400.jar to:
```
/qibm/proddata/lotus/domino120002/traveler/lib
```
For Domino 14.0.0, copy jt400.jar to:
```
/qibm/proddata/lotus/domino140000/traveler/lib
```
Stop the HCL 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 HCL Traveler in the following format:
```
./travelerUtil db set url=jdbc:as400://<server.HCL.com>/LNT  user=<username> pw=<password>
```
server.HCL.com is the DB2® location system's IP address. User and pw use the user profile and password created in step 1. For example, if the DB2® location system is 192.168.1.1, the command would be:
```
./travelerUtil db set url=jdbc:as400://192.168.1.1/LNT   user=<username> pw=<password>
```
Note: If you experience issues running travelerUtil, see this article.
Exit the qsh session and restart the HCL 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 HCL Traveler servers in the HA pool. Issue the command tell traveler hadr ping * to make sure all servers give a response.
Note: If you have multiple HCL Traveler servers in the pool, ensure one server starts successfully in HA mode before starting the other servers.

Configuring HCL Traveler DB2® manually using the DDL on IBM® i (optional)

This configuration is only be required when the default schema name 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 HCL Traveler DDL in <domino data dir>/traveler/cfg/db/TravelerSQL.zip to the current directory.

For IBM® i, run the command that corresponds to the Domino version that you use:

For Domino 9.0.1, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler901/data/traveler/cfg/db/AS400/createDb.sql’)
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 10.0.1, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler100001/data/traveler/cfg/db/AS400/createDb.sql’)
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 11.0.0, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler110000/data/traveler/cfg/db/AS400/createDb.sql’) 
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 11.0.1, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler110001/data/traveler/cfg/db/AS400/createDb.sql’)
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 12.0.0, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler120000/data/traveler/cfg/db/AS400/createDb.sql’) 
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 12.0.1, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler120001/data/traveler/cfg/db/AS400/createDb.sql’) 
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 12.0.2, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler120002/data/traveler/cfg/db/AS400/createDb.sql’) 
PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)

For Domino 14.0.0, run:

RUNSQLSTM SRCSTMF(’/QHCL/Proddata/lotus/traveler140000/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 the createDb.sql and run it.

For IBM® i, grant the necessary permissions to the DB Login user to the HCL Traveler DB. Run the command that corresponds to the Domino version that you use: