WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows


 

Configuring the WebSphere Portal Express server to recognize Lotus Domino and the Collaborative Services

You run the Lotus Domino configuration task on the IBM® WebSphere® Portal Express server. Running the task allows the portal to recognize the presence of the server (either an IBM Lotus® Domino® or non-Lotus Domino server) running the LDAP service, so that Lotus Collaborative Services can use the server to support features in Lotus Domino-based portlets, primarily auto-detection of mail files.

WebSphere Portal Express (which includes Collaborative Services) must be installed before you can run this task.

You run the configuration task by entering commands at a command line on the WebSphere Portal Express server.

Commands are case sensitive.

Note: During the instructions for this task, you will edit the wpconfig.properties file. Create a backup copy of this file before performing the following instructions.

For security reasons, you should not store passwords in the wpconfig.properties file. Edit the wpconfig.properties before running a configuration task, inserting the passwords needed for that task. Then, after the task has run, delete all passwords from the wpconfig.properties file.

Perform the following steps to run the configuration task:

  1. Use the following commands to stop WebSphere Portal Express:

    1. Open a command prompt and change to the following directory:

      • Windows: wp_profile_root\bin
      • Linux: wp_profile_root/bin
      • i5/OS: wp_profile_root/bin
    2. Enter the following command to stop the WebSphere_Portal server:

      • Windows: stopServer.bat WebSphere_Portal -user admin_userid -password admin_password
      • Linux: ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password
      • i5/OS: stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password
    where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example wp_profile.Note: The default name of the application server is the profile name.
  2. Locate the wpconfig.properties and wpconfig_dbdomain.properties files and make a backup copy of each before changing any values. The files are located in the following directory:

    Windows: wp_profile_root\ConfigEngine\properties

    Linux: wp_profile_root/ConfigEngine/properties

    i5/OS (UserData): wp_profile_root/ConfigEngine/properties

  3. Use a text editor to open the appropriate configuration properties file and enter the appropriate values for your environment. Note the following:

    Section of wpconfig.properties file: Lotus Domino Directory Properties

    LDAP Property Value
    LCC.DominoDirectory.Enabled

    Description: The property that determines whether the LDAP directory for Collaborative Services is enabled.

    Note: Setting LCC.DominoDirectory.Enabled to true enables this component. Setting the value to false disables it. Despite the name of the property, a non-Domino LDAP directory can be specified.

    Recommended Value: true

    Default Value: false

    LCC.DominoDirectory.Server

    Description: The fully qualified distinguished name of the LDAP directory for Collaborative Services. Despite the name of the property, a non-Lotus Domino LDAP directory can be specified.

    Recommended Value: my.server.com

    Default Value: my.server.com

    LCC.DominoDirectory.Port

    Description: The port number for the LDAP directory for Collaborative Services. Despite the name of the property, a non-Lotus Domino LDAP directory can be specified.

    Recommended Value: 389

    Windows and Linux: Default Value: 389

    i5/OS: Default Value: 389

    LCC.DominoDirectory.SSL Description: The property that determines whether the LDAP directory for Collaborative Services is enabled to communicate over SSL. Despite the name of the property, a non-Lotus Domino LDAP directory can be specified.Note: Setting LCC.DominoDirectory.SSL to true enables SSL.

    Recommended Value (SSL): true

    Recommended Value (non-SSL): false

    Default Value: false

  4. Save the file.
  5. Change to the wp_profile_root/ConfigEngine directory and type the following command: Windows:
    ConfigEngine.bat lcc-configure-dominodirectory
    Linux:
    ./ConfigEngine.sh lcc-configure-dominodirectory
    i5/OS (UserData):
    ConfigEngine.sh -profileName profile_root lcc-configure-dominodirectory
  6. Check the output for any error messages. If you encounter an error, check the appropriate logs file for more information.
  7. Use the following commands to start WebSphere Portal Express:

    1. Open a command prompt and change to the following directory:

      • Windows: wp_profile_root\bin
      • Linux: wp_profile_root/bin
      • i5/OS: wp_profile_root/bin
    2. Enter the following command to start the WebSphere_Portal server:

      • Windows: startServer.bat WebSphere_Portal
      • Linux: ./startServer.sh WebSphere_Portal
      • i5/OS: startServer WebSphere_Portal -profileName profile_root
      where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example wp_profile.

Advanced configurations for using Collaborative Services and Domino Directory are available.

Tip: The task lcc-configure-dominodirectory is specific for configuring Collaborative Services to use Domino Directory only. It is possible to change and save other Collaborative Services values in wpconfig.properties, and then run the configuration task ./ConfigEngine.sh lcc-configure-allConfigEngine.bat lcc-configure-all (Windows) to configure multiple Domino and Extended Products servers at once. Parent topic: Checklist of tasks: LDAP server for Lotus Collaborative Services Previous topic: Starting the LDAP service automatically on a Lotus Domino server Next topic: Specifying the Internet host name of the Lotus Domino server Related concepts
WebSphere Portal Express logs Collaborative Services environment properties
Library | Support | Terms of use |