6.3 Moving from Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone to a high availability environmentAdded by Whei-Jen Chen on January 3, 2013 | Version 1 (Original)
Integrating an existing Lotus Notes® Traveler 8.5.3 Upgrade Pack 1 stand-alone servers into a Lotus Notes Traveler High Availability pool
After this process is complete, all synchronization and administration data is automatically transferred to the HA pool database. This process is useful for consolidating an existing set of servers into a single HA pool.
This is useful to
move off existing
servers or transitioning to a different operating system (OS). For example, Windows™ 32-bit servers are not supported in a High Availability pool. However, it is possible to configure a Lotus Notes Traveler server running on a Windows 32-bit server to join an HA pool, regardless of the OS of the servers in the pool. The server data is automatically transferred to the HA pool database and then the Windows 32-bit server can be removed from the configuration.
When integrating an existing Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone server into a Lotus Notes Traveler High Availability pool, consider the following:
- During the transfer of data from the internal database to the enterprise database, the server is unable to serve devices requests. This transfer process can take several hours, depending on the amount of data.
- Lotus Notes Traveler clients do not support changing the server address after provisioning. This means that to support the integration of existing servers with existing clients, the existing server address must be aliased to the front end address (external URL) for the HA pool. Please note: SSL certificate(s) may need to be revoked and installed on the Load balancer supporting the server addresses.
- The new server URL is /traveler. However, for backwards compatibility with existing Lotus Notes Traveler clients, /servlet/traveler is still supported.
- Once a server has been configured for an HA pool, the original internal database data is removed. It is possible to reconfigure an HA server as a stand-alone server, however, any synchronization state data will have to be recreated as devices synchronize with the server after this is done.
There are two strategies for integrating existing servers into an HA pool:
- Building up the HA pool only from existing servers:
The advantage of this strategy is that no additional servers are required for the Lotus Notes Traveler servers. The disadvantage is that you cannot validate the configuration until at least one of the servers has been reconfigured for HA.
- Setting up a new HA pool and then integrate the existing servers into the pool:
The advantage of this strategy is that the initial HA configuration can be validated without impacting the existing users. Then the integration of the existing servers can be staged. At the end of the integration, excess servers can be removed from the configuration. The disadvantage of this strategy is the requirement for additional hardware, at least until the integration is complete.
The following integration checklist assumes the second strategy:
- Set up and validate the initial Lotus Notes Traveler High Availability pool.
Note that after the new environment is set up and validated, new users can be provisioned for the HA pool.
- Upgrade all of the existing Lotus Notes Traveler servers to the same version/release utilized by the HA pool.
During the upgrade process, existing data and configuration is migrated as necessary. Depending upon the size of the database this process can take a while. Note that during this upgrade process, the server will not be available for device requests.
- Configure the server for secure communication (optional).
If the HA pools is configured for secure server to server communication, enable this on the existing servers that will join the HA pool. See step 3 in the below section for assistance with this.
- Configure an existing Lotus Notes Traveler server for the HA pool database.
This configuration change will not take affect until the server is restarted.
- Restart the server.
Upon start, the server detects that it is now configured for an HA environment and starts transferring all of the user and administration data to the HA pool database. The server is not available for requests until the data transfer is complete.
- Validate the configuration.
After the transfer is complete, the server is registered as part of the HA pool. This can be validated from the web administration interface or from any server in the pool.
- Update the network configuration such that the server address is aliased by the front end sprayer, this is published URL that users access from their devices, for the HA pool. See your documentation for your IP sprayer for assistance with configuring this.
Update the front end sprayer to service this server
- Update the external server URL setting for the server to coincide with the front end sprayer for the pool.
- Repeat steps 3 through 8 for each server to be integrated into the HA pool.
Setting up a new HA pool and integrating an existing servers into the pool
Follow these instructions to install Lotus Notes Traveler server based on the platform as described in 3.2 Lotus Notes Traveler installation on Linux
. To set up and configure for High Availability pool, follow instructions described in 4.3.3 Lotus Notes Traveler configuration for high availability
Compete these steps to setting up a new HA pool and then integrate the existing servers into the pool:
- Set up and validate the initial Lotus Notes Traveler High Availability pool.
The installation considerations for a server that is to be part of an HA pool are as follows:
Upgrade all of the existing Lotus Notes Traveler servers to the same version/release utilized by the HA pool.
- Each Domino® Server running Lotus Notes Traveler should be registered for the same domain
- Each Domino Server running Lotus Notes Traveler should be co-located in the same data center to reduce latency for inter-server communication
- The external URL setting for Lotus Notes Traveler must be the same for each Lotus Notes Traveler in the pool, and can be setup after installation. This should be the front end IP sprayer's address.
Follow instructions as described in 6.2 Upgrading to 8.5.3 Upgrade Pack 1 from a previous version of Lotus Notes Traveler.
Configure the server for secure communication (optional).
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.
It might be desirable 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 will impact overall performance.
To enable the use of SSL sockets between the Lotus Notes Traveler servers, use the following steps:
Configure an existing Lotus Notes Traveler server for the HA pool.
- 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 just created to each server. A suggested location is \traveler\cfg. It is important for 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 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 Traveler 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.
You can add an exiting Lotus Notes Traveler server to an HA pool by configuring this Lotus Notes Traveler server to use the enterprise database that the servers on the pool shared. When you configure a stand alone server to use an enterprise database, the server migrates existing user and security information to the enterprise database. However, if you are moving from an enterprise database to another database, enterprise or stand-alone, no user or security data is migrated.
To configuring the Lotus Notes Traveler server to use the enterprise database, follow the steps outlined in section 4.3.3 Lotus Notes Traveler configuration for high availability