Configure Lotus Domino
This task describes how to change configuration settings for Lotus Domino.
Before you begin
When you install the Web server plug-ins for WebSphere Application Server, as described in Installing Web server plug-ins, the Plug-ins installation wizard configures the Web server.
This topic describes how to reconfigure the Domino V6 Web server. Other procedures in Editing Web server configuration files describe reconfiguring other supported Web servers.
Use the following procedure to enable the Web server plug-in to work with Lotus Domino.
- Start the Domino server.
- Access the names.nsf file using your Web browser (for example, http://tarheels2.raleigh.ibm.com/names.nsf). The browser prompts you for a password.
- Give the administrator name and password.
- Click Configuration on the left side of the page.
- Click Servers on the left side of the page.
- Click All Server Documents on the left side of the page.
- Click the server that you intend to have work with WebSphere Application Server, V6.
- Click Edit Server on the top-left of the center window.
- Click Internet Protocols in the middle of the page.
- Add the path to the Domino plug-in under the DSAPI Section in the middle-right of the page. The plug-in is installed in the bin directory of the Web server plug-ins for WebSphere Application Server.
If specifications for filter files for the Domino Server Application Programming Interface (DSAPI) already exist, use a space to delimit the Web server plug-in for WebSphere Application Server.
- Click Save and Close in the upper-left of the center window.
- Define the location of the plugin-cfg.xml configuration file.
The location varies depending on how you have configured your system. If the Web server and the Application Server are on separate machines, you have a remote installation.
If the two servers are on the same machine, you have a local installation.
If the two servers are on the same machine and the Application Server node or the custom node is federated, you have a local distributed installation.
In the following examples, webserver1 is the Web server definition name. Setting the path to the plug-in configuration file on a Linux or UNIX system
Set the WAS_PLUGIN_CONFIG_FILE environment variable to the location of the plug-in configuration file using one of the following paths:
If the type of installation is: Then use this command to set the environment variable: Remote WAS_PLUGIN_CONFIG_FILE=/opt/ IBM/ WebSphere/ Plugins/ config/ webserver1/ plugin-cfg.xml Local stand-alone WAS_PLUGIN_CONFIG_FILE=/opt/ IBM/ WebSphere/ AppServer/ profiles/ default/ config/ cells/ sa_cell/ nodes/ webserver1_node/ servers/webserver1/ plugin-cfg.xml Local distributed WAS_PLUGIN_CONFIG_FILE= /opt/ IBM/ WebSphere/ AppServer/ profiles/ custom01/ config/ cells/ dmgrcell/ nodes/ managednode/ servers/ webserver1/ plugin-cfg.xml
During the installation process, the Plug-ins installation wizard creates the setupPluginCfg.sh file in two places:
- The plug-ins_install_root/bin directory
- The lotus_install_root/notesdata directory
You can run the script from either location to set the WAS_PLUGIN_CONFIG_FILE environment variable. However, if you are reconfiguring the Web server, you might want to set the path yourself by setting the value of the environment variable with a path from the preceding table.
The setupPluginCfg.sh script sets the file path value to the file path that the wizard configured originally. If you are reconfiguring the Web server to change the original file path, do not use this script. Setting the path to the plug-in configuration file on a Windows system
Add the appropriate statement to your lotus_domino_install_root\notes.ini file:
If the type of installation is: Then use this command to set the WebSpherePluginCfg variable: Remote WebSpherePluginCfg="C:\ Program Files\ IBM\ WebSphere\ Plugins\ config\ webserver1\ plugin-cfg.xml" Local stand-alone WebSpherePluginCfg="C:\ IBM\ WebSphere\ AppServer\ profiles\ default\ config\ cells\ sa_cell\ nodes\ webserver1_node\ servers\ webserver1\ plugin-cfg.xml" Local distributed WebSpherePluginCfg="C:\ IBM\ WebSphere\ AppServer\ profiles\ default\ config\ cells\ dmgrcell\ nodes\ managednode\ servers\ webserver1\ plugin-cfg.xml"
- Restart the Domino server. When the server starts, information similar to the following example is displayed01/21/2005 01:21:51 PM JVM: Java virtual machine initialized WebSphere Application Server DSAPI filter loaded 01/21/2005 01:21:52 PM HTTP Web Server started
This procedure results in reconfiguring V6.x of Lotus Domino.
What to do next
After configuring a Web server, one can install applications on it. See the Applications section of the information center for more information.
For more information on configuring Lotus Domino to work with WebSphere Application Server, search the Lotus Support Services Web site. Enter the search term WebSphere in the keyword search field.
- Enabling single sign-on for Domino and WebSphere Application Server
- Extended Search installation: Using horizontal clusters in WebSphere Application Server
- Prompted to authentication again when using single sign-on (SSO) for WAS and Domino
- Some CGI Variables do not work with DSAPI filter, Domino, and WebSphere Application Server
- WebSphere Application Server plug-in can hang when Domino encounters HTTP Error 500
- Must I install WAS Network Deployment before Lotus Workplace Messaging?
Lotus Domino tips
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.