Upgrade considerations and overview
You can upgrade any previous version of HCL Traveler to the current level. Before you do, understand the considerations and the general steps.
When upgrading, be sure that your operating system and Domino® server levels are supported. If you need to move to a new operating system or newer hardware, see the article Moving HCL Traveler to a new server. If upgrading the Domino® server version at the same time as upgrading the Traveler server, always perform the Domino® server upgrade first followed by the Traveler server upgrade. Here are the detailed steps if upgrading both Domino® and Traveler at the same time.
- Shut down both Domino® and HCL Traveler.
- Remove
TRAVELER
from theServerTasks
list in thenotes.ini
file to prevent Traveler from starting. LeavingTRAVELER
in thenotes.ini
can result in errors on the console due to a mismatch in version levels. These errors will continue to display until both products are upgraded. - Install the new Domino® server.
- Start Domino® and allow it to complete any migration tasks.
- Shut down the Domino® Server.
- Install the new HCL Traveler server (it automatically adds
TRAVELER
back tonotes.ini
) - Start the Domino® server, and HCL Traveler starts automatically.
There are additional configuration items to consider when upgrading the HCL Traveler server:
- You can install and run Traveler on any version of Domino® that Traveler supports. Best practice is to use the latest maintenance level of the Domino® version you choose.
- If you upgrade the Domino® server major version you must re-run the HCL Traveler install to ensure proper binary files are installed. For example, if running HCL Traveler 11.0.0 on Domino® 10.0.1 and you upgrade to Domino® 11.0.0, re-run the HCL Traveler 11.0.0 installer.
- It is best practice to maintain a pilot environment that can be used for upgrade and migration testing prior to upgrading the production environment.