ShowTable of Contents
The goal of this document is to outline the steps by which the Web Content Management System Verification Test (SVT) team installed, configured, and tested Web Content Management. Authoring, Rendering , boundary test for 50k items and Syndication were tested in Portal 6.1.5 in this scenario.
Content introduction
The environment included a rendering cluster, an authoring cluster with a staging node in between. Content was moved between the different environments with automatic syndication. The software versions used in this test environment are as follows:
· WebSphere Application Server 6.1.0.27
· WebSphere Portal 6.1.0.3
· Lotus Web Content Management 6.1.5
· DB2 9.7.0.1
· Oracle 11.1.0.6.0
· IBM HTTP Server 7.0.0.0
· IBM Directory Server 6.1
Deployment topology
The following test environment was configured to test the scenario.
Server hardware and software configurations
The following table provides additional information about each server in the topology.
Configuration settings
WebSphere Portal 6.1.5 InfoCenter Main URL:
http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html
Please refer to the topics listed in the steps below for more detailed instructions on the steps to install and configure the environment used for this test.
The environment was installed with the following steps:
1. Install DB2 Server, using the topic “Planning for DB2 on UNIX or Linux”
a. Create databases and domains.
2. Install WebSphere Portal Network Deployment Manager, using the topic “Preparing the WebSphere Application Server Network Deployment on AIX”
3. Install the Web server, using the topic “Preparing a remote Web server on AIX/Linux/Solaris”
4. Install and Setup the primary node, using the topic “Preparing the primary node on AIX/Linux/Solaris”
a. Install WebSphere Portal
b. Configure/Transfer the remote database(s)
c. Setup Cluster
d. Configure primary node to communicate with the network deployment manager
e. Configure primary node to display WCM data through Web Server
f. Configure cluster to use external Web Server
5. Add an additional node to the cluster, using the topic “Preparing additional nodes on AIX/Linux/Solaris”
a. Install WebSphere Portal
b. Add the node to the cluster.
6. Configure Content Server, using the topic “Setting up a content server”
7. Create WCM Libraries/Content for Virtual Portals, using topic “Creating Web content”
a. create the content
b. specify the user level permission for the content
8. Create PZN Rules, using topic “Personalizing your content”
9. Tune All Servers for Portal and WCM related settings.
10. Restart environment and verify all settings
Test user configuration
The following tests were conducted using HAT-J, which is a similar open source tool to LoadRunner, to simulate the multiple users performing their various tasks over specific periods of time.
Authoring
The authoring use case created contents in a single library, which has three authoring templates, one site, three site areas and one 5 stage workflow (Draft, Approval, Published, Expired and Reject).
Two types of tests have been were completed, a reliability test and a stress test. The reliability test was for 70 Virtual Users with 20-60 second think time. The stress test was for 30 Virtual Users with 0 – 20 second think time. Three distinct runs were attempted, one with a basic workflow (draft -> approve ) , one with a more complex workflow ( draft -> approve -> published -> expired ) and one with a more complex workflow which has custom actions. All runs were executed for 12 hours for both reliability test and stress test. The complex run was executed for 72 hours for reliability test.
NOTE: Every customer is different. Our results were obtained in a controlled test environment. Customer environments are usually less optimal and may not get the same results. Understanding your environment (usage scenario, network, etc...) is crucial before recommending scaling numbers, hardware and solutions