Test Infrastructure: Migration from
WebSphere® Portal Express 5.0.2.3 to WebSphere Portal Express 6.1
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 migration of WebSphere Portal Express 5.0.2.3 to WebSphere Portal Express
6.1.
Environment overview
The environment included the following items:
- WebSphere Portal 5.0.2.3 and WebSphere
Application Server 5.0.2.9
- WebSphere Portal 6.1 and WebSphere Application
Server 6.1.0.15
- DB2® 8.1
- DB2 9.1 fix pack 4
- IBM® HTTP Server 6.1
- IBM Tivoli® Directory Server (ITDS)
6.1
The following picture shows the how the environment was configured:
Machine specifications
The following table gives the specifications for the machines used in this
test configuration:
|
Machine
|
OS
|
# of CPUs
|
CPU Speed
|
CPU Type
|
RAM (GB)
|
Function
|
| Portal Express 5.0.2.3
|
Windows 2003 server with
SP2
|
1
|
1.66 GHz
|
Intel
|
2
|
standalone node
|
| Database DB2 8.1 for Portal Express
5.0.2.3
|
Windows 2003 server with
SP2
|
1
|
1.66 GHz
|
Intel
|
2
|
database
|
| Portal Express 6.1
|
Windows 2003 server with
SP2
|
4
|
3.2 GHz
|
Intel
|
2
|
standalone node
|
| IBM HTTP Server 6.1
|
Windows 2003 server with
SP2
|
4
|
3.2 GHz
|
Intel
|
2
|
IHS Server
|
| Database DB2 9.1 FP4 for
Express 6.1
|
RHEL 5.0
|
2
|
2.8 GHz
|
Intel
|
4
|
database
|
| ITDS 6.1
|
Windows 2003 server with
SP2
|
4
|
3.6 GHz
|
Intel
|
4
|
LDAP server |
Installation and configuration
Refer to the topics from the
WebSphere
Portal Express 6.1 Information Center
or the
WebSphere
Portal Express 5.0.2.3 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 WebSphere Portal Express 5.0.2.3,
using the topic “Install and configure” in Express 5.0.2.3 Information
Center
2.0 Install and configure the DB2 8.1 server
using the topic “Installing --> Database” in Express 5.0.2.3 Information
Center
3.0 Transfer Cloudscape database in Portal Express
5.0.2.3 to DB2 8.1, using the topic “Installing --> Database” in Express
5.0.2.3 Information Center
4.0 Install and configure IBM Tivoli Directory
Server (ITDS) 6.1, enable security for Express 5.0.2.3 using “Installing
--> Configuring security” in Express 5.0.2.3 Information Center
5.0 Populate 5,000 pages in Express 5.0.2.3
6.0 Export all the data and configuration from
Express 5.0.2.3 following “Migrating WebSphere Portal” in Express 6.1
Information Center
7.0 Install WebSphere Portal Express 6.1, using
the topic “Setting up a stand-alone production server” in Express 6.1
Information Center
8.0 Install and configure the IBM HTTP Server
using the topic “Setting up a remote Web server with WebSphere Portal”
in Express 6.1 Information Center
9.0 Install and configure the external DB2 9.1
server using the topic “Setting up remote databases” in Express 6.1 Information
Center
10.0 Transfer database to remote DB2 9.1 using
“Setting up remote databases” in Express 6.1 Information Center
11.0 Enable security for Express 6.1 to IBM
Tivoli Directory Server (ITDS) 6.1, using the same LDAP users with Express
5.0.2.3
12.0 Copy the exported data and configuration
file from Express 5.0.2.3 to Express 6.1
13.0 Migrate to import the file into Express
6.1 following “Migrating WebSphere Portal” in Express 6.1 Information
Center, including migrating themes and skins, populated data
14.0 Make migration fail and try to resume (negative
testing)
15.0 Validate migration successful in all environments
16.0 Execute 24-hour post-migration reliability
run
17.0 Verify the run scenario, including checking
logs, GC, and so on
Test user configuration
This environment was load and tested with up to 200 concurrent users Rational®
Performance Tester to simulate users accessing the post-migrated environment,
viewing portlets or pages, randomly for 24 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.
Related articles
PE
6.1-A : Deploying WebSphere Portal Express for using idle standby