Installing Lotus Domino on an e-smith SME server

Warning - this may not be up to date! For the most recent version of this how-to, check the main website http://www.westcountrybusiness.com

The following installation is based on installing Domino 6.5 on an e-smith SME 5.6. server. However I'm not aware of any major changes that mean that it is not also valid for other version. The usual disclaimers apply - It works for me, but that doesn't mean it will work for you, YMMV and all of that.

Credit where credit's due.

With thanks for the work that went on before ....

The original How-To was created by Jochen Högerl and Ingo Börnig ( SuSE AG ).
Further developed by Nigel Cook, whose notes came to me to produce this current version.

and since ...

Thanks to Jim Gooch of Double6 in the UK for supplying a Domino Server automatic startup script for RedHat (from their own Howto for the Engarde linux server) which I was able to amend for SME.

Why install Domino on a perfectly good SME server?

So why bother adding Domino to an e-smith server that already provides a very reliable platform for e-mail, file sharing etc. It could be seen that the two products don't naturally sit together. Well there's a few reasons that I can see:

• You may come from a Domino background, though not Linux and are looking for a platform to run Domino on without having to learn a new OS. For example, you want you a Domino server at home (or a friends small business) & feel Linux gives you better value than a Windows server, or your Domino experience is on AS400s, so you're not gonna run one of them on that old P233 you've got spare!
• So Linux is the choice & e-smith has to be the easiest 'out-of-the-box' install around. A simple process and you not only have your Linux server, but also a Windows file server, print server, firewall etc. all ready for your Domino install.
• You already know and love the SME box, but want something more. Domino offers excellent groupware facilities, group calendaring, e-mail etc, databases and a full development environment. This website it running on a Domino server & if you want to see a few others, check out http://www.westcountrybusinessassociates.co.uk as an example & look a some of their sites - all in Domino.

So for professional Groupware & the rest, in my opinion, nothing beats Domino - Microsoft may offer comparable e-mail functionality but beyond that the Lotus products are streets ahead.

Price - Domino was formally just too damned expensive for small businesses - some £1,500 (GB£) for a server licence, plus £80 per client. Well not so anymore. IBM have recently started the Express licensing scheme and Lotus Domino is included. If you buy the express licence (only available via the IBM website & costs £82 + vat per user) you pay for the clients, but the server is free. This means that it can now be affordable for the small business user, finally competing in the market with Microsoft Small Business server.

One word of warning though. Although IBM claim to now target small business, to them this seems to be less than 1000 employees, not less than 10. So all works fine, but the website is not the easiest to navigate, you still need to join the passport licence scheme, which is overly bureaucratic for a small business and software is only available to download - so broadband is pretty much a prerequisite. IBM still have a lot to learn about what small businesses genuinely need.

• Install Remote Server Set-up client. This How-To uses the Lotus Remote Server set-up method to configure the Domino Server. This is an option when you install the Domino Administrator Client. If you didn't install it then, get the original install CD and re-run it, simply checking Remote Server Set-up & the install will add it to your Lotus Program Folder.
• The Remote Server Set-up uses Port No. 8585 (by default) so you need to make sure this is not blocked, which it may be if you run your server as a Secure Server or Gateway. Try it first, because it normally works for me. If it is blocked, you have two choices - either re-run the SME 'Configure the Server' option from the Console and set to 'Server Only' mode. You can reset it after the Domino install as its a one-off requirement. Or you Open the Port using one of the SME contribs, such as 'dmc-mitel-portopening' (copy that into Google & search & you'll soon find a download site).
• It is also possible to use the set-up the server using a browser, rather than the Remote Server set-up and so avoid opening the port. I haven't tried this as I know that Nigel Cook (who worked on this document before me) experienced some difficulty. It may well work and you are welcome to try it - let me know how you get on - but having discovered the Remote Server Set-up option, I prefer it and so have not bothered to try the HTTP route again.
• Domino provides services that are already provided by the SME. You will need to decide which you want to use. By default, this install disables HTTP, HTTPS (ports 80 & 443 , not server manager on port 980), POP, IMAP, SMTP and LDAP on the SME and assume the Domino Services will replace them. You may want to enable some of these services again, which you can do post install. See later in this How-To for tips and considerations in doing this.

• Installation should be done as 'root'.
• If you are installing from a CD then place the CD in the drive & mount it (mount /dev/cdrom). Otherwise copy the Domino software to a folder on the e-smith. (e.g. creating an IBAY and copying the file across the network).
• If your Domino installation is a tar file, you will need to extract it. Move to the folder where the file is located and enter:
  'tar -xvf c5167na-DominoServer6.5-Linux.tar' (Note: Make sure you substitute the correct file name of your installation file)
• You can now choose whether to perform a manual or automated installation. The automated installation involves downloading a file from this site and running a few scripts. The manual installation describes what to do if you do not choose to download the file. I would recommend choosing the automated installation, but have left the manual instructions in case you have any problems or want to understand what is actually happening.

Automated Installation

Note: The download is available at our main website at www.westcountrybusiness.com. Click in the Tech Forum link

• Download the file e-smith-domino.tar to the same directory and extract using 'tar -xvf e-smith-domino.tar'
  
• Enter the following command:
  
  e-smith-domino-install
  
• This sets up a new user 'notes' - you will be prompted to give it a password. It then stops all relevant e-smith services and starts the Domino Installation

• This assumes that the Domino Installation is started by the command 'linux\install'. If for some reason your Domino installation requires a different command to start, then just enter this manually.
• To install from CD, you would enter '/mnt/cdrom/linux/install' - assuming the CD is mounted (see above).
• This script stops the e-smith HTTP service that listens on port 80 and 443 (http & https). If you need to access Server-Manager at any time you can still do this. It can be found at either http://sme-Server-ip:980/server-manager or https://sme-Server-ip:981/server-manager.
• For information on deciding which services should be restarted and How To do it, refer to 'Which services should be restarted, if any?' section towards the end of this document.

• I assume if you are setting up a Domino Server then you know what you are doing. Its not too complex, in any case. So this how-to is not intended to cover the Domino configuration.
• If you are creating a new Administrator (rather than using an existin ID from a past install) then remember to tick the box to create the ID file.
• This set by default doesn't set up HTTP & Mail service, make sure you check them on install to set up.
• I have experienced some problems when opting to save / copy ID files to alternative locations for creating local copies. I would advise just accepting the default options then copying the ID files from /local/notesdata/ to wherever you want them. If you are using an Ibay to copy files from your e-smith server to your Windows PCs, then (assuming you are still in an Ibay folder) you need to type 'cp /local/notesdata/*.id' followed by 'chmod 777 *.id'. If you navigate from your windows PC to that Ibay, you will now see the ID files and be able to copy them to wherever you want. NB: For security reasons, make sure you delete unwanted copies of your ID files.
• The Remote Set-up program may not complete automatically. Wait till progress bar has settled on 100% for a suitably safe length of time & close the window manually. The click finish & all is well.

• Create a user 'notes' by typing: (Tip:Where commands are blocked together like the following two, it is safe to select them all, copy & then paste into your terminal session on the e-smith. This will save you the time to re-key).

adduser notes
passwd notes (-->You will be promoted to give password)


• Create a Notes Log directory and set ownership:
  
  mkdir /var/log/notes
  chown notes.notes /var/log/notes
  
  

You now need to edit the '/home/notes/.bashrc' file (e.g. pico /home/notes/.bashrc) and add the following line under the "User specific aliases and functions" heading:

export PATH=$PATH:/opt/lotus/bin:/local/notesdata

Before we start the Domino installation, we need to stop and disable the services on the e-smith that will conflict. There is a section later to help you decide which ones to switch back on again, if any.

Note: We are stopping the e-smith HTTP service that listens on port 80 and 443 (http & https). If you need to access Server-Manager at any time you can still do this. It can be found at either http://sme-Server-ip:980/server-manager or https://sme-Server-ip:981/server-manager.

I considered adding a script file to download, but got lazy. So just select all the following commands and copy / paste them into your e-smith terminal session.

/sbin/service xinetd stop
/sbin/service smtpfront-qmail stop
/sbin/service qmail stop
/sbin/service ldap stop
/sbin/service httpd-e-smith stop
/sbin/e-smith/db configuration setprop xinetd status disabled
/sbin/e-smith/db configuration setprop smtpfront-qmail status disabled
/sbin/e-smith/db configuration setprop qmail status disabled
/sbin/e-smith/db configuration setprop ldap status disabled
/sbin/e-smith/db configuration setprop httpd-e-smith status disabled
/sbin/e-smith/db configuration setprop imp status disabled

Right that's the e-smith ready, now for the Domino installation. I assume you're still in the directory in which you expanded the Domino set-up file (.tar). If so it should have create a directory called 'linux' & the install script is in there. So type:

linux/install

Starting the Domino Server Manually

To start Domino server manually, log on as user 'notes' using the password you entered when creating this user. (Don't run as root, or any other user). Then enter:

cd /local/notesdata
server lotusdomino start

This can also be achieve by the command, which also suppresses the console. This is the command that is used in the automatic setup when the server is booted:

su - notes -c "/opt/lotus/bin/server -jc -c > /dev/null 2>&1 &"

Note: I have noticed a problem when I start Domino from a console window. When I close the PC on which that session is running & switch off, next time I come to access it I get problems connecting to the Domino server. Not sure if that's just me or not. I worked around it by running the Domino Console on the server itself. Go to console, press alt-F2 to start a new session, log on as notes & do the above. Alt-F1 returns to original session (probably e-smith console). I would be interested to know if anyone else has a similar problem.

Which services should be restarted, if any?

You don't actually need to restart any services. Domino is now running as an SMTP server and will also provide POP and IMAP to clients. Its directory supports LDAP and it also runs its own webserver to permit access via HTTP and HTTPS. So you could happily leave every thing as it is and run your Domino Server without problems (hopefully). However consider the following:

• You want to use the e-smith as your webserver or want HTTP access to your IBAYS etc.
• You still want to use the front end e-mail tools for qmail, such as amavis anti-virus.

• In Domino Administrator, open the Sever Configuration document, go to Ports, Internet Ports and change the HTTP port to an alternative (e.g. 81). You can also choose here whether to enable HTTPS and which port it should use.
• Restart the Domino Server. In Administrator, this can be done in Server Tasks, or type Exit in the Domino Console & then start it again.
• Under server tasks you should now see that the HTTP server is listening on the new port.
• To enable HTTP & HTTPS again on the e-smith type (or copy / paste):
  
  /sbin/e-smith/db configuration setprop httpd-e-smith status enabled
  /sbin/service httpd-e-smith start
  
  
• Bear in mind that you now need to specify the alternative port to communicate with Notes. e.g. to test HTTP access to the server NAB (names.nsf) - assuming new port is 81 - type 'http://sme-server-IP:81/names.nsf'
• Remember, if you use the Domino server as a gateway and want to access via an alternative port, make sure the port is open. (see earlier comments at the start of this doc on port opening).
• Tips: You could make life a little easier by adding some 'proxypass' config lines to the httpd.conf file (via templates, of course) to pass calls over port 80 onto the Notes listening server. Haven't tried it myself yet, if I do I'll update the How-To. Or you could add some HTML or PHP redirect or forward into an IBAY so access to the IBAY name forwards to the Domino server. Again, I haven't tried this.

• In Domino Administrator, open the Sever Configuration document, go to Ports, Internet Ports and change the SMTP port to an alternative (e.g. 26).
• Restart the Domino Server. In Administrator, this can be done in Server Tasks, or type Exit in the Domino Console & then start it again.
• Under server tasks you should now see that the SMTP server is listening on the new port.
• Now you have to configure qmail to forward mail to the new port. Ideally you would go to the 'email retrieval' options in Server Manager and add 'localhost:26' (assuming port 26 is new Domino listening port). However, the validation in the server manager panel prevents this.
• So we need to add a template fragment to tell qmail to forward SMTP mail on a different port. To do this, type (or copy / paste):
  
  mkdir -p /etc/e-smith/templates-custom/var/qmail/control/smtproutes
  cp /etc/e-smith/templates/var/qmail/control/smtproutes/10delegateMailServer /etc/e-smith/templates-custom/var/qmail/control/smtproutes
  
  To edit the custom template, open it (e.g. pico /etc/e-smith/templates-custom/var/qmail/control/smtproutes/10delegateMailServer) and change line:
  
  $OUT .= "$DomainName:[$DelegateMailServer]\n";
  
  to
  
  $OUT .= "$DomainName:$DelegateMailServer\n";
  
  and change the line:
  
  $OUT .= "$key:[$DelegateMailServer]\n";
  
  to
  
  $OUT .= "$key:$DelegateMailServer\n";
  
  Note: By default the e-smith adds square brackets around the IP address of the delegate mail server. This doesn't work when the IP address also has a redirected port number. However, even if there is no port number, the syntax without the square brackets will work. So don't worry if you change the delegate mail server through Server Manager later, this change will not stop it working.

So the above template will support a Delegate Mail Server with a port redirection as well. Unfortunately the ServerManager panel does not. So this bit is a little messy - it would be better to amend the validation in the Server Manager function to allow for a port redirection, but here goes:

Note - and this is IMPORTANT - you need to set up a delegate mail server via the Server Manager panel at least once. If you don't do this first, the rest won't work. Remember, you can't enter the forwarding port via the Server Manager panel, so just enter the server IP address, save & exit. then continue with the installation by typing:

/sbin/e-smith/config set DelegateMailServer server-ip:port.

e.g. where the local server is IP 192.168.0.1 and you want to qmail for pass to Domino on port 26, you would type:

/sbin/e-smith/config set DelegateMailServer 192.168.0.1:26

This is using the standard Delegate Mail Server feature available in the e-smith, but worked around the Server Manager validation. Note: If you try and change any settings in the Server Manager panel for E-mail retrieval, it won't let you. You will get an error as it won't like the Delegate Mail Server field containing a port. So you'll have to delete the field, make whatever changes you want, then make this change again. Sorry - told you it needs improving! Don't forget to do the next steps too to rebuilt the template and restart qmail service.