In a high availability (HA) environment, Lotus Notes Traveler servers that are in the same HA pool use the same log settings, except for the location setting of log files.
The location of log files is defined by the "NTS_LOG_ROOT_DIR" parameter in the notes.ini on each server and so is not shared across the HA pool.
If an administrator changes the other setting on one server, this change will be applied to other servers because they refer to the identical setting in the enterprise database.
The method of changing the logging setting for a Lotus Notes Traveler server in an HA pool is the same as the server in a stand-alone environment. For details, see 8.6.1 Log setting and 8.6.2 Log considerations in a stand-alone environment.
Information for HA
The failover information of Lotus Notes Traveler servers and connection to the enterprise database are particular to a high availability environment. These information is included in NTSActivity*.log like other Lotus Notes Traveler information. So an administrator can use NTSActivity*.log to detect problems which occur in a high availability environment.
For example, there are two Lotus Notes Traveler servers, server A and B. If server A goes down when accessed by users, server B will recognize that A is failed and users will be registered to B. This event is recorded in NTSActivity*.log similar to the following:
[Server A IP address] [Server B IP address] "Server A hostname" Dead XXX 0 "XX" Heartbeat 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
User registration information
INFO Alarm-0960 [User DN] [Device ID] StateController.processSymbol#XXX User [User DN] has been registered.
INFO Alarm-0960 [User DN] [Device ID] StateController.processSymbol#XXX Device [Device ID] for user [User DN] has been registered.
When the enterprise database is down, Lotus Notes Traveler server cannot synchronize with devices. This event is recorded in NTSActivity*.log like below:
Lotus Traveler: SEVERE *system Error rollingback Transaction id=XXX Exception Thrown: com.ibm.db2.jcc.am.SqlNonTransientConnectionException: [jcc][t4][4.13.80] invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003
HTTP JVM: Error rollingback Transaction id=34. For more detailed information, please consult error-log-0.xml located in C:/IBM/Lotus/Domino/data/domino/workspace/logs
Lotus Traveler: WARNING *system Status change from Green to Red: Unable to connect to database via jdbc:db2://[database server hostname:port number].
Lotus Traveler: SEVERE *system Error starting a Transaction Exception Thrown: com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][4.13.80] Exception java.net.ConnectException: Error opening socket to server [database server hostname]/[database server IP address] on port [port number] with message: Connection refused: connect ERRORCODE=-4499, SQLSTATE=08001
Note that these are only example. Log contents are different according to differences of environments.
Logs of other components
In a high availability environment, in addition to the Lotus Notes Traveler servers, there are Domino mail servers, load balancers, and enterprise database servers. An administrator must manage logs on all these servers. About how to manage them, see the product documents of load balancer and database. The following are
IBM Mobile Connect document and IBM DB2 document:
IBM Mobile Connect documentation
IBM DB2 Database for Linux, UNIX, and Windows Information Center