Test Infrastructure: WebSphere Portal basic capacity planning test on AIX

Abstract
The purpose of this document is to describe the configuration and to outline the steps by which the WebSphere Portal System Verification Test (SVT) team installed, configured, and tested the reliability of WebSphere Portal using a Basic Capacity Planning stress testing.

Environment overview

The AIX stress test environment included the following components: WebSphere Portal 6.0.1 WebSphere Application Server Deployment Manager 6.0.2.17 on the portal system DB2 9.1 database for the data IBM HTTP Server Web Server 6.0.2.0 IBM Tivoli Directory LDAP server for authentication

The basic capacity planning scenario is the main benchmark scenario where mostlyauthenticated large set of users access the portal. The users are assumed to be in 50 groups in the LDAP server, and each group has access to a small number of pages with custom JSR 168 portlets. The scenario also includes some small set of unauthenticated users accessing the portal. Parallel Portlet Rendering was enabled for the portlets and pages.

Specifications
Machine OS # of CPUs 4 4 4 CPU Speed CPU Type PowerPC_Power 4 PowerPC_Power 4 PowerPC_Power 4 RAM (MB) 8192 8192 8192 4096 Function WebSphere Portal Web Server Database LDAP

Portal 6.0.1, WAS 6.0.2.17 ND IBM HTTP Server 6.0.2.0 DB2 9.1 ITDS on iSeries

AIX 5.3 AIX 5.3 AIX 5.3 iSeries V5R4

1453MHz 375 MHz 1453MHz Clock speed: 2700

The following pictures show the environment used for this test:
IBM HTTP Server WebServer 6.0.2.0

CPU 4 CPU, 375 MHz HTTP Memory 8192 MB

users
HTTP
4 CPU, 1453 MHz 8192MB

WP 6.0.1 WAS 6.0.2.17

CPU Memory

CPU Memory

Clock Speed batch 2700 4096 MB

CPU 4 CPU,1453MHz Memory 8192 MB

IBM Tivoli Directory Server on iSeries

DB2 9.1

Installation and Configuration The environment was installed and tested using the following steps: 1. 2. Install WebSphere Portal 6.0.1. Installing WebSphere Portal 6.0.1 Tune WebSphere Portal Server Version 6.0 tuning guide v.1.2 according to the performance tuning guide.

3.

Configure Portal to an external DB2 database Server Installing and configuring Portal with DB2

4.

Configure Security to ITDS LDAP user registry Installing and configuring to IBM Tivoli Directory Server Configure to an external IBM HTTP Server Web server Installing and configuring to IBM HTTP Server Web Server Install custom JSR 168 portlets using xmlaccess tool. Create custom pages using xmlaccess tool. Enable Parallel Portlet Rendering (PPR) for the pages and portlets The environment was load and stress tested for reliability using loadrunner automation scripts. Tasks involved were as follows:

5. 6. 7. 8. 9.

425 concurrent users access the portal page through the Web server URL Large set of users log in to WebSphere Portal, navigate to different pages, and work with the custom JSR 168 portlets Small set of users do not log in to portal but only browse the welcome page

The results were as follows: The CPU on the portal system was driven to 85-90%

The response times for all the transactions were measured to be under 1 second The longrun ran for 120 hours before the test was ended