Test Infrastructure: WebSphere® Portal
Express 6.1 Out-Of-Box test
Abstract
The purpose of this document is to outline the steps by which the WebSphere
Portal System Verification Test (SVT) team installed, configured, and tested
the business-to-customer (B2C) and business-to-employees (B2E) site shipped
with WebSphere Portal Express 6.1.
Environment overview
The environment included the following items:
Microsoft® Windows® 2003 Server SP2:
- WebSphere Portal Express 6.1 and WebSphere
Application Server 6.1.0.15
- DB2® 9.1 fix pack 4
iSeries™ V6R1:
- WebSphere Portal Express 6.1 and WebSphere
Application Server 6.1.0.15
- DB2 9.1 fix pack 4
The following picture shows the how the environment was configured:
Machine specifications
The following tables detail the machines used in this setup:
Windows 2003 Server SP2:
|
Machine
|
OS
|
# of CPUs
|
CPU Speed
|
CPU Type
|
RAM (GB)
|
Function
|
|
Portal Express 6.1
|
Windows 2003 server SP2
|
1
|
3.2 GHz
|
Intel
|
2
|
standalone node
|
|
Database DB2 9.1
FP4
|
Windows 2003 server SP2
|
1
|
3.2 GHz
|
Intel
|
2
|
database |
iSeries V6R1:
|
Machine
|
OS
|
# of CPUs
|
Processor CPW
|
CPU Type
|
RAM (GB)
|
Function
|
|
Portal Express 6.1
|
iSeries V6R1
|
4
|
6600
|
POWER4
|
12
|
standalone node
|
|
Database DB2 9.1
FP4
|
iSeries V6R1
|
4
|
6600
|
POWER4
|
12
|
database |
Installation and configuration
Refer to the topics from the
WebSphere
Portal 6.1 Information Center
listed in the steps below for more detailed instructions about the steps
to install and configure the environment used for this test.
The environment was installed with the following steps:
1. Install WebSphere Portal Express 6.1, using
the topic
Installing WebSphere Portal
2. Tune the WebSphere Portal server
Portal server’s Maximum Heap Size：
Windows: 1024M
i5/OS: 6000M
WPS database’s datasource’s Connection Pool ->
Maximum connections: 100
WPS database’s datasource’s Connection Pool ->
TimeOut: 600 seconds
WPS database’s datasource’s Connection Pool ->
Statement cache size: 100
Web container Thread Pool -> Maximum Size: 100
Session Timeout: 30 minutes
3. Perform a 24-hour reliability run for Web
Content Management (WCM) rendering longrun against B2E/B2C site
4. Perform a 24-hour reliability run for WCM
Authoring longrun against B2E/B2C site
5. Perform a 120-hour combination (authoring
& rendering) reliability run
Test user configuration
This environment was load and tested using Rational® Performance Tester
to simulate up to 50 concurrent users (10 viewers and 40 editors) accessing
the business-to-customer (B2C) and business-to-employees (B2E) site, then
viewing or editing portlets randomly for 120 continuous hours.
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.