Configure Lotus QuickPlace and WebSphere Portal to work together

The following topic provides instructions for configuring WebSphere Portal and Lotus QuickPlace.

Use the IBM Web Administration for iSeries Create WebSphere Portal wizard when configuring WebSphere Portal instances. The wizard creates the necessary servers (HTTP and WebSphere Application Server), configures the server for Portal, configures the database for Portal, configures security (LDAP) for Portal, and deploys the portlets installed with the WebSphere Portal product. You can edit the Portal instance configuration manually after you have used the WebSphere Portal wizard.

 

Configure Lotus QuickPlace settings to support WebSphere Portal

This section provides instructions for configuring Lotus QuickPlace settings to support the portal. All of the instructions in this section might not be required for your environment.

Note: You can find many of the steps provided in this section in the QuickPlace 3.0.1 Administrator's Guide. To find more information, go to the Lotus Documentation Library at: http://www.lotus.com/ldd/doc, and locate the QuickPlace 3.0.1 Administrator's Guide.

 

Access the administrative interface for the QuickPlace server

Perform the following steps to access the administrative interface for QuickPlace server.

  1. Start the Domino server.

  2. Open a Web browser and access QuickPlace by typing: http://domino_QuickPlace_server:port_number/QuickPlace where domino_QuickPlace_server is the fully-qualified host name and port_number is the port number for the QuickPlace server.

  3. Click Sign in.

  4. Type the user name and password for the QuickPlace administrator.

 

Configure QuickPlace to use an LDAP server

To configure QuickPlace with an LDAP server, follow these steps.

  1. Sign in to the QuickPlace administrative interface.

  2. Select Server Settings.

  3. Select User Directory.

  4. Click the Change Directory button.

  5. Select LDAP Server as the server type, not Domino server.

  6. Enter the fully-qualified host name of the directory server.

  7. Select Disallow new users.

  8. Click Next.

 

Add users or groups to administer the server

To identify who can administer the QuickPlace server, the following steps are required.

  1. Sign in to the QuickPlace administrative interface.

  2. Select Security.

  3. Click the Add button under Who can administer this server?.

  4. Click the Directory button to select the names of users or groups who can administer the server.

  5. Select the users or groups and then click the Add button.

  6. Click Close.

  7. Click the Next button to view the addition of users who can administer the server.

 

Configure settings to support Sametime people awareness

To configure QuickPlace settings to support Sametime people awareness, the following steps are required.

  1. Sign in to the QuickPlace administrative interface.

  2. Select the Other Options link in the toolbar, and then click the Edit Options button.

  3. To connect to the Sametime server so that awareness can work within QuickPlace, edit the fields for the Sametime Community Server and the Sametime Meeting Server.

  4. Click the Next button.

 

Configure settings to support multi-server single signon authentication

The following settings are required to configure the QuickPlace server in a multi-server single signon environment. To find more information, go to the Lotus Documentation Library online at: http://www.lotus.com/ldd/doc, and locate the QuickPlace 3.0.1 Administrator's Guide.

  1. Enable single signon between WebSphere Application Server and the Domino server

    If you have not done so already, configure single signon between WebSphere Application Server and the Domino server on which QuickPlace is running. Refer to the topic Configure Lotus Domino and WebSphere Portal to work together for instructions on enabling single signon between Domino servers and WebSphere Application Server.

  2. Edit the notes.ini file

    1. Locate and open the notes.ini file for QuickPlace server (Lotus\Domino\notes.ini). The notes.ini contains configuration settings.

    2. Add the following lines to notes.ini: 
      NoWebFileSystemACLs=1
h_ScopeUrlInQP=1

      Notes:

      • The NoWebFileSystemACLs parameter allows anonymous access to files in the HTML directory. If you set NoWebFileSystemACLs=1, anonymous access to files served up in the HTML directory is not allowed.

      • Set h_ScopeUrlInQP=1 tells QuickPlace to make all URL forms include the Place name in the URL so that proper authorizations are set and maintained for each URL of each Place.

      • To debug, you can turn on logging by adding this line to the notes.ini file: QuickPlaceAuthenticationLogging=5

    3. Save and close the notes.ini file.

  3. Edit the Domino Configuration database (domcfg.nsf)

    • If the domcfg.nsf database does not exist for your server, perform the following instructions:

      1. Start the Domino server and login to the Domino Administrator.

      2. From Domino Administrator, select File - Database - New.

      3. Enter the name of the Web server in the Server field.

      4. Type domcfg.nsf for the file name. Important: The file name must be domcfg.nsf.

      5. Click the Template Server button and select your server.

      6. Click the Show advanced templates checkbox.

      7. Select the Domino Web Server Configuration (R5.0) template (domcfg5.ntf).

      8. Click OK to create the database.

    • To map to the QuickPlace login form:
      Note: This is necessary because the login form contains JavaScript that makes single sign-on work with QuickPlace.

      1. Open the domcfg.nsf database. For example, for your server, click the File tab and then open the domcfg.nsf database.

      2. Click Create - Mapping a Login Form.

      3. Type quickplace/resources.nsf in the Target Database file name field.

      4. Type QuickPlaceLoginForm in the Target form name field.

      5. Click File - Save, and then close the form.

 

Verify settings in the notes.ini file

Perform the following steps to verify that DIIOP is enabled as a ServerTask in the notes.ini file.

  1. Locate and open the notes.ini file for QuickPlace server (Lotus\Domino\notes.ini). The notes.ini contains configuration settings.

  2. Ensure that DIIOP is one of the ServerTasks in the notes.ini file. If not, type DIIOP to add it as one of the ServerTasks.

Note: Setting DIIOP as a server task enables the picker feature in the QuickPlace portlets edit mode which enables browsing of QuickPlaces on a given server. In addition to adding DIIOP as a server task, ensure that you enable HTTP clients to browse database for your QuickPlace server. To enable this, use Domino Administrator to locate the Server Document for your QuickPlace server. Edit the server and on the Internet Protocols tab, check Yes in Allow HTTP clients to browse databases.

 

Add the QuickPlace servlet

To enable QuickPlace to work in your collaborative portal, you need to add the QuickPlaceServlet (stored in the Collaborative Components Java archive file cs.jar) to your QuickPlace server. The QuickPlaceServlet ensures that the records of portal users who are registered in portal are synchronized with QuickPlace membership records.

  1. Find the Domino Data servlets.properties file in the QuickPlace server's data directory. If the file does not exist, create it with a text editor.

  2. Open the servlets.properties file in a text editor and add this line:
    3. servlet.QPServlet.code=com.lotus.cs.util.QPServlet

  3. Save and close the file.

  4. Create a directory under <serverdatadir>/Domino called Servlet, if it does not already exist.

  5. Extract the Collaborative Services Web archive file (cs.war) from the Collaborative Services Enterprise Application file (cs.ear) and then extract the Collaborative Services Java archive file (cs.jar) from cs.war.

    6. Find the cs.ear file on the server in the directory -

    /qibm/UserData/webas5/base/<instance>/portalserver5/installableApps/cs.ear

  6. Follow these steps to copy the cs.jar file to a directory on your iSeries system:

    1. Enter the following on an OS/400 command line to create a new directory called WPS1: 
      MKDIR /WPS1

    2. Enter the following command to change the owner of the new directory to QNOTES: 
      CHGOWN OBJ('/WPS1') NEWOWN(QNOTES)

    3. Copy cs.jar to the new directory.

    4. Enter the following command: 
      CHGOWN OBJ('/WPS1/cs.jar') NEWOWN(QNOTES)

  7. Edit the notes.ini file for the QuickPlace server, making the following changes:

    • Add the following line: 
      WPS1=/WPS1/cs.jar

    • Append WPS1 to the JavaUserClassesExt line.

  8. Follow these steps to ensure that Domino Servlet Manager is set for Java Servlet Support:

    1. Start Domino Administrator and type the password for the administrator.

    2. Edit the QuickPlace server document.

    3. Go to Internet Protocols and click Domino Web Engine.

    4. Set Java Servlet Support to Domino Servlet Manager.

    5. Save the close the document.

  9. Ensure that the servlet engine is running. If it is not running, start it from the Domino Server.

 

Test QuickPlace

To test if QuickPlace is working, log in and create a test QuickPlace. For example, perform the following steps:

  1. Create a QuickPlace, add a new member, create a document, and then close the Web browser.

  2. Launch QuickPlace and log in. For example, type http://domino_QuickPlace_server:port_number/QuickPlace where domino_QuickPlace_server is the fully-qualified host name and port_number is the port number for the QuickPlace server.

  3. Click the My Places link, and select the newly created QuickPlace. If the link is working, QuickPlace is running properly.

 

Configure WebSphere Portal to use Lotus QuickPlace

This section provides instructions for configuring WebSphere Portal to use Lotus QuickPlace. Note that if you used IBM Web Administration for iSeries to configure WebSphere Portal for use with QuickPlace, you can skip these steps.

 

Before you begin

Read the following information before you begin.

 

Run the configuration task

To perform the configuration task, do the following:

  1. Open an OS/400 command prompt and start the Qshell Interpreter by entering the following: 
    STRQSH

  2. Change to the directory /qibm/proddata/webas5/pme/bin

  3. Type the following at the command line to stop WebSphere Portal. 
    stopServer -instance <instance> <app_server>

    where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

  4. If you intend to use Domino Directory with Lotus QuickPlace, follow the steps for Configure Collaborative Components to use Domino Directory.

  5. Locate the /qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties file and create a back up copy before changing any values.

  6. Edit the /qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties file and enter the values appropriate for your environment.
    Note the following:

    • Do not change any settings other than those specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

    • You can also modify the wpconfig.properties file locally on your iSeries system by entering the following on an OS/400 command line: 
      EDTF '/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties'

    • Some values, shown in italics below, may need to be modified to your specific environment.

    Section Property Value
    Collaborative Components Properties LCC.QuickPlace.Enabled

    Description: The property that determines whether Lotus QuickPlace is enabled. Note: Setting LCC.QuickPlace.Enabled to true enables this component. Setting the value to false disables it.

    Recommended Value: true

    Default Value: false
    LCC.QuickPlace.Server

    Description: The name of the Lotus QuickPlace server.

    Recommended Value: my.server.com

    Default Value: my.server.com
    LCC.QuickPlace.Protocol

    Description: The protocol used to connect to the Lotus QuickPlace server.

    Recommended Value: http

    Default Value: http
    LCC.QuickPlace.Port

    Description: The port number for the Lotus QuickPlace server.

    Recommended Value: 80

    Default Value: 80
    Database configuration Dbuser

    Description: The user ID for the database administrator.

    Value Type: Alphanumeric text string

    Default Value: ReplaceWithYourDbAdminId
    DbPassword Description: The password for the database administrator.

    Value Type: Alphanumeric text string

    Default Value: ReplaceWithYourDbAdminPwd
    WmmDbUser Description: The user ID for the database administrator.

    Value Type: Alphanumeric text string

    Default Value: ReplaceWithYourDbAdminId

    If you are migrating from a previous version of WebSphere Portal, this value must match the database user name for the WebSphere Member Services database from the previous WebSphere Portal version.
    WmmDbPassword Description: The password for the database administrator.

    Value Type: Alphanumeric text string

    Default Value: ReplaceWithYourDbAdminPwd

  7. Save the file.

  8. Start the Qshell Interpreter by entering the following on an OS/400 command line: 
    STRQSH

  9. Change to the directory /qibm/userdata/webas5/base/<instance>/portalserver5/config

  10. Type the following command:

    • WPSconfig.sh lcc-configure-quickplace

  11. Check the output for any error messages. If you encounter an error, check the appropriate logs file for more information. You can locate information about logs in the Use logs topic.

  12. Change to the directory /qibm/proddata/webas5/pme/bin

  13. Type the following at the command line to start WebSphere Portal. 
    startServer -instance <instance> <app_server>

    where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

Next steps

You have completed this step. Continue to the next step by choosing one of the following topics.

 

See also