Configure WebSphere Portal to recognize Lotus Domino and Collaborative Services

You configure the WebSphere Portal server to recognize the server (either an IBMLotus Dominoor non-Lotus Domino server) running the LDAP service so that Lotus Collaborative Services can use that server to support features in Lotus Domino-based portlets. To configure the WebSphere Portal server, you update the CSEnvironment.properties file.

  1. Stop WebSphere Portal:

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

        Windows™: WP_PROFILE/bin

        UNIX™: WP_PROFILE/bin

        IBM i: WP_PROFILE/bin

    2. Enter the following command to stop the WebSphere_Portal server, where WebSphere_Portal is the name of the WebSphere Portal server:

        Windows: stopServer.bat WebSphere_Portal -username admin_userid -password foo

        UNIX: ./stopServer.sh WebSphere_Portal -username admin_userid -password foo

        IBM i: stopServer WebSphere_Portal -username admin_userid -password foo

  2. Locate the CSEnvironment.properties file and make a backup copy before changing any values.

      The file is located in...

        Windows: WP_PROFILE/portalserver/config/config

        UNIX: WP_PROFILE/portalserver/config/config

        i: WP_PROFILE/portalserver/config/config

  3. Use a text editor to modify the CSEnvironment.properties file, and set appropriate values for the following properties, based on environment:

    LDAP property Value
    CS_SERVER_DOMINO_DIRECTORY.enabled The property that determines whether the LDAP directory for Collaborative Services is enabled. Setting CS_SERVER_DOMINO_DIRECTORY.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
    CS_SERVER_DOMINO_DIRECTORY_1.hostname 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
    CS_SERVER_DOMINO_DIRECTORY_1.port 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 UNIX: Default Value: 389
    i: Default Value: 389
    CS_SERVER_DOMINO_DIRECTORY_1.ssl 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. Setting CS_SERVER_DOMINO_DIRECTORY_1.ssl to true enables SSL.
    Recommended Value (SSL): true
    Recommended Value (non-SSL): false
    Default Value: false

  4. Save the changes to CSEnvironment.properties.

  5. Restart the portal server:

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

        Windows: WP_PROFILE/bin

        UNIX: WP_PROFILE/bin

        IBM i: WP_PROFILE/bin

    2. Enter the following command to start the WebSphere_Portal server, where WebSphere_Portal is the name of the WebSphere Portal server:

        Windows: startServer.bat WebSphere_Portal

        UNIX: ./startServer.sh WebSphere_Portal

        IBM i: startServer WebSphere_Portal


Parent

Configure automatic mail detection using a non-Domino LDAP directory


Next topic

Configure a bind user ID for Collaborative Services

 


+

Search Tips   |   Advanced Search