Open Mic: Quickr Portal 8.5 Clustering Best Practices. Tiffany H. Amos Jeffrey K. Johnson IBM Corporation

Transcription

1 Open Mic: Quickr Portal 8.5 Clustering Best Practices Tiffany H. Amos Jeffrey K. Johnson 2010 IBM Corporation

2 Deploying a Clustered Quickr Portal 8.5 Environment A Quickr cluster can be deployed during installation or after installation. Clustering During Initial Installation During the initial install of Quickr, there is an option to install as a cluster. The Quickr installer, will install Quickr and then run the necessary configuration task to transfer node and create cluster. Clustering a Stand Alone Node If there is a single Quickr node that needs to be moved to a clustered setup, there are configuration tasks that can be run to transfer node and create the cluster. Special Note: Whether creating a cluster at initial installation or from a standalone node, it is recommended to enable LDAP security after the cluster has been configured. 2

3 Option A: Clustering During Initial Installation Install & Configure the Deployment Manager Install Primary Node Configure the Primary Node to remote database (optional, but best practice) Install Secondary Node Configure Security on the cluster Configure Web Server (as needed) 3

4 Best Practices & Recommendations: (Clustering During Initial Install) Ensure that the Deployment Manager is started before performing the Lotus Quickr 8.5 installation or else the installation will fail. Ensure that the Deployment Manager is configured to use file based security. Move the following files to the Deployment Manager: (wkplc.comp.registry.jar, wp.wire.jar, com.ibm.ws.portletcontainer.deploytask_6.1.0.jar, metadata_wkplc.xml) Without these the addnode task will fail. 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 will fail. Ensure that the user used to install Quickr is the same as the administrator for the Deployment Manager. The user must have the administrator role. Test Quickr after each step (i.e. after installing the primary node). Stop and Start Quickr via the DM and test that you can still access and create places before transferring the DB and after before moving on to add any secondary nodes to the cluster. Step by Step Guide to Installing Quickr in a Cluster: 4

5 Best Practices & Recommendations: (Clustering During Initial Install) Special Considerations during Security Configuration Ensure that there are no duplicate names of the Portal Admin users or groups in the LDAP you provide. If you decide to keep the file-based repository, it cannot contain the same user name that is in LDAP or this will cause access issues within Quickr as the application will not be able to differentiate the users with the same name. 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 will not able to distinguish the user or group. 5

6 Option B: Clustering a Stand Alone Node Install Stand Alone Node Install Deployment Manager Update the security configuration on the Deployment Manager with the same security settings as the Lotus Quickr node Download and use the wp_cluster_cfg.xml before running any configuration task. Run configure cluster setup commands Verify cluster Proceed with installation of secondary node 6

7 Best Practices & Recommendations: (Clustering a Stand Alone Node) The Deployment Manager security matches the current security configuration of the Quickr node. (what is of value about this point. Need to expand here.) Ensure that the Deployment Manager is started before performing the Lotus Quickr 8.5 installation or else the installation will fail. Move the following files to the Deployment Manager: (wkplc.comp.registry.jar, wp.wire.jar, com.ibm.ws.portletcontainer.deploytask_6.1.0.jar, metadata_wkplc.xml) Without these the addnode task will fail. Ensure that the Quickr administrator user is part of the WebSphere Deployment Manager Administrative role. Download and use the wp_cluster_cfg.xml before running any configuration task. Step by Step Guide instructions to creating a new cluster from a single server node: 7

8 Troubleshooting the Cluster Confirm Administrative Links work: After configuring security, restart the environment and access each node to ensure that all administration links work: Place Catalog Administration, 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-touser/group mapping is correct (pointing to the portal admin group) 8

9 Troubleshooting the Cluster Error in the Place Center and no places are displayed After 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 are displayed, you can correct this by rebuilding the Place Catalog: 9

10 Question & Answer Session 10