+

Search Tips   |   Advanced Search

 

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.

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

Other procedures in Edit 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.

    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.

    [AIX] [HP-UX] [Linux] [Solaris]    

    Setting the path to the plug-in configuration file

    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/WAS/Plugins/config/webserver1/plugin-cfg.xml
    Local standalone WAS_PLUGIN_CONFIG_FILE=profile_root/config/cells/sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml
    Local distributed WAS_PLUGIN_CONFIG_FILE=profile_root/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 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.

    [Windows]    

    Setting the path to the plug-in configuration file

    Add the appropriate statement to your lotus_domino_root\notes.ini file: Do not delimit any of the following file paths with quotation marks unless there is a space in the file path. Otherwise, the plugin-cfg.xml file might not load correctly.

    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 standalone WebSpherePluginCfg=profile_root\config\cells\sa_cell\nodes\webserver1_node\servers\webserver1\plugin-cfg.xml
    Local distributed WebSpherePluginCfg=profile_root\config\cells\dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml

  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 WAS 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 WAS, search the Lotus Support Services Web site. Enter the search term WebSphere in the keyword search field. Related technotes:


Lotus Domino file locations and troubleshooting tips

 

Related tasks


Edit Web server configuration files

 

Related information


To configure the WebSphere plug-in