How-To: Domino 8 on Ubuntu 7.04 (virtual machine)
NOTICE: this translation isn’t probably the best you can find, but I hope that is better than the google’s one. Even if published consider this post “underway”, if you find some passage unclear leave a comment, I’ll try to explain and eventually update this page.
The inevitable premises: on Linux i’m still a newbie, I know something about Domino but I don’t have experience with other platforms than Windows. For this how-to I have taken most from other guides I’ve found on the web, almost all nearly complete except for a few details. And no, I haven’t mistaken the title, I used feisty and not gutsy because I had not yet VM ready with 7.10, nor with previous versions (like dapper).
VM details
HD with 5 GB, vmware tools built and installed (but not working ‘cause only the console mode was operation, no GUI), updated with the patch of a few days ago (date of the original guide is 5 November 2007), 394 MB RAM, 1 processor, 1 ethernet (bridged mode).The machine was almost ready, if you go on VMTN it can be found without difficulty. To be clear: I can run it without problem on my 3-year-old laptop.
I strongly advise you to not download and directly use the VMTM machine, make some “change” (username, password, networking, etc.).
Prerequisites
The first and most important you’ll never have, not today nor in the near future: Ubuntu supported by Lotus Domino. The installer will say this you too, but let you to proceed anyway.
There are some packages to install, I have aptgetted them as ignorant, found 3 guide that told me to do it, and I decided to trust:
sudo apt-get install libstdc[+][+]2[.]10-.*
sudo apt-get install libstdc++5
sudo apt-get install libxmu6
sudo apt-get install libxp6
sudo apt-get install libxp-java
sudo apt-get install libxtst6
sudo apt-get install gawk
Addittionally to run Domino a specific UNPRIVILEGED user is required, and to access his “data”, I found this option important, even if with Windows was easily achievable often you have problem with that, I appreciate that with linux this choice is by default. For “unprivileged” I mean not only that it isn’t root but It cannot even use SUDO.
sudo adduser notes
Obviously it will be consequently created a group with the same name, which will be asked later in installation. I advise you to follow this guide and not make cut-and-paste, ie use another name for the domino user.
At last but not least we have to re-enable the root user:
sudo passwd root
Domino Install
Nothing too complex, the .sh must be launched as root, do not use sudo because the IBM installer does not like it.And it would be advisable to use bash instead of dash (ubuntu default), but this is something that I have not done (at least in the installation) and it worked anyway.Up to you to load the installer on the machine, burn tar on cd, make iso file, network or who knows whatever else, it does not matter (to me, and this guide), at last unpack and install with shell:
./install -console
During the installation you will be prompted with some questions, answer with common sense if you like, if you do not you’ll probably face some problems some time ahead ( ^_^ ), btw I do not explain how to install Domino with the wizard, It is a classic next-next-next although with CUI. What I suggest you to do is to specify the “remote configuration”, which will leave a daemon listening for remote server setup. You may also leave unconfigured, and choose “manual” and reload in the future with server option “-listen” to configure it.
Setting up the server
Run a remote server setup, available to all those who have installed the administrative client (and relative features). Nothing special to remark, I think it is advisable to start the setup by an 8 client, but isn’t mandatory ‘cause I did it from a 7.02 and no problem emerged (as far as I know/tested).
Garbage collecting
With Domino installed with success (or at least I did, I hope is the same for you), now is time to do some clean-up on the system. For sure I’m not a good linux sysadmin, because “sudo” does not disturb me and I think it’s just a different way of seeing things, as long as this does not give technical problem and the distribution is built specifically for using that, I’ll prefer use it instead of root. Therefore we must log-off as root and disable it again (sudo passwd -l root).
Needless to say, It is better to remove the installer files.
Boot/Start/Stop scripts
We will still use the old Init scripts even if Ubuntu use Upstart because it seems there is compatibility, and I don’t know how to rewrote them, or at least not completely. I used these with some changes. Take only the script, and modify the parameters, such as:
#!/bin/sh
with
#!/bin/bash
and
su - $domino_user -c "cd ${data_dir}; cat ${passwd_file}|${bin_dir}/server" >> $output 2>&1 &
with
su - $domino_user -c "cd ${data_dir}; cat ${passwd_file}|${bin_dir}/server =/local/notesdata/notes.ini" >> $output 2>&1 &
It would be more elegant to modify using the variables inside the script, but since I have not yet had the opportunity to test I prefer to public this awful patch.
And copy to /etc/init.d .
Now we’re ready to update rc scripts for Domino:
sudo update-rc.d domino defaults
Jump over this command above unless you want to run Domino at machine startup.
Now login with the user created for Domino, move to the correct path and start the server manually as follows:
server =/local/notesdata/notes.ini
Quit when he finished the classic “first start”.
Test
Check the behavior of VM, tested the various commands and functions, and enjoy. They should not present anomalies.
Thanks to:
http://ubuntuforums.org/showthread.php?t=110892
Desktux
S. Beatty Consulting
Svaried Blog, a bit of Linux, in itagliano 