Test Infrastructure: Migration from WebSphere
Portal for z/OS V6.0.1.4 to WebSphere Portal for z/OS V6.1.0.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 for z/OS V6.0.1.4 (with Web Content Management
(WCM) 6.0.1.4) to WebSphere Portal for z/OS V6.1.0.1
Environment overview
The environment included the following items:
· WebSphere®
Portal for z/OS V6.0.1.4, Web Content Management 6.0.1.4 and WebSphere®
Application Server 6.0.2.31
· WebSphere®
Portal for z/OS V6.1.0.1, Web Content Management 6.1.0.1 and WebSphere®
Application Server 6.1.0.19
· IBM DB2®
8.1
· IBM® HTTP
Server 6.1
· Lotus Domino
Directory LDAP 8.0
· Lotus Sametime
7.5.1
· Tivoli Access
Manager 6.0.0.13
· Tivoli Access
Manager WebSEAL 6.0.0.13
The following picture shows the how the environment was configured:
test_zos_migrate.jpg
Machine Specifications:
|
MACHINE
|
OS
|
CPU
|
MEMORY
|
DISK
|
MODEL
|
Portal 6.0.1.4 DM
Portal 6.0.1.4 Federated Node
Portal 6.1.0.1 DM
Portal 6.1.0.1
Federated Node
Local Search
Sametime Server
Database DB2 8.1 PUT0803
| z/OS 1.8
| 4 CPs
|
VM Guest 6 GB
|
|
|
| Database DB2 8.1 PUT0803 for Portal 6.1.0.1
| z/OS 1.8
| 4 CPs
| VM Guest 6 GB
|
|
|
Portal 6.0.1.4 DM
Portal 6.0.1.4 Federated Node
Portal 6.1.0.1 DM
Portal 6.1.0.1
Federated Node
Database DB2 8.1 PUT0803
| z/OS 1.8
| 4 CPs
| VM Guest 10 GB
|
|
|
Portal 6.0.1.4 DM
Portal 6.1.0.1 DM
Database DB2 8.1 PUT0803 DS1 for 6.0.1.4
| z/OS 1.8
| 4 CPs
| VM Guest 6 GB
|
|
|
| Database DB2 8.1 PUT0803 for 6.1.01
| z/OS 1.8
| 4 CPs
| VM Guest 6 GB
|
|
|
| Domino LDAP
| Windows 2003 R2 Enterprise Server
| 1 x 3.2 GHz
| 3.5 GB
| 2 x 136 GB
| 6221
|
| Domino 8.0 LDAP/ TAM 6.0.0.13 / TAM WebSEAL
| Windows 2003 R2 Enterprise Server
| 2 x 3.2 GHz
|
2 GB
|
2 x 70 GB
|
6221
|
| IBM HTTP Server 6.1
| Windows 2003 R2 Enterprise Server
| 1 x 2.8 GHz
| 2 GB
| 1 x 40 GB
| 6221 |
Installation and Configuration
WebSphere
Portal Information Center
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.0 Install/configure Domino Directory LDAP
using the product documentation and the topic “Installing Lotus Domino”.
2.0 Install/configure Portal 6.0.1.4 on Primary
node (WP60_1) using the topic “WebSphere Portal Version 6.0.1.4”.
3.0 Install/configure Portal 6.0.1.4 on Secondary
node (WP60_2) using the topic “WebSphere Portal Version 6.0.1.4”.
4.0 Install/configure Portal 6.0.1.4 on Standalone
node (WP60_3) using the topic “WebSphere Portal Version 6.0.1.4”.
5.0 Install/configure DB2 database for WP60_1,
transfer data from WP60_3 using the topic “Planning for DB2”.
6.0 Install/configure DB2 for WP60_3, transfer
data from WP60_3 using the topic “Planning for DB2”.
7.0 Enable external security for WP60_3 to Domino
Directory using the topic “Setting up Domino Directory”.
8.0 Install WebSphere Application Server Network
Deployment on DM60 using the topic “Setting up a cluster”.
9.0 Federate WP60_1 to Deployment Manager using
the topic “Installing and federating the primary node”.
10.0 Create a cluster with just the Primary
node and DM60 using the topic “Creating the cluster”.
11.0 Add Secondary node WP60_2 to cluster using
the topic “Installing and federating the primary node”.
12.0 Enable external security for WP60_1, WP60_2
and DM to Domino Directory using the topic “Setting up Domino Directory”,
and “Enabling LDAP security after cluster creation”.
13.0 Configure remote rendering of WP60_3 content
on WP60_1 using the topic “Configuring the remote rendering portlet”.
14.0 Install/configure IBM HTTP server for WP60
cluster using the topic “Setting up a Web server with WebSphere Portal”.
15.0 Create four Virtual Portals on WP60 cluster
using the topic “Planning for virtual portals”.
16.0 Populate WP60 cluster with maximum of 15k
pages across Virtual Portals 1-3.
17.0 Populate WP60 cluster with eight Click-to-action
Wired Portlets across Virtual Portals 1-3.
18.0 Populate WP60 cluster with 250 Cloned portlets
across Virtual Portals 1-3 using the topic “Reference: Sample XML configuration
files”: Sample file ClonePortlet.xml.
19.0 Populate WP60 cluster Virtual Portal 4
with 64 non-‘out of box’ portlets.
20.0 Setup access controls for different groups
on Virtual Portal 4 using the topic “Access control scenarios”.
21.0 Populate WP60 cluster with portlets from
the Portlet catalog, including a large portlet (>20MB).
22.0 Install PZN sample database and portlet
on WP60 cluster using the topic “Install Personalization sample and database”
or customized equivalent.
23.0 Populate WP60 cluster with PDM docs (of
different sizes and types).
24.0 Setup search collections for WP60 cluster
and verify search functionality using the topic “Portal Search”.
25.0 Backup all WP60 cluster environments, including
files, systems and databases.
26.0 Configure WP60 cluster for External Security
Manager (Tivoli Access Manager) using the topic “Using Tivoli Access Manager
with WebSphere Portal”.
27.0 Create automation (using HP/Mercury LoadRunner)
to step through pages and portlets of WP60 cluster environment as single
user.
28.0 Run automation (using HP/Mercury LoadRunner)
to validate WP60 cluster environment as single user.
29.0 Prepare WP60 environments prior to migration
(including installing fixes) using the topic “Preparing your previous
environment for migration”.
30.0 Install/configure Portal 6.1 on Primary
node (WP61_1) using the topic “Installing WebSphere Portal”.
31.0 Install/configure Portal 6.1 on Standalone
node (WP61_3) using the topic “Installing WebSphere Portal”.
32.0 Prepare all WP61 environments prior to
migration using the topic “Preparing your new environment for migration”.
33.0 Configure DB2 database for transfer
database from WP61_1. Transferred only the Release, Feedback, Likeminds,
and Community domains using the topic “Planning for DB2”.
34.0 Copy JCR60 database using database utilities,
and Connect WP61_1 to the copy using the topic “Sharing JCR domain data”.
35.0 Connect WP61_1 to CUSTOMIZATION60
database using the topic “Sharing Customization domain data”.
36.0 Repeat the two steps above for connecting
the WP61_3 environment to its respective databases.
37.0 Install the Document List portlet on your
Portal 6.0.1.4 environment to migrate your PDM documents to Web Content
Management file resource components using the topic “Document Migration”.
38.0 Enable external security for WP61_1, and
WP61_3 to Domino LDAP using the topic “Configuring security on Windows”.
39.0 Create four empty Virtual Portals for WP61_1,
matching URL contexts of VPs on WP60 cluster using the topic “Virtual
portals reference”.
40.0 Configure WP61_1 for external security
manager TAM for authentication, and authorization using the topic “Configuring
Tivoli Access manager”.
41.0 Migrate 6.0.1.4 Portal (default portal
WP60 cluster) to WP61_1 using the topics “Understanding migration”, “Planning
for migration”, “Migration scenarios”, “Preparing for migration” and
“Migrating to a same machine”.
42.0 Migrate 6.0.1.4 Portal (virtual portals)
to WP61_1 using the topic “Importing configuration for migration to the
same machine”.
43.0 Make migration fail and try to resume.
44.0 Migrate remote search server, and web search
collections using the topic “Migrating your customized resources”.
45.0 Complete the post-migration steps for WCM
content and remote rendering portlets by using the topic “Version 6.0
to 6.1 post migration steps”.
46.0 Validate migration successful in all environments,
search logs using the topic “Verifying the migration tasks”.
47.0 Federate and Cluster the WP61_1 server
as a Primary node using the topic “Setting up a clustered production environment”.
48.0 Configure the Secondary node in the WP61
cluster for external security manager TAM for authentication, and authorization
using the topic “Configuring Tivoli Access manager”.
49.0 Create automation (using HP/Mercury LoadRunner)
to step through pages and portlets of 6.1 environment as single user.
50.0 Run automation (using HP/Mercury LoadRunner)
to validate 6.1 environment as single user.
51.0 Add pages and portlets after migration.
52.0 Verify migration content in Information
Center.
53.0 Execute twelve HR Post-Migration Reliability
Longrun (using HP/Mercury LoadRunner).
Test User Configuration
This environment was load and stress tested using LoadRunner with up to
120 concurrent users accessing remotely-rendered content including portlets
and pages for 12 continuous hours.