Task
Notes:
- Domino installation already performed
- Domino using Internet Sites with CerMgr and the CertStore.nsf on standard ports 80 and 443.
- Desktop policies already exist with apps to push to the Desktop so that just like normal Desktops, Nomad will create Local reps
- The web browser must support/enable storage for apps.
WARNING:
- These instructions are primarily for a new Nomad install; if upgrading, ensure to backup any customized files in nomad-files.
- See post upgrade steps further below.
Server: nomad.mindwatering.net
OS Sudo User Account: myadminid
OS Domino Account notes
Program Folder: /opt/hcl/domino/notes/latest/linux/
1. Transfer install to Server
a. Download HCL Nomad from HCL Software site
- my.hcl-software.com/downloads/domino/nomad/1.0.20 --> HCL_Nomad_server_1.0.20_linux.tar.gz
b. Use SCP/Filezilla to transfer to Domino server:
HCL_Nomad_server_1.0.20_linux.tar.gz --> /home/myadminid/tmp
2. Uncompress and Install:
a. Uncompress:
Notes:
- The files need to be owned by root when placed into the /opt/hcl/domino/notes/latest/linux folder. We'll sudo su - to be root for the extraction so we don't have to go through changing ownership.
- If you server has been upgraded for many releases, your program folder may be different (e.g. /opt/ibm/domino...)
- If this is a nomad upgrade, perform the backup steps now before proceeding. (See an overview of steps bottom of this tech-note.)
$ ssh myadminid@nomad.mindwatering.net
<enter password>
$ cd ~/tmp/
$ sudo su -
<enter password>
# tar -xvzf HCL_Nomad_server_1.0.20_linux.tar.gz
# ls -l
<view files - most will need to be moved into place, but a couple e.g. license can be left here>
b. Move files to the program folder:
# mv nomad /opt/hcl/domino/notes/latest/linux/
# mv nomad-files/ /opt/hcl/domino/notes/latest/linux/
# mv nomad.sf /opt/hcl/domino/notes/latest/linux/
d. Update notes.ini to add nomad to the list of startup tasks and append the NOMAD_WEB_HOST ini setting:
Note:
- If we update notes.ini while the service is running, we may get a warning that the notes.ini was updated while we were editing. If so, cancel the edit and go into notes.ini again and perform the edit again.
- The ServerTasks line will be near the top, append the nomad task at the end of the list. If you reopen the notes.ini, we'll see that the Domino server will move Nomad from the end of the lists and place it before HTTP and CertMgr.
- Add the new Nomad_Web_Host ini setting at the bottom.
# vi /local/notesdata/notes.ini
...
ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched,RnRMgr,Nomad,CertMgr,HTTP
...
NOMAD_WEB_HOST=nomad.mindwatering.net
<esc>:wq (to save)
Note:
- If this is a nomad upgrade, before starting Nomad, perform the upgrade tasks next.
3. Start Nomad:
Domino Administrator client --> Nomad server selected (left menu) --> Server (tab) --> Server Console --> Live (button)
> load nomad
<wait a second>
4. Verify Nomad:
Note:
- In our case, we have nomad.mindwatering.net behind a reverse proxy and we re-map 443 outside to nomad's internal 9443 port.
web browser --> nomad.mindwatering.net:9443
---
Upgrade Tasks
1. Backup pre-upgrade:
Note:
- HCL desires the nomad-files folder to be deleted after backup. It may as well be a mv instead of a cp.
a. Stop nomad task:
Domino Administrator client --> Nomad server selected (left menu) --> Server (tab) --> Server Console --> Live (button)
> tell nomad quit
b. Backup/remove nomad-files:
$ ssh myadminid@nomad.mindwatering.net
<enter password>
$ sudo su -
<enter password>
# mkdir /local/nomad-files-backup/
# mv /opt/hcl/domino/notes/latest/linux/nomad-files /local/nomad-files-backup/
2. Restore Customizations:
Note:
- Restoration of files is needed if you customized any within the /local/nomad-files-backup/config/ backup folder.
- If you customized the compressed notes.ini used w/in nomad - NOT /local/notesdata/notes.ini, but /nomad-files/waspreload/data/....ini.gz, merge the changes.
a. Merge customized version(s) of a config file back within ../config/ back to /nomad-files/config/
- Check (diff) the file(s) beforehand and copy-paste/edit the newly installed configuration file and manually paste the customization back instead.
- For the ../waspreload/data/...ini.gz file, only diff and then copy-paste/edit the changes. The ini is more likely to change between nomad versions.
previous page
|