ShowTable of Contents
The goal of this document is to outline the steps by which the WebSphere Portal 6.1.5 System Verification Test (SVT) team installed, configured, and tested the Wiki and Blog features of WebSphere Portal.
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 18.104.22.168
· WebSphere Portal 6.1.5
· DB2 22.214.171.124
· IBM HTTP Server 126.96.36.199
· IBM Directory Server 6.1
· IBM Tivoli Access Manager 6.1
Configuration diagram for Standalone WebSphere Testing Environment Diagram
The following tests were conducted using Hatj tool to simulate multiple users performing their various tasks over specific periods of time.
WebSphere Portal 6.1.5 InfoCenter Main URL:
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”
2. Install TAM Server, using the topic “Planning for external security managers”
3. Install WebSphere Portal Stand-Alone Server on AIX, using the topic “Installing WebSphere Portal on AIX”
a. Install WebSphere Portal
b. Configure/Transfer the remote database(s)
4. Install and Configure the IBM HTTP Web server, using the topic “Preparing a remote Web server on AIX/Linux/Solaris”
5. Configure TAM Security for Environment using topic “Configuring Tivoli Access Manager”
6. Created Wiki and Blog test sections using topic “Working with preinstalled Web content”
7. Tune All Servers for Portal related settings.
8. Restart environment and verify all settings
Test User Configuration
The following tests were conducted using HAT-J, which is a similar opensource tool to LoadRunner, to simulate the multiple users performing their various tasks over specific periods of time.
WIKI Test: 25 Concurrent Users logging into portal over a 24 hour time span and randomly viewing wikis created by other users, randomly create their own wiki, randomly add to another person’s wiki, randomly edit their own wiki, and randomly delete their own wikis.
BLOG Test: 25 Concurrent Users logging into portal over a 24 hour time span and randomly viewin blog created by other users, randomly create their own blog, randomly add to another person’s blog, randomly edit their own blog, and randomly delete their own blog.
COMBO Test: 30 Concurrent Users logging into portal over a 72 hour time span and randomly conducting either a wiki or blog test as listed above.