Transcript WebSphere Portal Technical Conference US 2007

WebSphere Portal Technical Conference U.S. 2007
WebSphere Portal v6 Migration
Rob Holt, WP Migration
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
Q&A
2
WebSphere Portal Technical Conference U.S. 2007
Disclaimer
THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS PROVIDED FOR
INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE
COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS
DOCUMENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT
PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT
NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE
USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENTATION OR ANY OTHER
DOCUMENTATION. NOTHING CONTAINED IN THIS DOCUMENTATION IS INTENDED TO,
NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS
FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND
CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM
SOFTWARE
3
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
What is migration
Migration Plan Roadmap
Supported migration
paths
Components to migrate
Portal core artifacts
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
Q&A
4
WebSphere Portal Technical Conference U.S. 2007
What is migration
Migration considerations
More than just software development
Must consider the applications, infrastructure, education and culture
Migration process should not compromise day-to-day business
Manage complexity, expectations, expense and risk
Careful planning is required
Each situation is unique
There is no one standard plan
5
WebSphere Portal Technical Conference U.S. 2007
Migration Plan Roadmap
Assessment
Assessment
Planning
Planning
Skills
Skills
Development Environment
Application Code Migration
Runtime Environment Migration
Development
Environment
Runtime
Environment
Code
Migration
Runtime
Migration
Unit Test
Test
Systems
Test
Production
Review the results
Test
Production
Review
results
6
WebSphere Portal Technical Conference U.S. 2007
Supported Migration Paths
Express
Enable
Extend
v5.0.2.x Portal Server
Enable
Extend
v6 Portal Server
v5.1.0.x Portal Server
7
WebSphere Portal Technical Conference U.S. 2007
Components to Migrate
There are many components that must participate in the migration process
Typical
WMM
Virtual resources
Custom portlets
Themes, skins, screens
Process tasks
Portlets
configuration
v5.x Portal Server
Portal Document
Manager
Personalization
Page configuration
WCM
Access control
Transcoding
WSRP resources
Etc…
Clients
configuration
v6 Portal Server
Advanced
8
WebSphere Portal Technical Conference U.S. 2007
Core Portal Artifacts
Migration will automatically migrate the core Portal artifacts







9
Themes
Skins
Screens
Portlet Applications
Access Control
User Customizations
Virtual Portal





Markups
Global settings
Portal Resources
JCR Content
Credential Vault Slots
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Portal 6.0 Install
Prepare Prior Portal
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
Q&A
10
WebSphere Portal Technical Conference U.S. 2007
Portal 6.0 Install
Install the 6.0 Portal
WP v6 can be on the same machine or a different machine
Operating system family must match
Standalone
Server Support
Portal v6
11
Process Portal
Server Cluster
DM Node
Portal v6
Cell
WebSphere Portal Technical Conference U.S. 2007
Portal 6.0 Install, Cluster Environment
V5.x Deployment
Manager
Step 0
Initial configuration
Step 1
•Migrate single node to
standalone node
Step 2
• Install Dmgr
Step 3
V5.x Portal
V5.x Portal
V5.x Portal
V5.x Portal
• Federate node and create
cluster
Step 4
V6.0 Deployment
Manager
• Create additional cluster
members
V6.0 Portal
12
V6.0 Portal
V6.0 Portal
WebSphere Portal Technical Conference U.S. 2007
V6.0 Portal
Portal 6.0 Install, Continued
Prepare WP 6.0 Portal configuration
Enable security to match prior Portal
Users in directory must match
Run database transfer
Reference the Portal InfoCenter for a list of
required fixes
Validate Portal function
Verify admin login
13
WebSphere Portal Technical Conference U.S. 2007
Prepare Prior Portal
Install required fixes (Mandatory)
Reference the Portal InfoCenter for a list of required fixes
Refer to maintenance procedures for v5.0 and v5.1 when applying required
fixes.
Backup previous Portal (Recommended)
Good idea even though migration does not make any changes
Disable user access (Recommended)
Set the portal to be active for read only access, this prevents the loss of updates
while migration is executing.
14
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Migration Steps
Migration Wizard
Command line
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
Q&A
15
WebSphere Portal Technical Conference U.S. 2007
Migration Wizard
Handles migration from
v5.0 and v5.1
Easy to use GUI
Independent import
and export phases.
16
WebSphere Portal Technical Conference U.S. 2007
Migration Wizard
Wizard Demo
17
WebSphere Portal Technical Conference U.S. 2007
Command line migration
Required to be used when doing a remote migration
Provided for host operating systems with no GUI support
Provides direct access to the migration commands
Used for migration of additional components
Automated core migration tasks
prop-collector
collector-extract
export-portal-content
import-portal-content
18
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional components
PDM
WCM
PZN
Log Files, Best Practices, Resources
Other things to think about
Q&A
19
WebSphere Portal Technical Conference U.S. 2007
Additional Components – PDM
 Export from PDM 5.0
WPMigrate migrate-pdm-export-50x
 Convert XML to 5.1 format
WPMigrate migrate-pdm-convert-50x
 Transform XML from 5.1 to 6.0
WPMigrate migrate-pdm-transform-50x
 Import to PDM 6.0
WPMigrate migrate-pdm-import-50x
20
WebSphere Portal Technical Conference U.S. 2007
Additional Components - WCM
Migrate all the WCM data
Install WCM migration tool
WPSconfig configure-wcm-migration
wcmmigrate all-data
Migrate WCM users
wcmmigrate users
Configure rendering portlets
wcmmigrate configure-local
wcmmigrate configure-remote
Remove the WCM migration tool
WPSconfig.bat remove-wcm-migration
21
WebSphere Portal Technical Conference U.S. 2007
Additional Components - PZN
1. Migrate from PDM 5.0 or 5.1
WPmigrate migrate-pzn-50x
WPmigrate migrate-pzn-51x
2. Migrate exported 5.1 data
WPmigrate migrate-pzn-svData-transform-51x
22
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Log files
Information for problem
analysis
Best practices
Migration Resources
Other things to think about
Q&A
23
WebSphere Portal Technical Conference U.S. 2007
Log files
Log files are created using the command line scripts and the migration
wizard.
The following log files are always created during the migration process:
• <wp_root>/log/MigrationMessages.log
• <wp_root>/log/MigrationTrace.log
The following log files are created only when using the migration wizard:
• <wp_root>/log/migrationwizard.log
• <wp_root>/log/migrationwizardlog.txt
24
WebSphere Portal Technical Conference U.S. 2007
Information for problem analysis
Current and Previous Portal configuration information
LDAP host
DB Type and configuration parameters
Current health of the previous and current portal
Previous portal configuration
Single Node/Clustered
Process server configuration
Network configuration
Remote migration/Single server
Network adapter/hostname configuration
25
WebSphere Portal Technical Conference U.S. 2007
Information for problem analysis (cont)
OS
OS level
Fix packs
Portal maintenance level – Including applied fix packs and individual fixes
for previous and v6 Portal
Log files
All temporary work files
Zip the directory <wp_root>/migration/work - be sure to compress this
information as some of the files can be several 100 MB’s in size. Text compress
works well, 200 MB XmlAccess files can be zipped into files < 7MB.
26
WebSphere Portal Technical Conference U.S. 2007
Best Practices
Review the directions in the Infocenter
Follow the pre-migration steps very carefully
Verify the HTTP server connection will not time out. It is preferable that the
internal WAS HTTP port is used for migration.
When attempting to migrate Portal on a machine with limited resources or
other servers running on them. Only start one server at a time.
Severe resource contention will cause failures, timeouts on DB or LDAP connections.
27
WebSphere Portal Technical Conference U.S. 2007
Best Practices (cont)
If both Portals are on the same machine, the Portal can use new or
conflicting ports
If conflicting ports, run one Portal at a time or change the Ports for the new portal
temporarily.
Start the previous server during export
Verify the previous server is reachable (i.e. check HTTP server, or firewall)
when attempting to export from remote server
Start the current server during import
28
WebSphere Portal Technical Conference U.S. 2007
Best Practices (cont)
Do not make additional changes to your Portal
Start with fresh install
Do not deploy portlets
Do not create pages
Do not change access control
Do not delete pages
If additional administration is needed, run after migrating
Be sure to specify the real host name in the v5 wpconfig.properties file,
“localhost” will not work when doing a remote migration.
Be sure to copy ONLY the non out of the box portlets to the
<wp_root>/installableApps directory.
29
WebSphere Portal Technical Conference U.S. 2007
Best Practices (cont)
If clustered, prevent access to the node from which the migration will be done.
Stop the node agent and prevent end user access to the node.
If using LDAP, verify the number of groups in the wmm.xml file is equal to or
larger than the number of groups visible to Portal in the LDAP server.
Verify the WAS and Portal admin user ID’s and passwords are specified
correctly for each migration task
30
WebSphere Portal Technical Conference U.S. 2007
Best Practices – Portlets
Login to the current portal installation, to verify installation has completed
successfully.
Shut down the node agent during a cluster migration
Allocate enough memory to the OS process or partition that is performing
migration.
Be sure any users from LDAP that have been deleted are also deleted from
the Portal server.
31
WebSphere Portal Technical Conference U.S. 2007
Best Practices – Portlets
Restart the v6 Portal after migration if the migrated themes and skins or
pages don’t show up properly.
Don’t rewrite portlets when migrating. Portlet changes that cause
migration difficulty:
Unique ID (uid)
WAR file name
Portlet parameters
Servlet changes
Portlet count in War file
32
WebSphere Portal Technical Conference U.S. 2007
Migration resources
Best resource for migration information
33
WebSphere Portal Technical Conference U.S. 2007
Migration Resources (cont)
WebSphere Portal Documentation
http://www-128.ibm.com/developerworks/websphere/zones/portal/proddoc.html
6.0 Information Center:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp
WebSphere Portal V5.0 Production Deployment and Operations Guide
http://www.redbooks.ibm.com/redpieces/abstracts/sg246391.html?Open
Developer works: WebSphere Portal Zone
http://www-106.ibm.com/developerworks/websphere/zones/portal/
IBM WebSphere Portal V6: Best Practices for Migrating from V5.1
http://w3.itso.ibm.com/redpieces/abstracts/redp4227.html
34
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
External Components
Advanced Customizations
Q&A
35
WebSphere Portal Technical Conference U.S. 2007
External Components
Rational Application Developer
Upgrade to RAD7 for the Portal 6.0 test environment
RAD can help with some manual portlet migration
Transfer LDAP users if needed
This is not recommended to be done before migration.
Upgrade HTTP server
Upgrade DB Server application
36
WebSphere Portal Technical Conference U.S. 2007
Advanced Customizations
Custom content may require manual updates
Custom themes and skins
• Manual modification is required to take advantage of the v6 features such as
drag and drop, fly out, context menus, etc….
• See the info center on how to upgrade prior themes to add new functionality.
Custom portlets
• C2A Portlets and Struts portlets may require updating
• Most other portlets should run as is
Custom XmlAccess scripts –
• XmlAccess is forward compatible.
• You can use the XmlAccess script used to set up your previous portal.
Transfer WebSphere Member Manager (WMM) database tables
• If you are using a WMM Custom User Registry
• Required for WebSphere Content Manager (WCM)
37
WebSphere Portal Technical Conference U.S. 2007
Advanced Customization (cont)
Transfer LDAP users if needed
Redeployment of WAS custom services
If using CredentialVaultService.getDefaultUserVaultSegmentId() API
• Migrating the credential vault is covered in the infocenter.
• Change com.ibm.wps.util.ObjectId  com.ibm.portal.ObjectId
In the rare case where customizations are on admin pages they need
to be recreated. None of the admin pages are migrated.
•Any modifications to ADMIN pages or portlets will need to be manually recreated.
•The wp.migration.admin component compensates for default theme selection
by explicitly assigning the IBM theme to the default Admin pages.
38
WebSphere Portal Technical Conference U.S. 2007
Limitations
WPS Tasks are not migrated
XmlAccess can not migrate large numbers of users
There is no undo
Migration of portlets within EAR files requires special handling
Services are not migrated automatically
39
WebSphere Portal Technical Conference U.S. 2007
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional
components
Log Files, Best Practices,
Resources
Other things to think about
Q&A
Thank You
40
WebSphere Portal Technical Conference U.S. 2007