Network Deployment (Distributed operating systems), v8.0 > Set up intermediary services > Implement a web server plug-in > Edit web server configuration files


Configure Lotus Domino

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

The Web Server Plug-ins Configuration Tool configures the web server plug-in.

Other procedures in Edit web server configuration files describe configuring other supported web servers.

Use the following procedure to enable the web server plug-in to work with Lotus Domino. Ensure that you install the plug-in as root. Domino can only be installed as root, and the configuration files belong to root.

If you install the plug-in as local and the WAS as nonroot, then web server management on WAS, such as generation, propagation, deletion of web server definitions and more, is unavailable because the plugin-cfg.xml file must be installed as root.


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 the product

  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) exist, use a space to delimit the web server plug-in for WAS.

  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 we have configured the system. If the web server and the application server are on separate machines, we have a remote installation.

    If the two servers are on the same machine, we have a local installation.

    If the two servers are on the same machine and the application server node or the custom node is federated, we have a local distributed installation.

    In the following examples, webserver1 is the web server definition name.

    (AIX) (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 paths in this table.

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

    The setupPluginCfg.sh file is created in two places:

    • The plugins_root/bin directory
    • The lotus_root/notesdata directory

    We can run the script from either location to set the WAS_PLUGIN_CONFIG_FILE environment variable. However, if you are re-configuring 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 Web Server Plug-ins Configuration Tool 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.

    If the type of installation is: Then use this command to set the WebSpherePluginCfg variable:
    Remote WebSpherePluginCfg=C:\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

    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.

  13. If you are configuring a 64-bit version of the Domino v7 or higher web server, modify the notes.ini file to point to the plugin_root\bin\64bit/domino5.dll file.

  14. Restart the Domino server. When the server starts, information like the following example is displayed: 
    01/21/2005 01:21:51 PM  JVM: JVM 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 about configuring Lotus Domino to work with WAS, search the Lotus Support Services website. Enter the search term WebSphere in the keyword search field.

Related technotes:

Tip: To unconfigure a web server, reverse the manual steps and remove what was manually added in this procedure.


Related


Lotus Domino file locations and troubleshooting tips
Edit web server configuration files
To configure the WebSphere plug-in

+

Search Tips   |   Advanced Search