|Steps for In-place Upgrade |
of Domino 10.0.1 to Domino 11.0.0 and Traveler from 10.0.11 to Traveler 11
- Linux server OS is CentOS 7.7, existing Domino is 64-bit, or course.
- The JVM changed in Domino R11 to use the OpenJVM libraries. We kept the old Domino data JVM folder, but changed its name to oldjvm.
- The existing start-up script is the Nashed one. It's a few years old, but still worked, so we didn't replace it with the newest one.
- A full step-by-step from a new CentOS 7.7 is also available in this support app titled: HCL Domino 11 on CentOS 7.6 / CentOS 7.7 Step-by-Step Swing Upgrade / Installation
- See Other Upgrade Notes below for licensing and feature removals.
In-Place Domino Upgrade:
1. Using Filezilla, copied the install file to the server in the server's downloads folder.
(In this case, to a dom11 folder in the server's admin user's Downloads folder)
2. Start SSH Terminal to server. View and extract files.
$ ssh firstname.lastname@example.org
We kept a backup of the last Traveler setup incase we needed to refer to them.
$ cd /home/myadmin/Downloads/dom11/
$ ls *
# sudo su
# tar -xvf Domino_11.0_Linux_English.tar
<watched files extracted>
3. Backed-up the jvm folder and Performed the installation.
$ sudo systemctl stop domino.service
$ sudo systemctl status domino.service
... Domino for xLinux (notes) shutdown completed
<ctl + c>
Remove or change the name of the old JVM folder. We don't want it around just in case.
$ mv /opt/ibm/domino/notes/latest/linux/jvm/ /opt/ibm/domino/notes/latest/linux/jvm-old/
$ cd linux64
<go through the prompts>
- The steps/questions are the same. But the navigation is a bit different as the new installation program is InstallAnywhere. So you click <enter> instead of <tab> to accept a setting, and you have to use "0" to get to the end of the license fine print page.
- Since my server has been upgraded over the years, the executable path still shows an IBM based one. So at Program Files Directory Name, we changed /opt/hcl/domino to /opt/ibm/domino. Update if yours if different.
- For Data Files Directory Name, we use /local/notesdata for our data path.
- For User Name, and Group Name, our Domino server user id is notes.
- Major releases always have a directory upgrade, the server "hangs" waiting on the answer. So our first boot into 11 will be manually.
- - There is a new ini for V11 to delay the Directory design upgrade. To enable add the following to the notes.ini on the Domino server: SERVER_UPGRADE_NO_DIRECTORY_UPGRADE_PROMPT=1
Skip to step 5, if this is not the administrative server for the Domino Domain.
4. Modify the lines below for your environment; start the server manually to upgrade the directory.
$ cd /local/notedata/
$ su notes
<answer Yes, with Y>
It might take a bit longer for large directories. But for us, it is done in about 30 seconds.
We let the Domino server run for 30 minutes and just watched it for any issues.
Shutdown the Domino service.
In-Place Traveler Upgrade:
5. Extract the Traveler software:
# sudo su
< password >
# tar zxf TRAVELER_11.0_Linux_ML.tar.gz
# vi installer.properties
- update/verify the program path and the data path.
- uncomment the LINUX_USER_NAME=notes and set to your server's Linux OS name, if not notes.
- uncomment the LINUX_GROUP_NAME=notes and set to your server's Linux OS name, if not notes.
# ./TravelerSetup -f /home/sysadmin/tmp/installer.properties -i silent -l en
The install will notify you that you are upgrading from Traveler 10.x to 11.x, and confirm the paths.
Once done, it should print Installation completed successfully.
6. Start the server manually as the notes user, and start the server normally.
# cd /local/notesdata
# su lotusnotes
Watch the server to make sure it upgrades the design of various databases (e.g. monitoring configuration) and wait for services to start.
Exit being the notes user.
# systemctl start domino.service
< wait >
# systemctl status domino.service
Remove the jvm-old folder if desired:
# rm -rf /opt/ibm/domino/notes/latest/linux/jvm-old/
If all is well. Exit the root user. Exit the SSH session.
Other Upgrade Notes:
The FlexNet server fields in the Configuration Settings doc can be ignored. Domino 11.0 is not yet using this licensing method for Domino servers. See KB0073301 for more info.
The console messages can also be ignored:
Licensing> Invalid length for configuration item 'LicensingServerURL': '0'
Licensing> Failed to get configuration item 'LicensingServerURL'; Invalid arguments
Licensing error: Domino license configuration is not available
There was a licensing models removed:
There were also two features removed:
- XSP mode
- DOTS (Domino OSGi Tasklet Service)