ShowTable of Contents
Web Content Management zOS End to End – Authoring and Rendering WCM content in a zOS clustered environment. 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, WCM content library Export/Import, WCM Authortime Search, and Syndication were tested in this scenario. During our rendering runs we created PZN rules to pull attribute information from content residing in other repositories.
The software versions used in this test environment are as follows
• WebSphere Application Server 7.0.0.6 with ++APAR AK98313
• WebSphere Portal for zOS V6.1.5
• Lotus Web Content Management for zOS V6.1.5
• DB2 zOS 9.1 PUT0905
• IBM HTTP Server v.7 (remote)
• IBM Directory Server 6.1 (remote)
All of the operating systems, databases and application server versions used in this test scenario were 64 bit.
The environment included a rendering cluster, an authoring cluster with a stand-alone staging node in between. Content was moved between the different environments with automatic syndication. All Item syndication was performed between the Authoring and Staging Node and then Live Item only syndication between the Staging and Rendering cluster.
Configuration Diagram
Test drivers
The following tests were conducted using Hatj tool to simulate multiple users performing their various tasks over specific periods of time.
Machine details
Server Specifications
The following table lists the specifications for the computers used in the infrastructure.
Purpose | Portal Install | OS | CPU | Memory | Model |
Primary node horizontal authoring cluster
Deployment Manager with db2-sharing
z/OS DB2 V9.1PUT0905
| Full Content Server | z/OS v1.9 | 4 (shared) LPAR | 10GB | 2084-D32 |
Secondary node horizontal authoring cluster
with db2-sharing
z/OS DB2 V9.1PUT0905
| Full Content Server | z/OS v1.9 | 4 (shared) LPAR | 6GB | 2084-D32 |
Remote HTTP Server v7 | -- | Windows 2003 Server x64 | 4 x 3.0 Ghtz | 8 GB | -- |
Primary node horizontal rendering cluster
Deployment Manager with db2-sharing
z/OS DB2 V9.1PUT0905
| Full Content Server | z/OS v1.10 | | 8GB | 2084-C24 |
Secondary node horizontal rendering cluster
Deployment Manager with db2-sharing
z/OS DB2 V9.1PUT0905
| Full Content Server | z/OS v1.10 | | 8GB | 2084-C24 |
Remote HTTP Server | -- | RedHat Linux Entreprise Server v5.2 | 2 x 2.8 Ghtz | 4 GB | -- |
Standalone full content server -
Staging environment with local
z/OS DB2 V9.1PUT0905
| Full Content Server | z/OS v1.10 | | 6GB | 2084-C24 |
|
| LDAPs |
|
|
|
LDAP ITDS 6.1(64 bit)
100k User Population
| n/a | RedHat Linux 5 | 4 - (p5) 1.6 GHz | 3.7GB |
|
Configuration settings
WebSphere Portal 6.1.5 for zOS Infocenter Main URL:
http://publib.boulder.ibm.com/infocenter/wpzosdoc/v6r1/index.jsp?topic=/com.ibm.wp.zos.doc_v615/welcome_main.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 for z/OS” and the zOS DB2 Infocenter for the version being installed.
2. Install WebSphere Portal Network Deployment Manager, using the version 7.0. WebSphere Application Server documentation for zOS located at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/welcome_nd.html
3. Install the Web server, following the product documentation for the version and o/s where the product will be installed. In our scenario the Web server was installed on Windows and Linux.
4. Depending on whether you simply want to install a standalone, federate but not cluster or cluster WebSphere Portal, the install path and steps will be different. Across the 3 environments in this usecase, we have performed 2 different install paths. The usecase install paths are defined below in sections 4.1 and 4.2. All install paths are located in the topic “Installing WebSphere Portal”.
4.1 Setting up a standalone production server
Prepare the WebSphere Application Server Deployment Manager and the Web server using the topic “Preparing prerequisite and co-requisite software on z/OS” to configure the software properly.
a. Preparing the z/OS operating system
b. Installing WebSphere Portal
· Verifying your RACF security settings
· Tuning your z/OS environment
· Enlarging the WebSphere Application Server for z/OS configuration HFS
· Configuring a base portal into a base node
· Tuning your z/OS environment
· Enabling sample Web Content Management content
· Changing ports
c. Setting up databases
d. Changing driver types
e. Transferring data
f. Preparing a remote Web server when portal is installed on z/OS
g. Configuring WebSphere Portal to use a user registry
· Preparing a SecureWay Security Server
· Choosing your user registry model on z/OS
i. Configuring the default federated repository on z/OS
· Configuring a federated LDAP user registry
· Adding an LDAP user registry on z/OS
· Tune your servers
4.2 Setting up a clustered production environment on z/OS” “Creating a cluster using managed server nodes” (done on Authoring and Rendering environments clusters)
a. Preparing prerequisite and co-requisite software on z/OS
· Preparing the z/OS operating system
· Preparing a remote Web server when portal is installed on z/OS
· Installing code through SMP/E
· Verifying your RACF security settings
· Tuning your z/OS environment
· Setting up a network deployment cell
· Preparing the WebSphere Application Server Deployment Manager on z/OS
NOTE: WebSphere Application Server Deployment Manager and Nodeagent were installed using WebSphere Customization Tool 7.0.
1. DM: Create -> Management -> Deployment manager
2. NodeAgent: Create -> Managed(custom) node
b. Preparing the primary node on z/OS
· Overview of installing the primary node
· Configuring the deployment manager
· Configuring a base portal into the primary node
· Tuning your z/OS environment
· Setting up databases
· Changing driver types
· Transferring data
c. Creating the cluster
d. Configuring WebSphere Portal to use a user registry
· Preparing a SecureWay Security Server
· Choosing your user registry model on z/OS
· Configuring the default federated repository on z/OS
1. Configuring a federated LDAP user registry
a. Adding an LDAP user registry on z/OS
e. Preparing additional nodes on z/OS
· Installing code through SMP/E
· Configuring a secondary node
· Adding cluster members
i. Adding horizontal cluster members
f. Configuring the HTTP session failover
g. Tune your servers
5. Configure Content Server, using the topic “Setting up a content server”
6. Create WCM Libraries/Content, using topic “Creating Web content”.
a. Create the content
b. Specify the user level permissions for the content
7. Create PZN Rules, using topic “Personalizing your content”
8. Tune All Servers for Portal and WCM related settings. WebSphere Portal 6.1.0.1 tuning guide: wp6101_tuning_guide.pdf
9. Restart environment and verify all settings
Authoring
The authoring use case created content in multiple libraries. Long run stress/reliability tests only one library at a time.
Two types of tests have been were completed, a reliability test and a stress test. The reliability test was for 50 Virtual Users with 20-60 second think time. The stress test was for 20 Virtual Users with 1 – 20 second think time. Runs were attempted, with a complex workflow ( draft -> approve -> published -> expired ). All stress runs were executed for 6 hours. The complex run was executed for 72 hours for reliability test.
Rendering
The rendering use case involved the creation of 'Riverbend' type website. The site contained PZN rules, wcm file components, wcm personalization component, wcm content. Some PZN rules were configured to requests attribute information from content residing in other content repositories.
Rendering reliability test run with 200 Virtual Users with a 20 – 60 second think time over 72 hours.
Syndication
Syndication was performed after the authoring library was populated. A syndicator/subscriber relationship was established between the authoring cluster and staging server, and a syndicator/subscriber relationship was established between the staging server and rendering cluster (as shown in the diagram above). The automatic syndication interval was set to 300 seconds.
After this initial syndication setup, both the authoring and rendering use cases were executed on their respective clusters and it was verified that data authored on the authoring cluster was correctly syndicated to the staging and then to the rendering cluster. This scenario was run for 72 hours.
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
Export and Import
Loaded data into multiple WCM libraries and then exported the data. The data was compressed and then the data was imported into another machine.
Authortime Search
The text search engine is enabled by default. WCM data was created and then allowed to be indexed by the text engine. Data was then queried for an expected result set.