This section describes configuration and verification of HTTP server.
Ensure that the hosts names you want to use for HTTP can be resolved to the machine which will host Domino, and that firewalls allow access to the server box by port 80 and 443, also, if SSL will be configured later.
Your operating system supports many types of HTTP servers. You need to find out if any other HTTP server is running on the operating system which will host the Domino HTTP server. HTTP servers may be installed to run as services or as daemons that autostart with the startup of the operating system. Unless otherwise configured these applications will bind by to port 80, the default port, and may include port 443, the conventional SSL port for all HTTP servers, including the Domino HTTP server. If a conflict occurs Domino will report that HTTP cannot bind to port 80 and HTTP will not start, although the rest of the server tasks will continue to start up.
You can find out if any other HTTP servers run on your machine before you install Domino.
• Examine the component services for the Windows operating system to find all of the services installed which may or may not be running at the time. If you find other HTTP servers , unless you wish to reconfigure them to work with Domino HTTP, then you may need to set the other HTTP servers to manual or disabled to allow Domino HTTP to bind to port 80 when it starts.
• Open a browser on the machine and point to localhost. If it answers, you have another HTTP server running.
• Open a command prompt and run netstat -nao, noting any IP address listening on port 80, indicated by a dotted set of four numbers followed by a colon and 80.
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 6492
In this example the results of netstat -nao
show an IP of 0.0.0.0:80
, generally meaning any available IP on the machine, showing that the PID 6492 has bound to port 80.
To find out the name of the application, for Windows operating systems, run Task Manager. In Task Manager select View
and check PID.
Then the Task Manager will show both the application name and its process ID.
Task Manager shows that the PID belongs to the Apache HTTP server. Unless modified this will conflict with the Domino HTTP server start and configuration.
HTTP server installation
When you see the Internet service window during installation of the Domino server click “Web browsers (HTTP Services)
“ so that the HTTP server will be started with the Domino server. The HTTP task will be entered, also, in the notes.ini to so that HTTP will be started on each Domino server start.
Testing for HTTP server responsiveness and access
You can test HTTP response and connectivity of the Domino HTTP server in several ways.
• Enter show tasks
in the Domino console. The result should show HTTP listening on port 80.
HTTP Server Listen for connect requests on TCP Port:80
• Open a browser on the machine and point it to http://[hostname]/homepage.nsf
Domino installs with homepage.nsf as the default homepage for the HTTP server.
• Open a browser on a workstation in the network and point it to http://[hostname]/homepage.nsf
If either of these steps fail then make sure that Domino HTTP can be reached on the network IP address by substituting the IP for the host name. If this works then modify DNS to allow the host name to be resolved to the machine.
If your browser can open homepage.nsf on the machine itself but not on a workstation external to the machine, then check for access to Domino over port 80 by examining the firewall on the host machine. You may, also, test access by opening a command prompt on your workstation and enter telnet [hostname] 80
or telnet [IP] 80
. This should result in a blank page and flashing cursor. If you do not see this, you may see, rather,
C:\>telnet [host] 80
Connecting To [host]...Could not open connection to the host, on port 80: Connect failed
This indicates that a firewall or network appliance does not allow access to the server over port 80.
Host name field in the server document
The host names field in the Server document->Internet protocols->HTTP
tab holds the fully qualified host name of the Domino HTTP server when that particular host name will be used, if necessary, for binding to one host name for HTTP, for use by the iNotes redirection database
to build a redirection URL, and used in URL's for
. Other applications may look to this field for integration purposes, for example, the iNotes portlet for Portal configuration.
Configuration of the HTTP server for user log in
You will want to confirm configuration of the HTTP server for user log in. By default users may login by
• Notes hierarchical name, Philippe Babineaux/Demos
• Canonical name, cn=Philippe Babineaux/o=Demos
• Distinguished name, cn=Philippe Babineaux,o=Demos
• Common name, which, also, can be any name in the User name field of the person document, Philippe Babineaux
• Email address, Philippe.Babineaux@demos.ibm.com
You can allow users to login with the shortname, also by setting the Server document->Security tab->Internet access->Internet authentication
to More name variations with lower security
. Restart the Domino HTTP server to enable this setting; enter in the Domino console
restart task http
Most if not all server processes can be restarted with the the restart task [task name]
phrase. For HTTP do not use the older command tell http restart
nor tell http refresh,
both of which were common for Domino R5.x versions. Using the older commands may not clear the HTTP cache properly to allow enabling the new configuration.
In practice you will see this setting used frequently to allow users to authenticate by their shortname. If after a Domino server restart users cannot authenticate to the Domino server then attempt to authenticate using the common name of the person. If the common name works to authenticate the user then check this field to ensure whether it had been reset for Less name variations.
Configuration of multi server signon among the Domino servers and the WebSphere Application Server allows users to authenticate once and be authenticated to each server in the environment which shares the MSSO token. A token created on the WAS server can be imported into the Domino server at the creation of a Web SSO configuration document, which contains all the names of the Domino servers to share the token. MSSO allows the user to pass seamlessly from a portal login to work with iNotes based mail, Quickr places, provides for Sametime awareness across the environment, and access to Lotus Connections, as well.
For multi server sign on configuration for this environment , see 5. Implement and test single sign-on
Multi server signon can fail abruptly when the configuration document becomes corrupted. You can find evidence of this when users login to one server and then receive another prompt to login when switching to another server in the same DNS domain shared by servers in the MSSO configuration. You can track this by entering in the Domino console:
set config debug_sso_trace_level=2
The Domino console may report that the token is invalid
. If this occurs you can
1. re-import the token into the Web SSO configuration document, replicate it to the servers which share the configuration document and restart HTTP on each server, or
2. delete and create a new Web SSO configuration document, replicate it to the servers which share the configuration document and restart HTTP on each server
You may access further information online about MSSO
iNotes mail access
You need to ensure that your environment meets the minimum system requirements for
IBM Lotus iNotes 8.5.2
or IBM Lotus iNotes 8.5.3
, depending on your implementation. For this environment Domino 8.5.2FP3 was installed initially then upgraded to Domino 8.5.3
, adding Domino 8.5.3IF1
to take advantage of available enhancements and fixes.
Since Domino 8.0 by default the mail files for all registered users contain the template design for iNotes mail. Earlier versions required template replacement to enable features for Domino Web Access, DWA, the feature name for iNotes before Domino 8.0.
You can find online information concerning details and examples for iNotes customization
and for the iNotes forms database
, which gives iNotes its unique functions and interface.
You can find further information on the Domino HTTP
server setup and use, and more information for iNotes mail