Clustering IBM Lotus Quickr 8.5 for WebSphere Portal: An end-to-end guide

Jeff JohnsonWebSphere Portal Customer Enablement TeamIBM Collaboration SolutionsIBM Software GroupDurham, NC US

February 2011

© Copyright International Business Machines Corporation 2011. All rights reserved.

Summary: This guide describes the comprehensive, step-by-step procedure for installing, configuring, and building an IBM® Lotus® Quickr® 8.5 for WebSphere® Portal cluster.

Table of Contents1 Introduction .............................................................................................................................. 2 2 Installing and configuring the Deployment Manager ................................................................ 3

2.1 Upgrading the DM ............................................................................................................. 7 2.2 Configuration changes for Quickr 8.5 install .................................................................... 12

3 Installing the primary WebSphere Portal node ....................................................................... 17 3.1 Start the installation program .......................................................................................... 18

4 Configuring the primary node to remote database ................................................................. 29 5 Installing the secondary WebSphere Portal node .................................................................. 47 6 Configuring security on the clustered Quickr environment ..................................................... 53 7 Configuring IBM HTTP Web Server for a clustered environment ........................................... 67

7.1 Install Web Server ........................................................................................................... 67 7.2 Install the plug-in for WebSphere Application Server ...................................................... 71 7.3 Configure Lotus Quickr to use the Web Server ............................................................... 77

8 Troubleshooting ..................................................................................................................... 78 8.1 Error in wpinstalllog.txt .................................................................................................... 78 8.2 Administration links not available or do not work ............................................................. 81 8.3 Bus security ..................................................................................................................... 82 8.4 Error in Place Center and no places displayed ................................................................ 83 8.5 Problem collecting data ................................................................................................... 84 8.6 Places not displayed on second node ............................................................................. 85

1

9 Conclusion ............................................................................................................................. 85 10 Resources ............................................................................................................................. 85 11 About the author .................................................................................................................. 86

1 IntroductionBuilding and configuring a cluster can be a very complex task. There are various ways to build Lotus Quickr 8.5 for WebSphere Portal (hereafter called “Lotus Quickr) clusters; this white paper provides a best-practice approach for building a Lotus Quickr cluster environment using:

• IBM WebSphere Application Server 6.1.0.29 • Microsoft® Windows® 2008 Server• IBM DB2® v9.5 Server• IBM Tivoli® Directory Server v6.1• IBM HTTP Server 6.1

The example in this paper results in a typical two-node horizontal cluster, as shown in Figure 1. Due to lab space limitations, however, one machine is used to host both the secondary node and Deployment Manager, which is not recommended in a production environment owing to performance concerns.

Figure 1. Two-node horizontal cluster arrangement

Your environment might require special considerations, but this document can be used as an overall guide. This guide is specifically written for 64-bit Lotus Quickr 8.5 and WebSphere

2

Application Server v6.1.029, but the same approach applies to other platforms, like AIX and Linux.

In the instructions for configuring Lotus Quickr with the database and LDAP, the screens shots show valid examples; use values that are appropriate for your database and LDAP.

2 Installing and configuring the Deployment ManagerIn this section we install the WebSphere Application Server Deployment Manager (DM) and prepare it for the future Quickr cluster. All the following steps are performed on the server you intend to use as your Deployment Manager:

1. From the Quickr Product CDs disk, navigate to \windows\ia32\ifpackage\WAS\ and launch install.exe. Note that this CD number may vary between operating systems; however, the CD title is “WebSphere Application Server Network Deployment for Windows 64-bit.”

2. Click Next on the Welcome Screen to proceed with the installation (see figure 2).

Figure 2. Welcome screen

3. Select the radio button to Accept the license agreement, and then click Next (see figure 3).

Figure 3. Software License Agreement window

3

4. Enter the directory in which Network Deployment Server will be installed (see figure 4). Click Next.

Figure 4. Installation directory window

NOTE: It's best to keep the path short because going forward, the configuration files could have problems if the full path becomes longer than 256 characters, causing an issue on Windows platforms.

4

5. From this point, you must decide whether to create the DM profile during installation or wait until after the installation is complete, using the profile creation tool. Do NOT select the “Cell (deployment manager and a managed node)” option; WebSphere Portal cannot use the managed node that would install the cell environment (see figure 5).

Figure 5. Environments window

NOTE: If you still prefer to create the DM profile after the installation is complete, you should review the WebSphere Application Server Information Center for details on how to do this.

6. Click the checkbox to Enable Administrative security, enter a user ID and a password, and click Next (see figure 6). Note that VMM Federated File Security is enabled here. The Quickr installer is expecting default security to be set for the Deployment Manager.

5

Figure 6. Enable Administrative Security window

7. On the Summary window, click Next for the IBM WebSphere Application Server Network Deployment Manager and profile to be installed (see figure 7).

Figure 7. Installation Summary window

8. The final windows displays indicating whether the install was successful (see figure 8). Click Finish to complete.

6

Figure 8. Installation Results window

2.1 Upgrading the DMNow we need to upgrade the DM to version 6.1.0.29. To do this:

1. Copy the WebSphere Application Server update installer from Quickr Product Disk W-Setup/was6_fixes/win into the Deployment Managers directory. The 6.1.0.29 fixpack is in the Maintenance directory.

NOTE: For Windows 64-bit systems, the WebSphere Application Server update installer is located in the W-Setup/was6_fixes/win64 directory.

2. Copy the JavaTM directory from the Deployment Managers directory into the directory for the update installer.

3. Stop the Deployment Manager server and run update.bat to open the Update Installer and perform the upgrade (see figure 9). Click Next.

7

Figure 9. Update Installer wizard

4. Select the installation directory of the Deployment Manager (see figure 10), and click Next.

Figure 10. Product Selection window

5. Select the option, “Install maintenance package,” and click Next (see figure 11).

8

Figure 11. Maintenance Operation Selection window

6. Select the updateinstaller\maintenance directory that was copied from the CDs earlier (see figure 12).

Figure 12. Directory Selection window

7. Ensure all fixes are selected and click Next (see figure 13).

9

Figure 13. Select Maintenance Packages to Install window

8. A warning displays indicating that existing fixes and fixpacks will be uninstalled, so the new fixpack and fixes can be installed (see figure 14).

Figure 14. Warning message

9. Click Next to install the required fixpack and fixes (see figure 15).

10

Figure 15. Installation Summary window

10. The Installation Complete window displays, confirming whether the install was successful (see figure 16). Click Finish.

Figure 16. Installation Complete window

11. Once complete, test to make sure that the DM will start and that you can still access it. Start the DM by issuing a startManager.bat command from DM_root/profiles/DMGR01/bin.

11

Access the admin console again to ensure you are able to connect. Once confirmed, a few configuration changes are needed for the Quickr 8.5 installation.

2.2 Configuration changes for Quickr 8.5 install 1. Log in to the administrative console for the DM and increase its HTTP connection timeouts:

a. Select System administration – Deployment Manager – Web container transport chains (see figure 17).

b. For the WCInboundAdmin and WCInboundAdminSecure entries listed in the "Web container transport chains" section, complete the following steps to increase the timeout values:

i. Click HTTP Inbound Channel.ii. Change the Read timeout value to 180.iii. Change the Write timeout value to 180.iv. Save the configuration changes.

Figure 17. DM HTTP connection timeouts

2. Change the timeout request period for the Java Management Extensions (JMX) connector:

a. Select System administration – Deployment Manager – Administration Services – JMX connectors – SOAPConnector – Custom Properties (see figure 18).

b. Select the requestTimeout property, and increase the value from 600 to 6000.c. Save the configuration changes.

12

Figure 18. DM requestTimout property

3. Update the maximum Java heap size used by the DM:

a. Select System administration – Deployment manager – Java and Process Management – Process Definition – Java Virtual Machine (see figure 19).

b. Update the value in the Maximum Heap Size field, using a value of at least 1408 MB.c. Click OK, and then save your changes.

Figure 19. Maximum Heap Size

13

d. Copy the following files from W-Setup/filesForDmgr/ to your Deployment Manager folder:

app_server_root\lib\wkplc.comp.registry.jar app_server_root\lib\wp.wire.jar app_server_root\plugins\com.ibm.ws.portletcontainer.deploytask_6.1.0.jar was_profile_root\config\.repository\metadata_wkplc.xml

e. Restart the DM and ensure that it's operating properly. On the WebSphere Application Server Network Deployment node, start the deployment manager by running the startManager script, entering app_server_root\\bin\\startManager.bat.

f. After the DM starts, launch the administrative console with the following URL:

http://dmgr_hostname:9060/ibm/console

where dmgr_hostname is the fully qualified host name of the WebSphere Application Server Network Deployment node.

4. Log in to the DM administrative console and increase its HTTP connection timeouts:

a. Select System Administration – Deployment Manager – Web container transport chains.b. For the WCInboundAdmin and WCInboundAdminSecure entries listed in the "Web

container transport chains" section, complete the following steps to increase the timeout values (see figure 20):

i. Click HTTP Inbound Channel.ii. Change the Read timeout value to 180.iii. Change the Write timeout value to 180.iv. Save the configuration changes.

14

Figure 20. Read/Write timeouts

5. Change the timeout request period for the Java Management Extensions (JMX) connector:

a. Select System administration – Deployment Manager – Administration Services – JMX connectors – SOAPConnector – Custom Properties (see figure 21).

b. Select the requestTimeout property, and increase the value from 600 to 6000.

Figure 21. requestTimeout property

6. Update the maximum Java heap size used by the DM:

a. Select System administration – Deployment manager – Java and Process Management – Process Definition – Java Virtual Machine (see figure 22).

15

b. Update the value in the Maximum Heap Size field, using a value of at least 1408 MB.c. Click OK, and then save your changes.

Figure 22. Maximum Heap Size

7. On the administrative console, navigate to Users and Groups – Manage Groups:

a. Click Create, and create a group called wpsadmins.b. Navigate to Users and Groups – Manage Users, and click click Create.c. Perform the following steps to create the Quickr Administrative user:

i. Enter the values for the new administrative user (this user should be used when installing primary and secondary nodes).

ii. Click the Group Membership button.iii. From the right-hand menu, select “wpsadmins”, and click Add.iv. Click Close, and then click Create, to create the user.

8. Copy the following files from W-Setup/filesForDmgr/ to your Deployment Manager folder:

NOTE: This step is required, or else the cluster setup process done during installation will fail.

• app_server_root\lib\wkplc.comp.registry.jar • app_server_root\lib\wp.wire.jar

16

• app_server_root\plugins\com.ibm.ws.portletcontainer.deploytask_6.1.0.jar • was_profile_root\config\.repository\metadata_wkplc.xml

9. Restart the DM. Configuration of the DM is now complete.

3 Installing the primary WebSphere Portal nodeThis system serves as the basis for the applications shared by the cluster members. The installation process installs Lotus Quickr, federates the node to the DM, and creates the cluster with the primary node as the first cluster member.

First, perform the items on this checklist:

➢ Make sure that the system on which you are installing meets the supported hardware and software requirements for the product, per the IBM Support document, “IBM Lotus Quickr detailed system requirements.”

➢ Make sure the user ID used during installation must have administrator authority.

➢ If you are using a firewall on the system on which you are installing, disable it while you perform the installation. If you do not do so, and the installation program detects it, a warning message will display during the installation.

➢ If you have antivirus software running, temporarily disable it before performing the installation. The antivirus software may interfere with the installation and cause it to fail by obtaining exclusive locks on files during its scans.

➢ Between the installation of the primary and secondary nodes, there is the option of performing a database transfer to a remote database server. Detailed instructions begin with the Quickr Product Documentation topic, Transferring to DB2. A database transfer can also be performed after secondary nodes have already been added to the cluster.

➢ Create a <qkr_install_root>/wp_profile/PlaceCenterCollections directory on one of the cluster servers to contain a Places catalog index. Make sure the directory has enough space for your deployment; 1 GB is usually enough. The primary node must have write access to the directory, and all other nodes must have read access.

In Step 12 of this section below, you will specify this as the location of Shared Resources for PlaceCenter Collections. For more information on configuring places catalogs for clusters, refer to the topic, Configuring places catalog for clusters.

17

➢ To configure a clustered environment for search, users must create a shared directory called jcr/search on a server in the network, ensuring that each node in the cluster has network access to the directory. For more information about configuring search in clusters, see the topic, Configuring search for Lotus Quickr content in clusters.

3.1 Start the installation program1. If you have the Setup disc, insert it into the CD drive. The installation program automatically

starts when you insert the Setup disc. If the autostart function is disabled, use the install.bat command from the root directory of the CD.

If you downloaded the product code, extract all the files and use the install.bat command from the root directory of the product download.

2. Select the language for the installation and click OK (see figure 23).

Figure 23. Select a language window

3. The Welcome screen displays (see figure 24). If you want to view the Information Center for Lotus Quickr, click the Launch Information Center button to open it in a browser; otherwise, click Next.

18

Figure 24. Welcome screen

4. Select the option “I accept both the IBM and the non-IBM terms” (see figure 25). Click Next.

19

Figure 25. Software License Agreement window

.

5. Select Enterprise Cluster, and click Next (see figure 26).

Figure 26. Select installation type

20

6. Select the database management system system (see figure 27). If DB2 is selected, a new instance of DB2 will be installed on the machine on which the installation is run. After the initial installation, you can transfer to a remote DB2 instance (see Transferring to a remote DB2 database).

Figure 27. Select the DBMS

7. Specify the directory in which you want to install Lotus Quickr, and click Next (see figure 28). If the directory that you specify does not exist, it will be created. Note the following:

• Do not include periods (.) in the installation path.• To avoid problems related to excessively long path names, use a short installation path

name; for example, C:\Quickr instead of C:\Program Files\IBM\Quickr.• If DB2 is the selected database, the DB2 installation path is based on the Lotus Quickr

installation path.

21

Figure 28. Select install directory

8. Select Primary Node and click Next (see figure 29).

Figure 29. Select node type

22

9. Specify the following server information (see figure 30) and click Next:

• The name that you want to use to identify this node in the cell. Typically, this value is the same as the host name for the computer. Note that the node name must be unique among other node names in the same cell.

• The fully qualified host name of the computer that is running the server.

Figure 30. Quickr server information

10. Specify the server information for the DM system, and enter the name you want to use for the cluster (see figure 31). Click Next.

IMPORTANT: Ensure that the DM is running while you are performing the Lotus Quickr installation or else the installation will fail.

NOTE: • The default value for the deployment manager port number is 8879. If you used a

different port number when you installed the DM, use that port number here instead.• When specifying the cluster to be created, do not use spaces or special characters.

23

Figure 31. DM information

Before continuing, verify that the system clock of the primary node is synchronized with the system clock of the deployment manager. The system clocks must be within 5 minutes of each other, or the node federation fails.

11. Enter the user ID and password to access Lotus Quickr and its supporting infrastructure services with administrator authority (see figure 32). Do not use spaces in either the user ID or the password, and ensure that the password is at least five characters in length. Click Next.

24

Figure 32. Admin user ID and password to access Lotus Quickr

• To streamline the installation process, the installation program uses this user ID and password to configure Lotus Quickr and all its related services. This does not mean a single user ID and password are used, but rather that the same user ID and password are used in several places to configure required services.

If you do not want to continue using this user ID and password for Lotus Quickr and its related services, you can change these values after installation. This user ID and password are also used to enable security on the deployment manager.

• The installation uses this user ID, with the password that you enter on this window, to configure DB2 and create an account on the local system. If you prefer to use an existing user ID or do not want to use this user ID for your database, you can change the database user ID and password after installation by using the configuration wizard included with the product.

• Lotus Quickr provides a fully secured environment immediately upon installation, and the strength of that security starts with the password that you select during installation. Avoid using a password that is the same as the user ID, and create a strong password by making it

25

lengthy, combining letters and numbers (both upper and lower case), and avoiding spaces or words found in a dictionary.

IMPORTANT: Because this password is used to create an account on the local system, make sure that the password you enter conforms to any character and length policies used by your organization.

Permitted characters: When entering the user ID and password, you can use characters a-z, A-Z, period (.), hyphen (-), and underscore (_). You can also use DBCS characters in the user ID, though not in the password. Refer to the topic, “Special characters in user IDs and passwords,” for more information about acceptable special characters.

12. Enter the location of the Shared Resources for PlaceCenter Collections (see figure 33). This is a shared folder that you created on one of the servers in your cluster called \\ServerName\PlaceCenter\Collections. The shared network folder need not be on one of the servers in the cluster, but it does need to be accessible from all nodes in the cluster.

The Universal Naming Convention (UNC) format, \\\\your_server\\your_share\\jcr\\search, is the required input format; for example, \\\\hostname.example.com\\share\\jcr\\search.

Figure 33. Shared resources location

NOTE: To use a locally mapped drive for the shared resources location, you must first install it, using the UNC format.

26

13. Select whether you want to run Lotus Quickr as services, and click Next (see figure 34).

Figure 34. Select to run as a service

14. Verify the components to be installed, and click Next (see figure 35).

Figure 35. Components to be installed

27

After the installation is under way, use the progress indicators and the process monitoring facilities of your operating system to monitor the overall progress of the installation.

15. When the installation is complete, a confirmation page displays. Before you click Finish, however, note the following information:

• The fully qualified URL to access Lotus Quickr is displayed, with the port number on which Lotus Quickr receives requests. Make a note of the URL, particularly the port number specified in the URL.

16. Now click Finish, and then verify that the cluster has been created and that the Lotus Quickr server is running as a cluster member:

a) Log in to the administrative console for the deployment manager.b) Select Servers – Clusters, and verify that the cluster you created is displayed.c) Click the cluster name, click Cluster members, and verify that the Lotus Quickr

application server is displayed.

17. Verify that Lotus Quickr can launch. Open a browser window and enter in the URL mentioned at the end of the Lotus Quickr installation.

4 Configuring the primary node to remote databaseNow that the Quickr primary node is installed, it is best practice to transfer the database to a remote server. So when the secondary node is installed, it will automatically pick up the settings of primary node and be connected to the same remote database. To do this:

1. Navigate to the quickr_root/wp_profile/wizard directory and run the wizard, or wizard64, to start the wizard. Click Next (see figure 36). Note that the default maximum number of connections to DB2 is 8, so you may need to increase the number of database connections (see the DB2 Support Technote, “SQL1041N The maximum number of concurrent databases have already been started.”)

28

Figure 36. Configuration wizard welcome screen

2. Select the “Configure the database” option and click Next (see figure 37).

29

Figure 37. Select configuration task

3. Enter the username and password used when you installed the primary node. Click Next (see figure 38).

30

Figure 38. Specify username and password for WebSphere Application Server

4. Select “Transfer data to another database” and click Next (see figure 39).

31

Figure 39. Select database task

5. Select “Transfer data with individual domains” and click Next (see figure 40).

32

Figure 40. Select the transmission mode

6. Verify that each of the listed source domains are set to DB2. Click Next (see figure 41).

33

Figure 41. Source database type

7. Verify that each of the listed target domains is set to DB2. Click Next (see figure 42).

34

Figure 42. Target database type

8. Enter the information for the DB2 installation that was created during the primary node install (see figure 43).

35

Figure 43. Properties for source DB2 database

8. Enter the DB information for where you are transferring database to (see figure 44).

36

Figure 44. Properties for target DB2 database

9. Enter the source and target database information for the Community realm (see figure 45).

37

Figure 45. Source and target database information for Community realm

10. Enter the source and target database information for the Customization realm (see figure 46).

38

Figure 46. Source and target information for Customization realm

11. Enter the source and target database information for the Feedback realm (see figure 47).

39

Figure 47. Source and target information for Feedback realm

12. Enter the source and target database information for the JCR realm (see figure 48).

40

Figure 48. Source and target information for JCR realm

12. Enter the source and target database information for the LikeMinds realm (see figure 49).

41

Figure 49. Source and target information for LikeMinds realm

13. Enter the source and target database information for the Release realm (see figure 50).

42

Figure 50. Source and target information for release realm

14. Enter the source and target database information for the PlaceCenter realm (see figure 51).

43

Figure 51. Source and target information for PlaceCenter realm

14. Enter the source and target database information for the Search Center realm (see figure 52).

44

Figure 52. Source and target information for Search Center realm

16. Enter the source and target database information for the Quickr Admin realm (see figure 53).

45

Figure 53. Source and target information for Quickr Admin realm

17. Finally, confirm everything is correct in the Preview Information window, and click Next (see figure 54).

46

Figure 54. Preview Information window

18. Once completed, click Finish (see figure 55).

47

Figure 55. Task completed successfully window

It is recommended to stop and start the Quickr Server via the DM and then test that you can still access and create a place as a test. If you prefer to manually transfer the database, follow the steps outlined in the topic, “Transferring individual domains manually.”

5 Installing the secondary WebSphere Portal nodeWhen a secondary node is installed, the node is federated without including any of its applications. This is because the cell can contain only one set of these applications, and the applications were already included when the primary node was federated.

1. Start the installation program by issuing the install.bat command from the setup disk.

2. Select the language for the installation and click OK. The welcome screen displays.

3. Select the option, “I accept both the IBM and the non-IBM terms.” Click Next.

48

5. Select Advanced Enterprise Cluster, and click Next.

6. Select the database management system system (DBMS) type. If DB2 is selected, a new instance of DB2 will be installed on the machine on which the installation is run. Use the same DBMS used for the primary node. Click Next.

7. Specify the directory in which you want to install Lotus Quickr, and click Next. If the directory that you specify does not exist, it will be created. NOTE:

• Do not include periods (.) in the installation path.• To avoid problems related to excessively long paths names, use a short installation path

name; for example, C:\\Quickr, instead of C:\\Program Files\\IBM\\Quickr.• If DB2 is the selected database, the DB2 installation path is based on the Lotus Quickr

installation path.

8. Select Secondary Node, and click Next (see figure 56).

Figure 56. Select the node type

9. Specify the following server information and click Next (see figure 57):

49

• The name you want to use to identify this node in the cell. Typically, this value is the same as the host name for the computer. Note that the node name must be unique among other node names in the same cell.

• The fully qualified host name of the computer that is running the server.

Figure 57. Quickr server information

10. Specify the server information for the deployment manager (DM) system, and enter the name of the cluster to which you are adding the new cluster member (see figure 58).

IMPORTANT:• Ensure the DM is running while you are performing the Lotus Quickr installation, or else the

installation fails.• The default value for the DM port number is 8879. If you used a different port number when

you installed the DM, use that port number here instead.• Use the same cluster name used for the primary node install.• Before continuing, verify that the system clock of the primary node is synchronized with the

system clock of the DM. The system clocks must be within 5 minutes of each other, or the node federation fails.

50

Figure 58. DM system information

11. Enter the user ID and password to access Lotus Quickr and its supporting infrastructure services with administrator authority (see figure 59). Do not use blanks in either the user ID or the password, and ensure the password is at least five characters in length. Click Next.

NOTE: The user ID and password you enter here must exactly match the user ID and password you used when installing the primary node.

51

Figure 59. Admin user ID and password

12. Select whether you want to run Lotus Quickr as a service, and click Next (see figure 60).

Figure 60. Select to run as service

52

13. Verify the components to be installed, and click Next (see figure 61).

Figure 61. Components to be installed

After the installation is under way, use the progress indicators and the process monitoring facilities of your operating system to monitor the overall progress of the installation.

14. When the installation is complete, a confirmation page is displayed.

Before you click Finish, however, notice that the fully qualified URL to access Lotus Quickr is displayed, with the port number on which Lotus Quickr receives requests. Make a note of the URL, particularly the port number specified in the URL.

15. Now click Finish, and verify that the cluster has been created and the Lotus Quickr server is running as a cluster member:

a) Log in to the administrative console for the DM.b) Select Servers – Clusters, and verify that the cluster you created is displayed.c) Click the cluster name, click Cluster members, and verify that the Lotus Quickr

application server is displayed.

53

16. Finally, verify that Lotus Quickr can still launch from the primary node, and that it can launch from the new secondary node. Open a browser window and first enter the primary node URL. After that page renders, enter the secondary node URL mentioned at the end of the Lotus Quickr install.

6 Configuring security on the clustered Quickr environmentThis section explains how to add a LDAP repository to the Quickr 8.5 cluster. The end result is two repositories in a federated LDAP configuration, the original defaultWIMFileBasedRealm and a LDAP Repository, with the admin user and group residing on LDAP. Other configuration options can be found in the documentation topic, “LDAP user registry.”

It is critical to ensure that there is no duplicated name of Portal Administrator users or groups in the LDAP you provide. If you decide to keep the file-based repository, it must not contain the same user name that is in LDAP.

If the same shortname for a user exists in both the LDAP and the file-based repository, you will not be able to log in to the Quickr environment because security is not able to distinguish the user or group.

Configuring an LDAP repository for Lotus Quickr in a clustered environment uses the same commands and helper files as the configuration for a single server. However, for some tasks, certain steps must be performed on the primary node machine and then propagated throughout the cluster, while other tasks must be performed on secondary node machines.

To add an LDAP repository:

1. Ensure that the Deployment Manager and nodeagents are started.

2. Use a text editor to open the wp_add_federated_xxx.properties helper file, located on the primary node in the quickr_root/wp_profiles/ConfigEngine/config/helpers directory.

3. Modify the wp_add_federated_xxx.properties file, entering values for the following parameters:

a) Set the VMM federated LDAP properties as follows:

federated.ldap.id = federatedLDAP(any name to identify the federated configuration within WebSphere Security)federated.ldap.host = dpi-ldap.rtp.raleigh.ibm.com

54

( ldap server hostname)federated.ldap.port= 389( ldap server port)federated.ldap.bindDN = uid=wpsbind,cn=users,dc=Raleigh,dc=ibm,dc=com(username in LDAP that has read privileges and is able perform LDAP search)federated.ldap.bindPassword = wpsbind(LDAP user password)federated.ldap.ldapServerType = IDS6(LDAP type)federated.ldap.baseDN = dc=Raleigh,dc=ibm,dc=com(base DN in ldap tree structure)

b) Set the LDAP entity types:

federated.ldap.et.group.objectClasses= groupOfUniqueNames(object class for group in ldap)federated.ldap.et.group.objectClassesForCreate = (The object class to use when an entity type is created. If the value of this parameter is the same as the objectClass parameter, you do not need to specify this parameter.)federated.ldap.et.group.searchBases = (search base used as starting point when searching for group entities, default is blank)federated.ldap.et.group.searchFilter = (The search filter that you want to use to search the entity type, default is blank)federated.ldap.et.personaccount.objectClasses= inetOrgPerson (Object class for users for the entity type in LDAP)federated.ldap.et.personaccount.objectClassesForCreate = (The object class to use when an entity type is created. If the value of this parameter is the same as the objectClass parameter, you do not need to specify this parameter.)federated.ldap.et.personaccount.searchBases =( The search base or bases to use while searching the entity type.)federated.ldap.et.personaccount.searchFilter = (The search filter that you want to use to search the entity type, default is blank)

c) Set the Group member attributes:

federated.ldap.gm.groupMemberName = uniqueMember(The name of the LDAP attribute that is used as the group member attribute)federated.ldap.gm.objectClass = groupOfUniqueNames(The group object class that contains the member attribute)federated.ldap.gm.scope= direct

55

(The scope of the member attribute)federated.ldap.gm.dummyMember = uid=dummy(If you create a group without specifying a member, a dummy member will be filled in to avoid creating an exception about missing a mandatory attribute.)

d) Set the following attributes exactly as specified:

federated.ldap.adapterClassName=com.ibm.ws.wim.adapter.ldap.LdapAdapter(The implementation class name for the repository adapter)federated.ldap.certificateMapMode=EXACT_DN(Specifies whether to map X.509 certificates into a LDAP directory by exact distinguished name or certificate filter)federated.ldap.authentication=simple(Indicates the authentication method to use)federated.ldap.derefAliases=always(Controls how aliases are de-referenced. The default value is always)federated.ldap.referral=ignore(The LDAP referral)

4. On the primary node machine, validate the configuration (see figure 62):

<quickr_root>/wp_profile/ConfigEngine/ConfigEngine.bat validate-federated-ldap –DparentProperties=<location of wp_add_federated_ids.properties> -DSaveParentProperties=false –Dfederated.ldap.bindPassword=<bind user password> -DWasUserid=<user used during install> -DWasPassword=<install user password>

Figure 62. Validate the configuration

56

5. Ensure that you receive the BUILD SUCCESSFUL message before continuing (figure 63).

Figure 63. Build successful message

6. Add the LDAP repository (see figure 64):

<quickr_root>/wp_profile/ConfigEngine/ConfigEngine.bat wp-create-ldap -DparentProperties="./config/helpers/wp_add_federated_ids.properties" -DSaveParentProperties=false –Dfederated.ldap.bindPassword=<bind id password) -DWasUserid=<User used to install quickr> -DWasPassword=<password of user used to install quickr>

Figure 64. Add LDAP repository

57

7. Ensure that you get the BUILD SUCCESSFUL message (see figure 65).

Figure 65. Build successful message

8. Run the following tasks to propagate the security changes in the clustered environment:

From the <dmgr_profile_root>\\bin directory: stopManager.bat -username <admin_userid> -password <admin_password> From the <wp_profile_root>\\bin directory: stopNode.bat -username <admin_userid> -password <admin_password> From the <wp_profile_root>\\bin directory: stopServer.bat WebSphere_Portal -username <admin_userid> -password <admin_password> From the <dmgr_profile_root>\\bin directory: startManager.bat From the <wp_profile_root>\\bin directory: startNode.bat From the <wp_profile_root>\\bin directory: startServer.bat WebSphere_Portal

9. On the primary node machine, modify the <parent_file_dir>/parent.properties file to contain the new WebSphere Application Server administrator user ID. The new user must be a unique user in the Federated Repository:

# Required# newAdminId: The full form of user ID for the WebSphere Application Server Administrator in the LDAP server.newAdminId=uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com

58

10. On the primary node machine, replace the password variables in the following command, run it (figure 66), and make sure to get the BUILD SUCCESSFUL message (figure 67):

<wp_profile_root>/ConfigEngine/ConfigEngine.bat wp-change-was-admin-user -DparentProperties="<parent_file_dir>/parent.properties" -DSaveParentProperties=false -DnewAdminPw=<ReplaceWithNewPwd> -DWasUserid=<ReplaceWithYourWasUserid> -DWasPassword=<ReplaceWithYourPwd> 2>&1 > "<log_path>/ChangeWASAdm.log"

Figure 66. Replace password variables

Figure 67. Build successful message

59

11. On the primary node, modify the <parent_file_dir>/parent.properties file to contain the new WebSphere Portal administrator user ID and group. The new user ID and group must be unique in the Federated Repository:

# Required# newAdminGroupId: The full form of group ID for the WebSphere Portal Administrator in ldap server.newAdminGroupId=# Required# newAdminId: The full form of user ID for the WebSphere Portal Administrator in ldap server.newAdminId=uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com

12. On the primary node machine, replace the password variables in the following command, run it (figure 68), and make sure to get the BUILD SUCCESSFUL message (figure 69):

<wp_profile_root>/ConfigEngine/ConfigEngine.bat wp-change-portal-admin-user -DparentProperties="<parent_file_dir>/parent.properties" -DSaveParentProperties=false -DnewAdminPw=<ReplaceWithNewPwd> -DWasUserid=<ReplaceWithYourWasUserid> -DWasPassword=<ReplaceWithYourPwd> -Dskip.ldap.validation=true 2>&1 > "<log_path>/ChangePortalAdm.log"

Figure 68. Replace password variables

60

Figure 69. Build successful message

13. To propagate the security changes in the clustered environment, the environment needs to be restarted, as in step 8.

14. Run the following task to apply security fixes (figure 70), making sure to get the BUILD SUCCESSFUL message (figure 71) and to use the RDN instead of DN as UserId and GroupId):

<wp_profile_root>/ConfigEngine/ConfigEngine.bat action-security-ifixes-for-qkr -DPortalAdminId="<ReplaceWithYourNEWPortalAdminId>" -DPortalAdminPwd=<ReplaceWithYourPortalAdminPwd> -DPortalAdminGroupId="<ReplaceWithYourNEWPortalAdminGroupId>" -DWasUserid="<ReplaceWithYourNEWWasUserid>" -DwasPassword=<ReplaceWithYourPwd>

Figure 70. Apply security fixes

61

Figure 71. Build successful message

15. To propagate the security changes in a clustered environment, the environment needs to be restarted as in step 8.

16. On the primary node machine, modify the <parent_file_dir>/parent.properties file to contain the content group information:

# PortalAdminIdShort: The short form of the user ID for the WebSphere Portal Administrator in ldap server.# See LDAP examples below:# IBM Directory Server: { uid=<wasuserid>,cn=users,dc=yourco,dc=com } short form: wasuserid> PortalAdminIdShort=# PortalAdminPwd: The password for the WebSphere Portal Administrator. PortalAdminPwd=###################################################################### Properties required for importing and exporting of migration data###################################################################### Required# Using the full group name in ldap server WpsContentAdministrators=uid=WpsContentAdministrators,cn=users,dc=raleigh,dc=ibm,dc=com

17. On the primary node machine, replace the password variables in the following command, run it (figure 72) and make sure you get the BUILD SUCCESSFUL message (figure 73):

62

<wp_profile_root>/ConfigEngine/ConfigEngine.bat action-configure-content-groups-for-pdm -DparentProperties="<parent_file_dir>/parent.properties" -DSaveParentProperties=false -DWasUserid=<ReplaceWithYourWasUserid> -DWasPassword=<ReplaceWithYourPwd> -Dskip.ldap.validation=true 2>&1 > "<log_path>/ChangeContent.log"

Figure 72. Replace password variables

Figure 73. Build sucessful message

18. On the primary node machine, replace the password variables in the following command (figure 74), run it, and make sure to get the BUILD SUCCESFUL message (figure 75):

<wp_profile_root>/ConfigEngine/ConfigEngine.bat wp-update-federated-ldap-attribute-config -Dfederated.ldap.attributes.mapping.ldapname="mail,title" -Dfederated.ldap.attributes.mapping.portalName="ibm-primaryEmail,ibm-jobTitle" -Dfederated.ldap.attributes.mapping.entityTypes="PersonAccount,Group" -

63

DWasUserid=<ReplaceWithYourWasUserid> -DWasPassword=<ReplaceWithYourPwd> 2>&1 > "<log_path>/log12.log"

Figure 74. Replace password variables

Figure 75. Build successful

19. To propagate the security changes in a clustered environment, the environment needs to be restarted as in step 8.

20. On each secondary node, replace the password variables in the following command (figure 76), run it, and make sure to get the BUILD SUCESSFUL message (figure 77):

<wp_profile_root>/ConfigEngine/ConfigEngine.bat enable-jcr-security - DWasUserid=<New_WASAdm_shortname> -DwasPassword=password

64

Figure 76. Replace password variables

Figure 77. Build successful

21. To propagate the security changes in a clustered environment, the environment needs to be restarted as in step 8.

22. Finally, restart the environment, access each node via WebSphere transport, and test logging in to ensure all administration links work (Place Catalog Administrator, Advanced Administration, and Place Administration).

If you do not see these links, check the application security roles (QuickrNextAdmin and PlaceCntrApp) and ensure that the security-role-to-user/group mapping is correct (pointing to the portal admin group), as shown in figure 78.

65

Figure 78. Security role to user/group mapping

7 Configuring IBM HTTP Web Server for a clustered environmentSet up your IBM HTTP Server (hereafter called “Web Server”) to communicate with Lotus Quickr by installing and configuring the Web server plug-in provided with WebSphere Application Server. By default WebSphere Portal uses the internal HTTP transport within WebSphere Application Server to handle requests.

This paper focuses on installing and configuring a remote Web Server on a different machine. The Web server plug-in determines whether a request is handled by the Web Server or by WebSphere Application Server, and is installed on the same machine as the Web Server.

Ensure that the Web Server is installed and configured. Refer to the Web Server documentation for more information.

7.1 Install Web ServerTo do this, follow these steps:

1. Execute the install.exe file to start the install process. The Welcome screen displays; click Next (see figure 79).

66

Figure 79. Web Server Welcome screen

2. Choose “I accept both the IBM and non-IBM terms” and click Next (see figure 80).

Figure 80. License Agreement window

3. Enter the install location of the Web Server and click Next (see figure 81).

67

Figure 81. Enter install location

4. Enter HTTP Port and Administration Port and click Next (see figure 82).

Figure 82. Port Values Assignment window

5. Select to run IBM HTTP Server and Administration as a Windows service, provide the Administrator ID and password, and click Next (see figure 83).

68

Figure 83. Windows Service Definition window

6. Set the HTTP Administration Server ID to use for administration and click Next (see figure 84).

Figure 84. HTTP Administration Server Authentication window

69

7. The Installation summary window displays; click Next to complete the installation (see figure 85).

Figure 85. Installation summary window

8. The Success window displays; click Finish (see figure 86).

Figure 86. Success window

70

7.2 Install the plug-in for WebSphere Application Server1. Start the installation by launching the install.exe. The Welcome screen displays; select if you

want to see the Installation roadmap, and click Next (see figure 87).

Figure 87. Welcome screen

2. In the Software License Agreement window, select “I accept both the IBM and the non-IBM terms” and click Next.

3. Select the Web server to configure, in this case, IBM HTTP Server; click Next (see figure 88).

71

Figure 88. Select the Web server to configure window

4. Select the option for “Web server machine (remote)” and click Next (see figure 89).

Figure 89. Select the installation scenario window

5. Enter the installation path of the WebSphere Application Server plug-in and click Next (see figure 90).

72

Figure 90. Installation directory window

6. Enter the path of HTTP Server configuration file and Port used; click Next (see figure 91).

Figure 91. Select the Web server configuration file

7. Enter name of the Web server definition and click Next (see figure 92).

73

Figure 92. Specify Web server definition name

8. Enter location where you want the plug-in to be generated; click Next (see figure 93).

Figure 93. Location of Web server plug-in

9. Enter the host name of the Application Server and click Next (see figure 94).

74

Figure 94. Application Server name

10. Click Next to complete the installation; the Summary window displays (see figure 95).

Figure 95. Install complete

As stated in the above figure, once complete, you must follow the directions in the WebSphere plug-in roadmap:

75

1. Copy the configureWeb_Server_name script from the machine on which the plug-in was installed and paste it onto the Deployment Manager machine in the was_install_root/bin directory.

2. On the DM machine, run the script to configure the Web server definition for a cluster.

3. Because the configureweb_server_name script not only creates the Web server definitions but also changes the target mappings of all enterprise applications deployed in the cell, you must synchronize and restart the cluster when running the script on a DM system.

7.3 Configure Lotus Quickr to use the Web ServerFinally, we need to configure Lotus Quickr to use the Web Server:

1. Log in to the DM and navigate to Resources – Resource Environment Providers – WP_ConfigService – Custom properties.

2. Select host.name and enter the Web Server name (see figure 96).

Figure 96. Web Server name

76

For the IBM HTTP Server:

1. Edit the httpd.conf file on the Web Server machine and ensure that the AllowEncodedSlashes directive is set to “On”. You must explicitly set AllowEncodedSlashes to “On” in every <VirtualHost> container. See the Apache Server documentation for more information about the AllowEncodedSlashes directives .

2. After the Web Server is successfully installed and running, stop the Web Server.

3. Ensure that the following required substitution variables are set in the configuration for WebSphere Application Server:

a) Log in to the administrative console for WebSphere Application Server. If you are using the Web Server in a clustered environment, open the administrative console for the DM machine.

b) Select Environment – WebSphere Variables, and update the value of the WCM_HOST variable with the fully qualified host name of the Web Server.

c) Update the value of the WCM_PORT variable with the port number used to access the Web Server.

d) Update the Quickr_Base_URL, restart the Lotus Quickr server, and verify that Lotus Quickr is operational with the new Web Server configuration.

8 TroubleshootingLet's discuss some of the common issues that can be encountered during the installation.

8.1 Error in wpinstalllog.txtIf the user defined in the install is not set in the Administration Console as part of the Administrator Role, you will see the following error in the wpinstalllog.txt:

Oct 12, 2010 7:30:16 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: [10/12/10 19:30:16.979 EDT] ssl.disable.url.hostname.verification.CWPKI0027I(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: com.ibm.websphere.management.exception.ConfigServiceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.

77

(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:473)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wkplc.was.registry.AdminConfigRegistry.getExistingRegistry(AdminConfigRegistry.java:104)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wkplc.models.compregistry.ResourceWidget.loadRegistryFromWAS(ResourceWidget.java:200)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wkplc.models.compregistry.GenerateNodeRegistryXML.cacheWASRegistry(GenerateNodeRegistryXML.java:243)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wkplc.models.compregistry.RegistryHelper.getWasRegistry(RegistryHelper.java:132)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wps.config.ConfigEngine.loadRegistry(ConfigEngine.java:1250)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:707)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:247)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at java.lang.reflect.Method.invoke(Method.java:618)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)

78

(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at java.lang.reflect.Method.invoke(Method.java:618)Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wps.config.launch.ConfigEngineLauncher.process(ConfigEngineLauncher.java:273)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.wps.config.launch.ConfigEngineLauncher.main(ConfigEngineLauncher.java:315)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:824)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:792)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:582)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:409)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at $Proxy0.invoke(Unknown Source)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:205)

79

(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:448)(Oct 12, 2010 7:30:18 PM), Quickr.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: ... 18 more

8.2 Administration links not available or do not workAnother issue that has been seen after enabling security on the clustered environment is the Quickr Administrative links either do not display with administrators or do not work when selected. This can occur for several reasons:

First, check the Quickr applications to ensure the security mappings are correct. They must point either directly to the Quickr Administrator or to the Administrative group found in LDAP that was configured in the security steps:

1. Navigate to Enterprise Application in the DM console (http://dm-server:port/admin), and review the PlaceCntrApp (figure 97) and QuickrNextAdmin (figure 98) applications.

2. Select “Security role to user / group mapping” and ensure that the Administrator group is defined in the Administrator role. You can also manually add your Quickr Administrator to the mapped users.

3. Also, ensure that the creator and member all authenticated tabs are checked. This controls who is able to create places.

Figure 97. PlaceCntrApp Security role to user/group mapping

80

Figure 98. QuickrNextAdmin Security role to user/group mapping

8.3 Bus securityAnother issue is that, after a Federated LDAP has been configured, the Bus user defined is still pointing to the previous admin (used during installation). If you see an error like the following:

Caused by: com.ibm.wsspi.sib.core.exception.SIAuthenticationException: CWSIP0301E: Unable to authenticate user quickradm when creating a connection to secure messaging engine GSJ2EEAPP1.WebSphere_Portal-SearchBus on bus SearchBus. at com.ibm.ws.sib.processor.impl.MessageProcessor.createConnection(MessageProcessor.java:767) at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection.createConnection(SibRaMessagingEngineConnection.java:979) at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection.<init>(SibRaMessagingEngineConnection.java:261)

then log in to the DM via http://dm-server:9060/admin and navigate to Security – Secure Administration, applications, and infrastructure – JAAS - J2C authentication data. Confirm that the SearchBusServerAlias is pointing to the new Quickr administrator set in the security steps (see figure 99).

81

Figure 99. SearchBusServerAlias

8.4 Error in Place Center and no places displayedAfter logging in to Lotus Quickr, if you receive an error in the Place Center that it is not able to find places and no places displayed, you can correct this by rebuilding the Place Catalog:

1. Log in to Lotus Quickr and navigate to Place Catalog Administration.

2. For the DefaultPlaceCrawlerLocal, select “More”, and then clear the data by selecting “more actions” (see figure 100).

Figure 100. Place Catalog Administration window

3. Once complete, select “More actions” and select collect data. This will restart the crawler and find the existing places.

4. Use the same steps for DefaultTemplaceCrawlerLocal (see figure 101).

82

Figure 101. More actions drop-down menu

8.5 Problem collecting dataIf there is a problem collecting data, such as indicated by a “403 Authentication Failed” error, then check the following:

1. Select Edit Details in the Place Catalog Administration window. Ensure that the ID used is the new Quickr Administrator. If it's still failing, check the PlaceTemplateSeedListServletApp application's security mappings, ensuring that the Administrator user or group is specified for SeedlistUser (see figure 102).

Figure 102. SeedlistUser

2. Also, ensure that the new Quickr Administrator user and group is part of the Administrator role in WebSphere. Log in to the DM and select User and Groups – Administrative Group Roles, and add the new Quickr Administrator group, if not already there (see figure 103).

83

Figure 103. Administrative Group Roles

8.6 Places not displayed on second nodeIf Place Center is not displaying any places when accessing the secondary node, the problem is likely due to insufficient privileges on the shared folder in which the index of places and templates are stored. During installation, the SharedResources network share is configured and created. The crawler updates the index on network share but only runs on the primary node.

To correct the issue:

1. Find the location of the share by using the DM and navigating to Resource Environment Providers – PlaceCntrPropertiesService – Custom properties.

2. In the defaultCollectionsFolder, review the permissions set on the network share, ensuring the second node can access the SharedResources.

9 ConclusionNow that you have walked through the entire process of setting up a Quickr 8.5 cluster, including remote database, security, and remote Web server, you should have a working, horizontal clustered Quickr 8.5 environment that's ready for test or production.

10 ResourcesdeveloperWorks Lotus Quickr for WebSphere Portal product page:http://www-01.ibm.com/software/lotus/products/quickr/portal/

developerWorks Lotus Quickr product documentation:https://www.ibm.com/developerworks/lotus/documentation/quickr/

Participate in the Lotus Quickr forum:http://www-10.lotus.com/ldd/quickplace.nsf?OpenDatabase

84

Quickr wiki article, “Troubleshooting clustering in IBM Lotus Quickr 8.5 for WebSphere Portal”: http://www-10.lotus.com/ldd/lqwiki.nsf/dx/Troubleshooting_clustering_in_IBM_Lotus_Quickr_8.5_for_WebSphere_Portal

11 About the authorJeff Johnson is a member of the Lotus Quickr for WebSphere Portal team based at IBM's Research Triangle Park, NC, facility. He specializes in the combination of the Lotus Quickr, Lotus Web Content Management, and WebSphere Portal products, before which he was a member of the Proactive Customer Enablement team, working exclusively on critical issues that included travel to customer locations for hands-on assistance. You can reach Jeff at jeffjohn@us.ibm.com.

Trademarks• DB2, developerWorks, IBM, Lotus, Quickr, Tivoli, and WebSphere are trademarks or

registered trademarks of IBM Corporation in the United States, other countries, or both.

• Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• Other company, product, and service names may be trademarks or service marks of others.

85