Deployment checklist for HA

This section contains a high level check list of the process to deploy a High Availability pool.

The specifics on each of these steps is contained in the Installing and Configuring sections.

The recommended minimum configuration for a HCL Traveler HA Pool is as follows:
  • Two Domino® servers running HCL Traveler
  • One DB2 server, Microsoft™ SQL server, or MySQL server (two database servers, if you want High Availability of the HCL Traveler data)
  • One server running the IP sprayer/load balancer (two servers, if you want High Availability)
Note: For specific information on hardware and software required for this release, see the system requirements for your HCL Traveler version.

Condensing the number of servers (for example, running the database server with a HCL Traveler server) can create single points of failure, as well as create performance bottlenecks.

Setting up a HCL Traveler High Availability pool consists of some initial infrastructure setup as well as steps for each individual server.

Initial infrastructure setup

To set up your infrastructure, perform the following procedure. You only need to perform these steps once.
  1. Deploy an enterprise database server and create the HCL Traveler database on a separate server from the HCL Traveler servers. For more information, see Deploying and configuring the enterprise database.
  2. Deploy the front end load balancer/IP sprayer. It's possible you may already have one that can be utilized. For more information, see Deploy an IP sprayer or load balancer.
  3. Update your firewall(s) or other network equipment to support the sprayer to server and server to database connections. See Planning your network topology for network port information.

Setup for individual servers

Complete the following setup steps for each HCL Traveler server to be added to the HA pool:
  1. Install HCL Domino® server and validate its functionality. All Domino® servers in the HCL Traveler HA pool should be in the same Domino® domain.
  2. Install HCL Traveler and validate its functionality. See Installing the HCL Traveler server for more information.
  3. Configure HCL Traveler to use the enterprise database server and validate its functionality. For more information, see Configuring HCL Traveler for enterprise database.
  4. Update the front end sprayer to include the new HCL Traveler server in the load balancing/sprayer configuration.
  5. Update the external URL setting for the server to point to the front end sprayer. This will be a single URL access for all servers in the HA pool. For more information, see Setting the external server URL.

    This step is not required on each server if you enable common configuration for all HCL Traveler servers in the pool.

Optional setup considerations

The following setup considerations are optional but recommended:
  • Set up the server pool to share configuration information. For more information, see Setup for common configuration (optional).
  • Set up and configure the enterprise database to be highly available.
  • Set up and configure the front end sprayer to be highly available.
  • Configure the HCL Traveler servers for secure server to server communication. For more information, see Enable server to server secure communications (optional).
    Note: There will be a performance impact to enabling secure sockets for server to server communications. Depending upon your network configuration, this step may not be required.