This document outlines the experiences of the IBM System Verification Test (SVT) team specifically in relation to reliability when upgrading, configuring and testing an existing Lotus Quickr 8.1 deployment to the 8.1.1 service release level in a Microsoft Windows 2003 environment using a clustered Lotus Quickr configuration with a Deployment Manager and two physical nodes. The system had a remote database back-end and remote HTTP server with the deployment enabled against an external LDAP source. This document also outlines how to configure the 8.1.1 Quickr system for use with an IBM FileNet P8 system.
Overview
As a part of our test requirements, we focused on the following specifics:
- A single Deployment Manager (DM)
- Two separate Lotus Quickr 8.1.0 nodes
- IBM Tivoli Directory Server 5.2 server
- Separate DB2 server. Before installing this release, you must upgrade to DB2 FP5
- Remote IHS web server. The version we used was IBM_HTTP_Server/6.0.2.29
- IBM FileNet P8 system comprising of two components, a content engine machine and an application engine
The goal of our testing was to run System Integration Verification Testing and load testing of Lotus Quickr components under load for 120 hours (5 days) with 500 concurrent users.
Assumptions:
- We already have a Quickr deployment at the required level, Quickr 8.1. If you have IBM Lotus Quickr services for WebSphere Portal 8.0 or 8.0.0.2, then you must first upgrade to IBM Lotus Quickr services for WebSphere Portal 8.1 before upgrading to 8.1.1.
- The existing deployment has a remote DB2 server and remote HTTP server already configured.
- The existing 8.1 deployment has been enabled against an external LDAP, IBM Tivoli Directory Server 5.2.
- The current 8.1 Quickr deployment should have all applicable patches and tuning applied.
- After upgrading to version 8.1.1, it is advisable to check the tuning applied at the 8.1 level.
Infrastructure Diagram
The infrastructure configuration we used is illustrated below in this diagram:
Specifications
The following table lists the specifications for the computers used in the infrastructure.
| Machine | OS | Software | Spec |
| Deployment Manager | Windows 2003 | WAS Network Deployment (ND) 6.0.2.17 | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
| Quickr server - 2 nodes | Windows 2003 | Quickr 8.1 / WAS 6.0.2.17 / WPS 6.0.1.1 / JRE 1.4.2 SR11 | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
| DB2 server | Windows 2003 | IBM DB2 Universal Database Enterprise Server Edition 9.1 FP5 - DB2 JDBC Universal Driver (Type 4) | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
| LDAP server | Windows 2003 | IBM Tivoli Directory Server 5.2 server |
|
| Web server | Windows 2003 | IBM HTTP Server 6.0.2.29 / 2.0.47.1 | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
| Content Engine | Windows 2003 | DB2 client 9.1 / WAS 6.1.0.19 / FileNet Enterprise Manager / IBM FileNet Services for Lotus Quickr Version 1.0 | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
| Application Engine | Windows 2003 | WAS 6.1.0.19 / DB2 Universal Database Enterprise Server Edition 9.1 FP4a | 2 Dual-Core CPUs @ 2.33 GHz - 4 GB RAM |
Recommended reading for installation and configuration of a Lotus Quickr 8.1.1 clustered system:
The following references are recommended when installing and configuring Lotus Quickr 8.1.1:
IBM Lotus Quickr Version 8.1.1 Information Center
The hardware and software requirements for Lotus Quickr 8.1.1
8.1.1: Readme for upgrading IBM Quickr 8.1 services for IBM WebSphere Portal -- Clustered Configuration
Required post-installation fixes for Lotus Quickr 8.1.1 services for WebSphere Portal
Installation and configuration of a P8 system for use with Quickr:
Refer to the relevant
product documentation for FileNet P8 Platform for information on setting up the P8 system.
Refer to the relevant product documentation
"FileNet Services for Lotus Quickr" for information on installing the IBM FileNet Services for Lotus Quickr services layer.
Configuring the Lotus Quick system for use with a P8 System:
Refer to the relevant
product documentation to configure the Lotus Quickr system to enable users to publish content to the P8 system.
While it is not required, it is recommended that SSO is enabled between the Quickr cluster and the P8 system, details on how to enable SSO can be found in the IBM FileNet Services for Lotus Quickr
Installation and Configuration Guide that is included with the installation files.
Sample settings are illustrated below. Note that this is a specific scenario; refer to the Information Center and the Services layer installation documentation for further documentation.
Log on to your administration console, normally this will be
https://hostname.domain:9043/ibm/console
Under
Resources -> Resource environment providers --> QuickrWhitelistProvider --> Custom properties enter a value for the domains that you wish to allow. A sample is shown in the figure below:
Log on to your administration console, normally this will be
https://hostname.domain:9043/ibm/console
Under
Resources -> Resource environment providers -> QuickrPublishConfig -> Custom properties enter the values that are applicable for your particular scenario, sample values are shown in the figure below:
Also create a vault slot as shown below with name equal to FilingSlot
You will also need to run the following task on node (it is necessary to have your deployment started before running this command):
From the
/PortalServer/config directory run the command
WPSconfig.bat action-init-contentmodel
Now restart all servers. You should now be able to publish documents to the P8 system from the Quickr System.
Hints and tips
Below are some sample properties files that were used in this infrastructure.
Sample settings from node 1 in wpconfig.properties:
P8_wpconfig_node1.properties
Sample settings from node 1 wpconfig_dbdomain.properties:
P8_wpconfig_dbdomain_node1.properties
Sample settings from node 2 wpconfig.properties:
P8_wpconfig_node2.properties
Sample settings from node 2 wpconfig_dbdomain.properties:
P8_wpconfig_dbdomain_node2.properties
Post Upgrade Tuning:
Some of these tuning steps might already be included from earlier configuration and may be unnecessary for the upgrade. Check the
Lotus Quickr information center for your particular scenario.
DB2 Tuning:
db2 connect to wpsdb user db2admin using 'mypassword'
db2 update alert cfg for database on wpsdb using db.tb_runstats_req set THRESHOLDSCHECKED NO
db2 update alert cfg for database on wpsdb using db.db_backup_req set THRESHOLDSCHECKED NO
db2 update alert cfg for database on wpsdb using db.tb_reorg_req set THRESHOLDSCHECKED NO
db2 CREATE INDEX JCR.ICMSTJCR_ALI3 ON JCR.ICMSTJCRLINKS (TVID ASC, TIID ASC) PCTFREE 10 MINPCTUSED 10
db2 "alter bufferpool ICMLSFREQBP4 size 12000"
db2 "alter bufferpool ICMLSVOLATILEBP4 size 72000"
db2 "alter bufferpool ICMLSMAINBP32 size 30000"
db2set DB2_FMP_COMM_HEAPSZ=5000
db2 "update dbm cfg using KEEPFENCED YES"
DB2_ASYNC_IO_MAXFILOP=512
DB2_USE_ALTERNATE_PAGE_CLEANING=on
DB2_INLIST_TO_NLJN=YES
DB2_EVALUNCOMMITTED=YES
db2 "update db cfg for wpsdb using MAXFILOP 512"
Disconnect from the wpsdb database and stop and restart the DB2 server.
For all FileNet P8-related tuning parameters, refer to that
product's documentation.
After the upgrade to 8.1.1 ensure that you regenerate the web server plug-in. If you encounter any issues with the newly generated plugin file, read
Error received when downloading connectors from a Lotus Quickr server that uses a remote HTTP server.
General references
Lotus Quickr: Product documentation, white papers, Redbooks, and more
WebSphere Portal and Workplace Web Content Management product documentation
IBM DB2 Database for Linux, UNIX, and Windows Information Center
Lotus Quickr product home page on ibm.com
Lotus Quickr Support page
Product Documentation for FileNet P8 Platform
NOTE: All customer environments are different. Our results were obtained in a controlled test environment. Customer environments are typically less optimal and may not provide the same results. Understanding your environment (usage scenario, network, etc...) is crucial before recommending scaling numbers, hardware and solutions.