HCL Domino 14.0 with FP2 In-Place Upgrade from Domino 12.0.2

Mindwatering Incorporated

Author: Tripp W Black

Created: 10/16 at 08:44 PM

 

Category:
Domino Upgrades / Installations
Software Upgrade

Steps for In-place upgrade of HCL Domino 12.0.2 FPx to
HCL Domino 14.0 and adding FP2 (The latest at the time of writing)

Notes:
- Linux server OS is RockOS 9.x, existing Domino is 64-bit, or course.
- 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.
- See Other Upgrade Notes below for licensing and feature removals.
- Separate installation of Verse is no longer needed with Domino 14, only run a separate Verse set-up if you need to patch Verse beyond Domino for some reason.
- If you are running on a newer Linux than Domino 14.0 supports or you are running Ubuntu (Debian), you can set the following before the ./install: export INSTALL_NO_CHECK=1
- - Make sure your package versions are at leaste:
- - - kernel-5.14 x86_64 or higher
- - - glibc-2.34-28 x86_64 or higher
- - - libstdc++-11.2.1 x86_64 or higher


BEFORE YOU START:
Check server drive disk for free drive space (10 GB min)
Write down or memorize the server program and data folders and the user name (e.g. notes) for verification when going through installation prompts
e.g.
/opt/hcl/domino
/local/notesdata
notes


In-Place HCL Domino Upgrade:
1. Using Filezilla, copy the install file to the server in the server's downloads folder:
a. SSH to Domino server and become root
$ sudo su

b. Make two new directories, dom140 and dom140FP2.
# cd /home/myadmin/Downloads/
# mkdir dom140
# mkdir dom140FP2

c. Transfer the files from the local repository to the server into their respective folders:
Transferred:
Domino_14.0_Linux_English.tar --> dom140
Domino_1400FP2_Linux.tar --> dom140FP2


2. Extract both installations before we shut down the Domino service:
$ cd /home/myadmin/Downloads/dom140
$ tar -xvf Domino_14.0_Linux_English.tar
<watch files extracted>
$ cd /home/myadmin/Downloads/dom140FP2
$ tar -xvf Domino_1400FP2_Linux.tar
<watch files extract>


3. Perform the installation:
$ sudo systemctl stop domino.service
<wait>
$ sudo su
# cd /home/myadmin/Downloads/dom140/linux64
# ./install
<go through the prompts>
<wait>

Notes:
- The steps/questions are the same as version 12, as installation program is still InstallAnywhere. So click <enter> instead of <tab> to accept a setting, and 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. Update if yours if different. We also use /local/notesdata for our data path. Also, 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 14 will be a manual start.

Start the server manually just in case there is a prompt to accept.
# Yes
cd /local/notesdata/
$ su notes
$ /opt/hcl/domino/bin/server
<We were prompted to answer Yes to upgrade the directory>

Notes:
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 a few minutes and just watched it for any issues.

Shutdown the manually started Domino server:
> q <enter>
$ exit
(so we are the (sudo) root user)


4. Patch to the latest FixPack:
# cd /home/myadmin/Downloads/dom140FP2/linux64/domino
# ./install
<go through the prompts>
# exit
(to exit (sudo) root user session)

Notes:
- The steps/questions are the same for 14 FixPacks as with 12 FIxPacks. Use <tab> instead of <enter> to accept a setting. There is no 0 to skip to the end.
- There should not be any prompts for a fix pack so you can manually start Domino or just start the service.


5. Start the Domino service:
$ sudo systemctl stop domino.service
<wait>

Verify the services are running okay:
$ sudo systemctl status domino.service

___


Verse Upgrade from Verse 3.1.x to Verse 3.2.2 (Usually Not Necessary):

Notes:
- By default, Verse is installed/upgraded w/Domino now. Manual install is no longer required.
- These instructions assume this is an upgrade of Verse and that the prerequisite JVM notes.ini settings have already been performed.

1. Using Filezilla, copy the Verse zipped file to the server in the server's downloads folder:
a. SSH to Domino server and become root
$ sudo su

b. Make two a new directories, verse322.
# cd /home/myadmin/Downloads/
# mkdir verse322

c. Transfer the Verse zip file from the local repository to the server into their respective folders:
Transferred:
HCL_Verse_3.2.2.zip --> Verse322


2. Extract the zipped file before we shut down the Domino service:
$ cd /home/myadmin/Downloads/Verse322
$ unzip HCL_Verse_3.2.2.zip
<watch files extract>

$ unzip HCL_Verse.zip

Remove the extra clutter files:
$ rm readme.html
$ rm License.txt
$ rm Notices \& Information.txt


3. Install the Verse Files (perform the upgrade):
$ sudo systemctl stop domino.service
<wait>

$ sudo su

Replace the templates and the servers-lookup jar files:
# cp catalog12.ntf local/notesdata/catalog.ntf
# cp iwaredir.ntf /local/notesdata/iwaredir.ntf
# cp servers-lookup-3.2.2-0.0-44.jar /local/notesdata/
# chown notes:notes /local/notesdata/catalog.ntf
# chown notes:notes /local/notesdata/iwaredir.ntf
# chown notes:notes /local/notesdata/servers-lookup-3.2.2-0.0-44.jar

Remove the old servers-lookup jar:
# rm /local/notesdata/servers-lookup-3.1.0-0.0-14.jar
<y - confirm delete>

Replace the jar files:
# rm /local/notesdata/domino/workspace/applications/eclipse/plugins/ats-*.jar
<y - confirm delete>
# rm /local/notesdata/domino/workspace/applications/eclipse/plugins/sequoia-osgi-*.jar
<y - confirm delete>
# rm /local/notesdata/domino/workspace/applications/eclipse/plugins/core-*.jar
<y - confirm delete>
# rm /local/notesdata/domino/workspace/applications/eclipse/plugins/servlet-*.jar
<y - confirm delete>

# cd /home/myadmin/Downloads/Verse322/eclipse/plugins
# cp *.jar /local/notesdata/domino/workspace/applications/eclipse/plugins/
# chown notes:notes /local/notesdata/domino/workspace/applications/eclipse/plugins/*.jar

Proof w/:
# ls -l /local/notesdata/domino/workspace/applications/eclipse/plugins/
total 91828
-rw-r--r-- 1 notes notes 3615781 Oct 16 21:51 ats-3.2.2-0.0-899.jar
-rw-r--r-- 1 notes notes 18104477 Oct 16 21:51 core-3.2.2-0.0-347.jar
-rw-r--r-- 1 notes notes 72267207 Oct 16 21:51 sequoia-osgi-3.2.2-0.0-899.jar
-rw-r--r-- 1 notes notes 31753 Oct 16 21:51 servlet-3.2.2-0.0-347.jar

# exit
(exit sudo root)


4. Start the domino service:
$ systemctl start domino.service

Verify:
$ systemclt status domino.service
<confirm service is active (running) and Domino tasks are running, verify the messages at the bottom don't include issues>


5. Verify HCL Verse is working
Use a browser and verify that Verse loads with login.



previous page