Configure Lotus Domino

This task describes how to change configuration settings for Lotus Domino.

When you install the Web server plug-ins for WebSphere Application Server on a non-iSeries system, the Plug-ins installation wizard configures the Web server.

See Installing Web server plug-ins on i5/OS.

This topic describes how to manually configure the Domino V6 Web server.

If you are running Domino Web Server on i5/OS, use the IBM Web Administration for iSeries GUI. See Creating and configuring an HTTP server instance for more information.

Other procedures in Editing Web server configuration files describe configuring other supported Web servers.

Overview

Use the following procedure to enable the Web server plug-in to work with Lotus Domino.

Procedure

1. Start the Domino server.

2. 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.

3. Give the administrator name and password.

4. Click Configuration on the left side of the page.

5. Click Servers on the left side of the page.

6. Click All Server Documents on the left side of the page.

7. Click the server that you intend to have work with WebSphere Application Server, V6.

8. Click Edit Server on the top-left of the center window.

9. Click Internet Protocols in the middle of the page.

10. Add the path to the Domino plug-in under the DSAPI Section in the middle-right of the page.

    The DSAPI filter location on i5/OS is /QSYS.LIB/QWAS61.LIB/LIBDOMINOH.SRVPGM. 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.

11. Click Save and Close in the upper-left of the center window.

12. 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

    Edit your notes.ini file.

    1. From a CL command prompt, enter the Work with Domino Servers (WRKDOMSVR) command.

    2. Type 13 next to the applicable Domino server, then press Enter.

    3. Add or edit the WebSphereInit property. (See the following table.)

       To add a new line, type "i" next to the desired insertion line, then press Enter.

    4. Press F3 to save and exit.

    If the type of installation is:	Then use this command to set the environment variable:
    Remote	WebSpherePluginConfig profile_root/config/webserver1/plugin-cfg.xml
    Local standalone	WebSpherePluginConfig profile_root/config/cells/my_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml
    Local distributed	WebSpherePluginConfig profile_root/config/cells/my_cell/nodes/my_managednode/servers/webserver1/plugin-cfg.xml

    During the installation process, the Plug-ins installation wizard creates the setupPluginCfg.sh file in two places:

    • The plugins_root/bin directory

    • The lotus_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.

13. Restart the Domino server. When the server starts, information similar to the following example is displayed:

    01/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
    

Results

This procedure results in reconfiguring V6.x of Lotus Domino.

What to do next

After configuring a Web server, you 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. Related technotes:

• Enabling Single Sign-on for Domino and WebSphere Application Servers

• Extended Search installation: Using horizontal clusters in WebSphere Application Server V5.0

• Prompted to authentication again when using SSO for WebSphere Application Server and Domino

• Some CGI Variables Do Not Work with DSAPI Filter, Domino, and WebSphere

• WebSphere Application Server Plug-in Can Hang when Domino Encounters HTTP Error 500

• Do I Need to Install IBM WebSphere Application Server ND Edition Before IBM Lotus Workplace Messaging?

Related tasks

Related information