Presentation is loading. Please wait.

Presentation is loading. Please wait.

WebSphere Portal Technical Conference U.S. 2007 WebSphere Portal v6 Migration Rob Holt, WP Migration.

Similar presentations


Presentation on theme: "WebSphere Portal Technical Conference U.S. 2007 WebSphere Portal v6 Migration Rob Holt, WP Migration."— Presentation transcript:

1 WebSphere Portal Technical Conference U.S. 2007 WebSphere Portal v6 Migration Rob Holt, WP Migration

2 WebSphere Portal Technical Conference U.S. 2007 2 Agenda Overview Preparing for migration Migration Steps Migration of additional components Log Files, Best Practices, Resources Other things to think about Q & A

3 WebSphere Portal Technical Conference U.S. 2007 3 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

4 WebSphere Portal Technical Conference U.S. 2007 4 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

5 WebSphere Portal Technical Conference U.S. 2007 5 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

6 WebSphere Portal Technical Conference U.S. 2007 6 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 Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

7 WebSphere Portal Technical Conference U.S. 2007 7 Supported Migration Paths v5.0.2.x Portal Server Direct migration to V6 v6 Portal Server Enable Extend Express Enable Extend v5.1.0.x Portal Server

8 WebSphere Portal Technical Conference U.S. 2007 8 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

9 WebSphere Portal Technical Conference U.S. 2007 9 Core Portal Artifacts Migration will automatically migrate the core Portal artifacts  Themes  Skins  Screens  Portlet Applications  Access Control  User Customizations  Virtual Portal  Markups  Global settings  Portal Resources  JCR Content  Credential Vault Slots

10 WebSphere Portal Technical Conference U.S. 2007 10 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

11 WebSphere Portal Technical Conference U.S. 2007 11 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 Standalone Server Support Process Portal Server Cluster DM Node Portal v6

12 WebSphere Portal Technical Conference U.S. 2007 12 V6.0 PortalV5.x Portal Portal 6.0 Install, Cluster Environment V5.x Deployment Manager Step 0 Initial configuration V6.0 Deployment Manager 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

13 WebSphere Portal Technical Conference U.S. 2007 13 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

14 WebSphere Portal Technical Conference U.S. 2007 14 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.

15 WebSphere Portal Technical Conference U.S. 2007 15 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

16 WebSphere Portal Technical Conference U.S. 2007 16 Migration Wizard Handles migration from v5.0 and v5.1 Easy to use GUI Independent import and export phases.

17 WebSphere Portal Technical Conference U.S. 2007 17 Migration Wizard Wizard Demo

18 WebSphere Portal Technical Conference U.S. 2007 18 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

19 WebSphere Portal Technical Conference U.S. 2007 19 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

20 WebSphere Portal Technical Conference U.S. 2007 20 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

21 WebSphere Portal Technical Conference U.S. 2007 21 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

22 WebSphere Portal Technical Conference U.S. 2007 22 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

23 WebSphere Portal Technical Conference U.S. 2007 23 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

24 WebSphere Portal Technical Conference U.S. 2007 24 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: /log/MigrationMessages.log /log/MigrationTrace.log The following log files are created only when using the migration wizard: /log/migrationwizard.log /log/migrationwizardlog.txt

25 WebSphere Portal Technical Conference U.S. 2007 25 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

26 WebSphere Portal Technical Conference U.S. 2007 26 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 /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.

27 WebSphere Portal Technical Conference U.S. 2007 27 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.

28 WebSphere Portal Technical Conference U.S. 2007 28 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

29 WebSphere Portal Technical Conference U.S. 2007 29 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 /installableApps directory.

30 WebSphere Portal Technical Conference U.S. 2007 30 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

31 WebSphere Portal Technical Conference U.S. 2007 31 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.

32 WebSphere Portal Technical Conference U.S. 2007 32 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

33 WebSphere Portal Technical Conference U.S. 2007 33 Migration resources Best resource for migration information

34 WebSphere Portal Technical Conference U.S. 2007 34 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

35 WebSphere Portal Technical Conference U.S. 2007 35 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

36 WebSphere Portal Technical Conference U.S. 2007 36 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

37 WebSphere Portal Technical Conference U.S. 2007 37 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)

38 WebSphere Portal Technical Conference U.S. 2007 38 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.

39 WebSphere Portal Technical Conference U.S. 2007 39 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

40 WebSphere Portal Technical Conference U.S. 2007 40 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

41 WebSphere Portal Technical Conference U.S. 2007 41 Migration Roadmap Back up

42 WebSphere Portal Technical Conference U.S. 2007 42 Migration Roadmap

43 WebSphere Portal Technical Conference U.S. 2007 43 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 Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

44 WebSphere Portal Technical Conference U.S. 2007 44 Assessment Gather the people Consider a core Migration team Identify education requirements Developer, Administrator… Hardware requirements Possible Upgrades, All levels Topology assessment Downtime tolerance, Failover support Application architecture Tightened specifications Dependencies between apps API removal, JDK changes Vendor apps and WebSphere products J2EE/JDK/WebSphere version requirements Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

45 WebSphere Portal Technical Conference U.S. 2007 45 Planning Build a plan based on assessment Hardware requirements Educational needs Identify early adopters Identify Pilot projects Consider risk factors Create an execution timeline Include a rollback plan Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

46 WebSphere Portal Technical Conference U.S. 2007 46 Skills Plan for education New development tooling Changes in WebSphere administration model Changes in the latest WebSphere version New standards Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

47 WebSphere Portal Technical Conference U.S. 2007 47 Runtime Environment Migrate test systems iteratively Development Integration System test Performance Pre-Production Production Based on your environment Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

48 WebSphere Portal Technical Conference U.S. 2007 48 Development Environment May require a change in IDE Progress iteratively, expand outward Assume application compatibility Assess apps, based on known issues If no changes required, perform standard regression If development is required do it iteratively Initially make changes that are required to support version migration Reduces complexity of planning, diagnosis and debug - “Keep it Simple” Test to the depth of test environment that fits your comfort level Then do any necessary new code development and iterate following your standard practices Address Deprecations at some point Ideally as part of application maintenance Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment

49 WebSphere Portal Technical Conference U.S. 2007 49 Test/Production/Review Run your standard test processes Progress applications normally through the test environments Ensure Performance is measured Differences exist between WebSphere versions JDK changes may have occurred Have a rollback plan for production Practice on another system earlier in the cycle Review the results of the Migration Update the plan for next time Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment


Download ppt "WebSphere Portal Technical Conference U.S. 2007 WebSphere Portal v6 Migration Rob Holt, WP Migration."

Similar presentations


Ads by Google