Test Infrastructure: Virtual portal,
multi-realm, multi-LDAP, stand-alone environment
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 Virtual Portal feature provided by WebSphere® Portal with multiple
LDAPs and realms in a stand-alone environment.
Environment overview
The environment included the following items:
- WebSphere Portal v.6.1
- z/OS® DB2® v.9.1
- IBM® Tivoli® Directory Server 6.1 (32
bit) on RedHat Linux® AS4
- IBM Tivoli Directory Server 6.1 (64
bit) on RedHat Linux AS4
- IBM Tivoli Directory Server 6.0 (32
bit) on Microsoft® Windows® 2003 Server
- Microsoft Active Directory (32 bit)
on Windows 2003 Server
- SunOne 5.2 (32 bit) on Windows 2000
SP4
The following picture shows the how the environment was configured:
Machine specifications
The following table details the machines used in this test infrastructure:
|
Use
|
|
RAM
Memory
|
Hard disk
qty – size
|
Operating
System
|
Software
|
|
Stand-alone server
|
2
|
4GB
|
|
z/Linux Suse9
64bit
z/VM 5.3.0) (z/OS 01.09.00
|
WebSphere Application Server /
WebSphere Portal
|
|
z/OS DB2 server
|
4 – (shared)
|
6GB
|
|
z/OS v1.9
2nd level guest
|
DB2 v9.1 Put0803
|
|
Remote content server
|
16 CPU
|
128GB
|
|
i5/OS v5r4
|
WebSphere Application Server /
WebSphere Portal /
Local DB2 i5/OS V5R4m0
|
|
LDAP 1
|
1 - 1GHz
|
2GB
|
1 x 18GB
|
RedHat Linux AS4
|
ITDS 6.1
(32 Bit)
|
|
LDAP 2
|
2-2.8 GHz
|
2GB
|
1 x 70GB
|
Windows 2000 Server
SP4
|
ITDS 6.0
(32 Bit)
|
|
LDAP 3
|
1-1.0 GHz
|
1GB
|
1 x 37GB
|
Windows 2000 Server
|
LDAP AD (32bit)
|
|
LDAP 4
|
1-1.0 GHz
|
2GB
|
2 x 18GB
|
Windows 2000 Sever SP4
|
SunOne5.2
(32bit)
|
|
LDAP 5
|
4-1.6 GHz
|
3.7GB
|
|
RedHat Linux AS4
|
ITDS 61
(64bit)
|
Installation and configuration
Refer to the topics from the
WebSphere
Portal 6.1 Information Center
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.0 Install and configure z/OS DB2 Server using the topic “Planning
for DB2 for z/OS”
2.0 Install and configure the Content Server using the topic “Setting
up a stand-alone production server”
a. Preparing your System i5/OS
b. Install Full Content
WebSphere Portal
c. Configure and transfer
to local databases on iSeries
3.0 Set up multiple LDAPs on the Content Server and stand-alone server
using the topic “Adding an LDAP user registry on i5/OS”
a. Prepare LDAP1
b. Add LDAP 1 to the federated
VMM
c. Repeat for all LDAPs
being used
4.0 Create Web Content Managment (WCM) libraries and content on Content
Server using topic “Creating Web content”
a. Create the content
b. Specify the user level
permissions for the content
5.0 Install and configure the stand-alone server using the topic “Setting
up a stand-alone production server”
a. Preparing your Linux
operating system
b. Install Full Content
WebSphere Portal
c. Configure and transfer
the remote database(s) using “Preparing DB2 for z/OS for a stand-alone
production server."
6.0 Set up multiple LDAPSs on the stand-alone server using the topic “Adding
an LDAP user registry on Linux”
a. Prepare LDAP1
b. Add LDAP 1 to the federated
VMM
c. Repeat for all LDAPs
being used
7.0 Set up multiple realms on stand-alone server using the topic “Adding
realm support on Linux”
a. Prepare for Realm1
b. Create Realm 1
c. Repeat for all realms
being used
8.0 Set up multiple Virtual Portals using the topic “Multiple virtual
portals”
a. Prepare for Virtual
Portal 1
b. Create Virtual Portal
1
c. Repeat for all Virtual
Portals being used
9.0 Create WCM Libraries and content for Virtual Portals using topic “Creating
Web content”
a. Create the content
b. Specify the user level
permissions for the content
10.0 Create personalization (PZN) rules for Virtual Portals using topic
“Personalizing your content”
a. Create appropriate rules
based on content in each Virtual Portal
b. Create appropriate rules
to be shared across all Virtual Portals
11.0 Connect the stand-alone server to the Content Server using topic “Configuring
the remote rendering portlet”
a. Add remote rendering
portlet to stand-alone server
b. Configure remote rendering
portlet to point to Content Server with WCM data
12.0 Tune all servers using
the instructions in the
WebSphere
Portal Version 6.0 Tuning Guide 1.2
13.0 Restart environment and verify all settings
Test user configuration
The environment was tested by using HP LoadRunner and an internal IBM tool
for HTTP testing to simulate up to 300 users searching on and viewing Web
Content Management (WCM) generated content rendered through WCM local and
remote rendering portlets across the 10 Virtual Portals for a period of
72 hours, as well as testing various types of portlets. The content
had a sampling of various WCM component types, as well as Personalization
(PZN) rules.
The stand-alone environment with z/OS DB2 was also used to simulate 50
concurrent users creating Web Content Management content in the base portal
for 72 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.