Upload
melvin-leonard
View
225
Download
1
Embed Size (px)
Citation preview
WebSphere Portal Technical Conference U.S. 2007WebSphere Portal Technical Conference U.S. 2007
WebSphere Portal v6 Migration
Rob Holt, WP Migration
WebSphere Portal Technical Conference U.S. 20072
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional components
Log Files, Best Practices, Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 20073
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
WebSphere Portal Technical Conference U.S. 20074
Agenda
OverviewWhat is migrationMigration Plan RoadmapSupported migration pathsComponents to migratePortal core artifacts
Preparing for migration
Migration Steps
Migration of additional components
Log Files, Best Practices, Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 20075
What is migration
Migration considerationsMore than just software developmentMust consider the applications, infrastructure, education and cultureMigration process should not compromise day-to-day businessManage complexity, expectations, expense and risk
Careful planning is requiredEach situation is uniqueThere is no one standard plan
WebSphere Portal Technical Conference U.S. 20076
Migration Plan Roadmap
Assessment
Planning
Skills
Development Environment
Application Code Migration
Runtime Environment Migration
Test
Production
Review the results
Assessment
Planning
Skills
Production
Review results
Test
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
WebSphere Portal Technical Conference U.S. 20077
Supported Migration Paths
v5.0.2.x Portal Server
Direct migration to V6
Direct migration to V6
v6 Portal ServerEnableExtend
ExpressEnableExtend
v5.1.0.x Portal Server
WebSphere Portal Technical Conference U.S. 20078
Components to Migrate
WMM
Custom portlets
Process tasks
Portlets configuration
Page configuration
Access control
WSRP resources
Clients configuration
Virtual resources
Themes, skins, screens
Portal Document Manager
Personalization
WCM
Transcoding
Etc…
There are many components that must participate in the migration process
v5.x Portal Server
Advanced
Typical
v6 Portal Server
WebSphere Portal Technical Conference U.S. 20079
Core Portal Artifacts
Migration will automatically migrate the core Portal artifacts
ThemesSkinsScreensPortlet ApplicationsAccess ControlUser CustomizationsVirtual Portal
MarkupsGlobal settingsPortal ResourcesJCR ContentCredential Vault Slots
WebSphere Portal Technical Conference U.S. 200710
Agenda
Overview
Preparing for migrationPortal 6.0 InstallPrepare Prior Portal
Preparing for migration
Migration Steps
Migration of additional components
Log Files, Best Practices, Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 200711
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
Cell
StandaloneServer Support
Process Portal Server Cluster
DM NodePortal v6
Portal v6
WebSphere Portal Technical Conference U.S. 200712
V6.0 Portal
V5.x Portal V5.x Portal V5.x Portal V5.x Portal
Portal 6.0 Install, Cluster EnvironmentV5.x Deployment
ManagerStep 0Initial configuration
V6.0 DeploymentManager
Step 1•Migrate single node to standalone node
Step 2• Install Dmgr
Step 3• Federate node and create cluster
Step 4• Create additional cluster members
V6.0 Portal V6.0 Portal V6.0 Portal
WebSphere Portal Technical Conference U.S. 200713
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
WebSphere Portal Technical Conference U.S. 200714
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.
WebSphere Portal Technical Conference U.S. 200715
Agenda
Overview
Preparing for migration
Migration StepsMigration WizardCommand line
Migration of additional components
Log Files, Best Practices, Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 200716
Migration WizardHandles migration from v5.0 and v5.1
Easy to use GUI
Independent import and export phases.
WebSphere Portal Technical Conference U.S. 200717
Migration Wizard
Wizard Demo
WebSphere Portal Technical Conference U.S. 200718
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 tasksprop-collector collector-extract export-portal-content import-portal-content
WebSphere Portal Technical Conference U.S. 200719
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional componentsPDMWCMPZN
Log Files, Best Practices, Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 200720
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
WebSphere Portal Technical Conference U.S. 200721
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
WebSphere Portal Technical Conference U.S. 200722
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
WebSphere Portal Technical Conference U.S. 200723
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional components
Log Files, Best Practices, Resources
Log filesInformation for problem analysisBest practicesMigration Resources
Other things to think about
Q & A
WebSphere Portal Technical Conference U.S. 200724
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
WebSphere Portal Technical Conference U.S. 200725
Information for problem analysis
Current and Previous Portal configuration informationLDAP hostDB Type and configuration parameters
Current health of the previous and current portal
Previous portal configurationSingle Node/ClusteredProcess server configuration
Network configurationRemote migration/Single server Network adapter/hostname configuration
WebSphere Portal Technical Conference U.S. 200726
Information for problem analysis (cont)
OSOS levelFix 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.
WebSphere Portal Technical Conference U.S. 200727
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.
WebSphere Portal Technical Conference U.S. 200728
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
WebSphere Portal Technical Conference U.S. 200729
Best Practices (cont)
Do not make additional changes to your PortalStart with fresh installDo not deploy portletsDo not create pagesDo not change access controlDo not delete pagesIf 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.
WebSphere Portal Technical Conference U.S. 200730
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
WebSphere Portal Technical Conference U.S. 200731
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.
WebSphere Portal Technical Conference U.S. 200732
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 namePortlet parametersServlet changesPortlet count in War file
WebSphere Portal Technical Conference U.S. 200733
Migration resources
Best resource for migration information
WebSphere Portal Technical Conference U.S. 200734
Migration Resources (cont)
WebSphere Portal Documentationhttp://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 Zonehttp://www-106.ibm.com/developerworks/websphere/zones/portal/
IBM WebSphere Portal V6: Best Practices for Migrating from V5.1http://w3.itso.ibm.com/redpieces/abstracts/redp4227.html
WebSphere Portal Technical Conference U.S. 200735
Agenda
Overview
Preparing for migration
Migration Steps
Migration of additional components
Log Files, Best Practices, Resources
Other things to think aboutExternal ComponentsAdvanced Customizations
Q & A
WebSphere Portal Technical Conference U.S. 200736
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
WebSphere Portal Technical Conference U.S. 200737
Advanced Customizations
Custom content may require manual updatesCustom 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)
WebSphere Portal Technical Conference U.S. 200738
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 re-created.•The wp.migration.admin component compensates for default theme
selection by explicitly assigning the IBM theme to the default Admin pages.
WebSphere Portal Technical Conference U.S. 200739
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
WebSphere Portal Technical Conference U.S. 200740
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