We installed Traveler around 2010 on Ubuntu and have been upgrading Ubuntu (via do-release-upgrade) and Domino and Traveler in-place. However, we want to move Ubuntu to 64-bit. Therefore, we are installing a new VM.
STEP 1: Install and Prep New Server:
Install the 64-bit server addition of Ubuntu 16.04.
When selecting packages, add the SSH package.
After reboot update the system:
$ sudo apt-get update
$ sudo apt-get upgrade
Configure UFW:
$ sudo ufw allow proto tcp to any port 22 from 192.168.n.0/24
$ sudo ufw allow proto tcp to any port 22 from 10.0.n.0/24
$ sudo ufw allow proto tcp to any port 1352
$ sudo ufw allow proto tcp to any port 443
$ sudo ufw allow proto tcp to any port 80
$ sudo ufw allow proto tcp to any port 8642
$ ufw enable
$ ufw status
Set-up the server with a static IP:
$ sudo vi /etc/network/interfaces
Update like following:
auto ens160
iface ens160 inet static
address 192.168.n.123
netmask 255.255.255.0
network 192.168.n.0
broadcast 192.168.n.255
gateway 192.168.n.1
dns-nameservers 192.168.n.1 123.123.123.123
dns-search mindwatering.internal mindwatering.com
$ sudo service networking restart
Create the new server user (e.g. notes or lotusnotes):
$ sudo useradd -d /home/notes -m notes
$ sudo passwd notes
Increase file-handles for Domino.
Edit /etc/security/limits.conf using sudo and add or modify the lines:
$ sudo vi /etc/security/limits.conf
Add / modify the following lines:
notes soft nofile 20000
notes hard nofile 65535
(where notes is / will be the o/s username for the server. Use 49152 for 32 bit Linux and use 66635 for 64 bit Linux)
Create the notesdata folder:
$ sudo mkdir /local/notesdata
$ sudo chown -R notes /local/notesdata
$ sudo chgrp -R notes /local/notesdata
STEP 2: Transfer /local/notesdata to the New Server:
Shut down Traveler on old server / VM. Leave OS running.
OLD- $ sudo service domino stop
Use FileZilla or some other utility (e.g. rsync) to copy all of /local/notesdata to the new server.
Server OLD /local/notesdata/ --> NEW /local/notesdata/
There can easly be 100000 files easy to transfer. Therefore, I use sshpass and rsync typically, since it's much faster. Below is my command line to copy from the old server to the new server:
$ sudo apt-get install sshpass
Connect mannually to get the old server's SSH key:
$ ssh sysadmin@10.10.10.10
Now we can perform transfer:
$ sudo sshpass -p ' myoldserverpassword' rsync -avz --no-perms --no-owner --no-group sysadmin@10.10.10.10:/local/notesdata/* /local/notesdata/
Change the ownership again as necessary:
$ sudo chown -R notes /local/notesdata
$ sudo chgrp -R notes /local/notesdata
STEP 3: Install Domino and Traveler:
Install 64-bit Domino:
Notes:
Copy the install files for Domino and Traveler to the server (e.g. /home/sysadmin/tmp)
You must end up w/a Domino version same or higher than one one being copied. To the server it will look like an upgrade. For example, if the old server is Domino 9.0.1 FP7, install the full Domino 9.0.1, and then
$ cd /home/sysadmin/tmp/
$ sudo tar -xvf DOMINO_9.0.1_64_BIT_LIN_XS_EN.tar
$ cd linux64/domino
$ sudo -s
# ./install
... answer "yes" to continue in console mode
.. 1 for Next
.. 1 to accept the agreement
.. 0 for no partition upgrade and to continue
.. 1 for Next
.. <enter> to take default program directory ( /opt/ibm/domino )
.. <enter> to take No for partitioned server
.. 1 for Next
.. <enter> to take default data directory ( /local/notesdata/ )
.. 1 for Next
.. <enter> to take the domino server's user name ( notes )
.. <enter> to take the domino server's group name ( notes )
.. <enter> to take the option to setup server manually ( X Manual - 0 )
.. 1 for Next
.. 0 for Domino Enterprise Server
.. 1 for Next
Review installation answers for accuracy.
.. <enter> to read down the page
.. 1 for Next
After installation, we need to redo the FT and view indexes:
# su lotusnotes
$ cd /local/notesdata
$ /opt/ibm/domino/bin/fixup -F
(wait)
$ /opt/ibm/domino/bin/compact -c
(wait)
$ /opt/ibm/domino/bin/updall -R
(wait)
Let's apply the fixpack to the same or higher than the old server's level.
$ exit
(returns us to the sudo root user)
# cd /home/sysadmin/tmp/
# rm -rf linux64/
# tar -xvf domino901FP8_linux64_x86.tar
Edit the NIC.pm file, around line 80, removing "defined" Perl function called as it is deprecated in Perl 5.22 and higher.
# cd linux64/domino/tools/lib
# vi NIC.pm
So this line:
if (defined(@{$scr->{target_hosts}})) {
... becomes ...
if (@{$scr->{target_hosts}}) {
# cd linux64/domino/
# NUI_NOTESDIR=/opt/ibm/domino
# export NUI_NOTESDIR
# ./install
.. <tab> to continue
.. 1 for accept license
.. <tab> to continue and install
Check the notes.ini for NTS_IPC_TCP_Port and NTS_IPC_TCP_Port2 lines. If they exist, update them to any new IP.
# vi /local/notesdata/notes.ini
Install JRE/JDK for Traveler install (needs one):
$ sudo apt-get install default-jdk
Install unzip:
$ sudo apt-get install unzip
Remove the install directory:
# rm -rf linux64/
Extract Traveler FULL installation:
Note: Install doesn't create a folder but extracts to current folder.
# cd /home/sysadmin/tmp/t14/
# tar zxf IBM_TRAVELER_9.0.1.14_LNX_ML.tgz
# vi installer.properties
- verify the program path and the data path.
- uncomment the LINUX_USER_NAME=notes and set to your server's Linux OS name.
- uncomment the LINUX_GROUP_NAME=notes and set to your server's Linux OS name.
# ./TravelerSetup -f /home/sysadmin/tmp/installer.properties -i silent -l en
Extract Traveler Fix Pack:
# cd /home/sysadmin/tmp/tfixpack/
# tar zxf Traveler_90117_Linux.tar.gz
# vi installer.properties
- verify the program path and the data path.
- uncomment the LINUX_USER_NAME=notes and set to your server's Linux OS name.
- uncomment the LINUX_GROUP_NAME=notes and set to your server's Linux OS name.
# ./TravelerSetup -f /home/sysadmin/tmp/installer.properties -i silent -l en
Note:
For the IBM_Traveler_9.0.1.20_LNX_ML.tar.gz, file, tar reported as not a gz file, when I processed it as a .tar file, it expanded successfully. I used the tar -xvf options instead.
Update the silent installer.properties file as we will not be using a GUI:
# vi installer.properties
- verify the program path and the data path.
- uncomment the LINUX_USER_NAME=notes and set to your server's Linux OS name.
- uncomment the LINUX_GROUP_NAME=notes and set to your server's Linux OS name.
# ./TravelerSetup -f /home/sysadmin/tmp/installer.properties -i silent -l en
Test the install:
# su lotusnotes
$ cd /local/notesdata
$ /opt/ibm/domino/bin/server
$ exit
Autostart service files:
(We like the Nash ones.)
In file domino, update the DOMINO_USER and DOMINO_START_SCRIPT path to the rc_domino_script.
In file domino.service, update the User line to your OS LInux Domino user, update the ExecStart and ExecStop to /opt/ibm/domino/...
In file rc_domino_script, updated the DOMINO_CONFIG_FILE and the DOMNO_DEFAULT_CONFIG_FILE path to the /etc/domino/rc_domino_config, and update the $DOMINO_USER line 42, from notes to your Domino OS username as needed, and update line 45, LOTUS path to /opt/ibm/domino.
In file rc_domino_config_notes, update the LOTUS path line to /opt/ibm/domino.
# cd /home/sysadmin/tmp/
# mv domino /etc/init.d/
# mv rc_domino_script /opt/ibm/domino/
# mkdir /etc/domino/
# mv rc_domino_config_notes /etc/domino/
# mv domino.service /etc/systemd/system/
Make sure all but the config file are executable.
# service domino start
or
# systemctl start domino.service
_______________________________________________________________________
Other Notes:
If you have lots of users and your system was up-and-running for a long time, which on Linux is quite common, your database might need defragging.
After upgrade, using the Domino console, stop the Traveler service and HTTP and run Traveler with the defrag option:
> tell traveler quit
<wait>
> tell http quit
<wait>
> load traveler -defrag
Note: Traveler will start HTTP automatically after completing its database management. Verify that it did okay.
Once we say this after a Traveler 9.0.1.18 update, this Traveler release was beyond the version specified in an IBM PMR. So we just had Traveler update the table via the Domino console with the command below. The error went away and functionality was fine.
-- Traveler Error: WARNING "system Exception caught trying to create constraint PK_INVMAP on Table INV_MAP...
> tell traveler sql ALTER TABLE inv_map ALTER COLUMN devuid NOT NULL
previous page
|