command is added in Lotus Notes Traveler 184.108.40.206 to enable log collection when the process could not start. It was enhanced to perform new configuration functions in the Lotus Notes Traveler 8.5.3 Upgrade Pack 1. This command is built during product installation and contains the server information of the system on which the Lotus Notes Traveler is installed. Therefore, this command is specific to the system and the data that is in place at installation time.
To use the travelerutil
command, you must run the this on the operating system level of the server:
- Open a command prompt.
- Change directory to \traveler\util.
travelerutil db set
The travelerutil db set
command configures the Lotus Notes Traveler server to the High Availability mode.
The basis for high availability for all the Lotus Notes Traveler servers in the pool to share common data via a remote enterprise database. Thus, if one server is to go down, another server can access the same data and "pick up" where that server left off. With that said, you can see that this command changes the Lotus Notes Traveler server from using the internal local Derby file system database to a central database that can be shared among additional servers.
IBM DB2 Server usage
To set a Lotus Notes Traveler to use DB2 for Linux, UNIX, and Windows database, use the following command
travelerUtil db set url=jdbc:db2://<db2server hostname>:<db port>/<traveler db name> user=<db2 admin id> pw=<db2 password>
Example of this usage:
travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler user=db2admin pw=passw0rd
On Linux the usage would be slightly different:
./travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler user=db2admin pw=passw0rd
Note: "50000" is the default DB2 port.
Micorsoft SQL Server usage
To set a Lotus Notes Traveler to use Microsoft SQL Server database, use the following commands;
travelerUtil db set url=jdbc:sqlserver://<sqlserver hostname>:<db port>;databasename=<traveler db name> user=<sqlserver user id> pw=<sqlserver user password>
Example of this usage:
./travelerUtil db set url=jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER user=LNTUSER pw=passw0rd
In a Linux environment, you cannot run the command with the JDBC URL because the database name is delimited from the server name by a required semicolon and the Linux shell interprets this semicolon as a command separator. To avoid this problem, run the command without specifying the parameter:
travelerUtil db set user=<sqlserver user id> pw=<sqlserver user password>
When the system prompts for the JDBC URL, enter:
Example of this usage:
./travelerUtil db set user=LNTUSER pw=passw0rd
travelerutil ssl set
By default, Lotus Notes® Traveler uses regular TCP sockets for communication between the Lotus Notes Traveler server and the HTTP server, and for communications between the Lotus Notes Traveler servers within an HA pool. You might want to use secure sockets for this communication if the networking between the Lotus Notes Traveler servers is not isolated or secure. Note that requiring secure server to server communications might impact overall performance.
To enable the use of SSL sockets between the Lotus Notes Traveler servers, complete the following steps:
- To generate a self-signed certificate with an expiration date far in the future, use the following example:
<domino>\jvm\bin\keytool -genkey -v
Use the same password for the storepass and the keypass. If the password parameters are omitted, the keytool will prompt for them.
- Copy the traveler.jks that was created to each server in the HA pool. A suggested location is \traveler\cfg. It is important for each of the servers to use the same certificate file, so the keytool command should not be run on each server.
- Open a command prompt and change the directory to \traveler\util.
- Run travelerUtil ssl set to configure Lotus Notes Traveler to use SSL:
travelerUtil ssl set keystore=<domino data>\traveler\cfg\traveler.jks key=<password>
Specify the same password that was used for the storepass and keypass parameters with the keytool command.
After making these changes, both the Lotus NotesTraveler task and the HTTP task must be restarted on the Lotus Notes Traveler Server. When the Lotus Notes Traveler server restarts, it will use SSL sockets to communicate with other Lotus Notes Traveler servers.
Repeat these steps for each Lotus Notes Traveler server in the pool. All the Lotus Notes Traveler servers in the pool must be configured the same way; otherwise, they will not be able to communicate with each other.