Before installing Lotus® Quickr™ for use in a managed node or as part of a cluster, review these important guidelines and limitations.
If you plan to migrate your data from a previous version of Quickr, you must review the Planning for migration
For redundancy, failover, and simpler maintenance, Lotus Quickr may be installed in several clusters, sharing some common data through the database. This section contains the following topics:
- Before you begin
- Guidelines for implementing cluster environments
Before you begin
In WebSphere® Application Server, a cluster is composed of multiple identical copies of an application server. A cluster member is a single application server in the cluster. Lotus Quickr is installed as an enterprise application server within the WebSphere Application Server infrastructure. All of the clustering features available within the WebSphere Application Server infrastructure are also available and apply to Lotus Quickr. Thus, a Lotus Quickr cluster is simply a collection of multiple Lotus Quickr servers that are identically configured.
When planning for Lotus Quickr clusters, you must also take into account any cluster planning required for the WebSphere Application Server nodes.
If you are planning on migrating from a previous Lotus Quickr installation, you must complete the migration before clustering the system.
For further information, refer to the Planning section of the information center for the version of IBM® WebSphere Application Server Network Deployment product supported by the version of Lotus Quickr you are using.
Configure the place backups/archives storage
If you are planning to cluster your server, you should configure the place backups/archives to be stored on a shared network drive. To configure this, you need to set a custom property for the WP_AIInitService Resource Environment Provider according to the following guidelines:
- Log on to the WWebSphere Application Server Administrative Console.
- Navigate to Resources -> Resource environment providers .
- Click WP_AIInitService.
- Click Custom Properties.
- Click New .
- Set the name to backup.root
- Set the value to a valid directory, for example:networkshare/quickr85/backup.
- Click Apply and Save the change.
- Restart the WebSphere Portal Server to pick up the change.
Guidelines for implementing cluster environments
Cluster environments should be implemented according to the following guidelines:
- There are several approaches you can use to configure an external Web server in a clustered environment. The instructions provided here for installing a Lotus Quickr follow the approach recommended by WebSphere Application Server, which involves using the Plug-ins installation wizard to install the binary plug-in module after the cell has been set up. For a complete description of the recommended procedure for configuring an external Web server in a clustered environment, refer to the WebSphere Application Server information center:
The deployment manager node must be installed separately before the cells and clusters can be configured. For more information, refer to Installing WebSphere Application Server Deployment Manager on a Windows system.
WebSphere Application Server provides database session persistence and memory-to-memory replication as techniques for HTTP session failover in a clustered environment. Review the following information to determine whether you want to use one of these techniques in your cluster.
Before using the configureweb_server_name
script during Web server configuration in a managed cell, change the timeout request period for the Simple Object Access Protocol (SOAP) client on the deployment manager machine. The default, in seconds, is 180. Edit the soap.client.props
file in the was_profile_root/properties
Change the line to: com.ibm.SOAP.requestTimeout=6000
Note: Ensure that WebSphere Application Server plugin Version 188.8.131.52 or later is installed if you are using an IBM HTTP Server as the Web server.
If you add a node to a cell or change a node's configuration after it has been federated to the deployment manager, synchronize the node's configuration. In the administrative console for the deployment manager, select System Administration -> Nodes, select the node from the list, and click Full Resynchronize. This helps ensure that there is no mismatch between node and cell configuration after the synchronization is complete.
If you are planning to configure an external security manager to perform authentication or authorization for Lotus Quickr in a cluster environment, install and configure the Lotus Quickr cluster first. Verify that the Lotus Quickr cluster is working properly before proceeding with the configuration of any external security managers.
As the first step in configuring search, create a shared directory called jcr/search on a server in the network and make sure that each node in the cluster has network access to the directory. Then see the topic Configuring search for Lotus Quickr content in clusters.
The following limitations apply when implementing a Lotus Quickr cluster:
- You must install and configure Lotus Quickr separately on each node. In addition, there can only be one Lotus Quickr cluster per cell.
- Except for the temporary state during the initial setup of the cluster, Lotus Quickr is not supported when running on a managed node that is not part of a clustered environment.
Note: A cluster may be created which contains only one portal server, enabling a single Lotus Quickr server to be operational in a managed cell.
- Windows: Long path names can be a potential problem due to the depth of the WebSphere Application Server Network Deployment directory structure, particularly when deploying applications in a cluster. To avoid problems related to excessively long paths names, consider the following recommendations when installing WebSphere Application Server Network Deployment:
In a clustered environment, it is not possible to change portal settings through the Global Settings portlet or the XML configuration interface. These changes must be made by modifying the respective properties in the WebSphere Application Server administrative console.
To support search in a clustered environment, you must install and configure search for remote search service on an application server node that is not part of the cluster.
Administrative actions for Lotus Quickr are immediately visible for the user who performs them. However, another user can be assured of seeing the changes only if the user logs out of Lotus Quickr and then logs back in. This limitation applies to both cluster and non-cluster environments.
When creating a cluster or a cluster member, do not use spaces in the cluster name or the cluster member name.
For the deployment manager and each Lotus Quickr node to be in the cluster, verify that each system clock is set to within 5 minutes of the others or the addNode command will fail.
- Use a short installation path. For example, use C:\\Quickr instead of C:\\Program Files\\IBM\\Quickr.
- Specify short cell and node names – do not use names longer than 5 characters. For example, you might use scell instead of stonemillNode01cell.
- The name of the WAR files must be less than approximately 21 characters. The installation program attempts to truncate or rename long names before it deploys the WAR file into the application server; however, it cannot always circumvent the path name to exceed the limit. To correct this error, modify the file name to less than 21 characters.
- See the technote 1254579 for more information.
Parent topic: Planning considerations: qp85