© 2008 ibm websphere portal v6.1 migration rob holt websphere portal migration lead
Post on 26-Mar-2015
236 Views
Preview:
TRANSCRIPT
© 2008 IBM
WebSphere Portal v6.1 MigrationRob HoltWebSphere Portal Migration Lead
222
Agenda
Overview
Migration
Preparing for migration
Migration Process Overview
Framework
Problem Determination
Common User Errors and Best Practices
333
Agenda Overview
– What is migration
– Migration Plan Roadmap– Assessment– Planning– Skills– Runtime Environment Migration– Development Environment– Application Code Migration– Test– Production– Review the results
– Supported migration paths
– Components to migrate
– What is migrated automatically
Migration
Preparing for migration
Migration Process Overview
Framework
Problem Determination
Common User Errors and Best Practices
444
What is Migration
Migration - Moving your existing data and functionality from one WebSphere Portal release to a newer WebSphere Portal release.
– Migration does not include the merging of new functionality with the old functionality.
– Parallel function and performance
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
555
Migration Plan Roadmap
Assessment
Planning
Skills
Runtime Environment Migration
Development Environment
Application Code Migration
Test
Production
Review the results
Assessment
Planning
Skills
Production
Review results
Test
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
666
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
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
777
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
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
888
Skills
Plan for education– New development tooling
– Changes in WebSphere Portal administration model
– Changes in the latest WebSphere version
– New standards
– New features
Assessment
Planning
Skills
Production
Review results
Test
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
999
Runtime Environment
Migrate test systems iteratively– Development
– Integration
– System test
– Performance
– Pre-Production
– Production
Based on your environment– Iterate through servers providing
support
– DB, HTTP, LDAP, etc…
Assessment
Planning
Skills
Production
Review results
Test
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
101010
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
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
111111
Test/Production/Review
Run your standard test processes– Progress applications normally through the test
environments
Ensure Performance is measured– Gather baseline measurement
– 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
DevelopmentEnvironment
CodeMigration
Unit Test
RuntimeEnvironment
RuntimeMigration
Test Systems
DevelopmentEnvironment
RuntimeEnvironment
121212
Supported Migration Paths
Available paths:– WP 5.0.2.2+ Express WP 6.1
– WP 5.1.0.X (recommended 5.1.0.4+) WP 6.1
– Latest 2 v6.0 Portal Fixpacks
– v6.0.1.3. and v6.0.1.4
Migration is not a fixpack but a side by side operation, requiring a new install.
131313
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
Etc…
There are many components that must participate in the migration process
v5.x/v6.0 Portal Server v6.1 Portal Server
141414
What is Migrated Automatically
Migration scripts attempt to migrate the following resources– WMM configuration – WMM attributes and associated database tables
– Client configuration - Configuration information for all clients that are supported by WebSphere Portal.
– Themes and skins configuration - Configuration information for themes and skins for WebSphere Portal.
– Portlet Applications and portlets - Migration tasks are provided to facilitate deployment of the custom portlet applications.
– Portlet configurations – Customized portlet application configuration is migrated.
– Portal pages and places - The corresponding access control is migrated automatically with these artifacts.
– User customizations –these are customizable settings that are associated with portlet instances.
– Access control- Migration tasks migrate permissions page, porlet application, portlets, and user groups within the portal.
– JCR Content – WCM and PZN data
151515
Agenda
Overview
Migration
Preparing to Run Migration Scripts– Portal 6.1 Install
– Prepare Prior Portal
Migration Process Overview
Framework
Problem Determination
Common User Errors and Best Practices
161616
Portal 6.1 Install
Migration is side-by-side
Prepare WP 6.1 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
–PK69311–PK69096
– Validate Portal function
– Verify admin login
171717
Portal 6.1 Install, Continued Do not cluster 6.1 Portal
–Federate after migration
Validate Portal function–Ensure login is possible
–Set the WAS and Portal admin ID and passwords to match those from the previous version
Customizations to the v6.1 portal should be avoided, they will be removed or can cause problems during migration
–Start with fresh install
–Do not deploy portlets
–Do not create pages
–Do not change access control
–Do not delete pages
181818
Prepare Prior Portal Backup previous WebSphere Portal
–Good idea even though v5.x migration does not make any changes
–Required if you want to be guaranteed you can revert back to your v6.0 system
Install required fixes–Currently Available in <PortalServer_v61>/migration/fixes
– Known fixes at the time of GA are included in the v6.1 installed image
– PK64247 – Augments the customization domain for migrations from v6.0
191919
Prepare Prior Portal
For v5.x Portals Disable user access–Set the portal to be active for read only access, this prevents the loss of updates while migration is
executing.
If clustered, migrate from the primary node and prevent user access to that node during the execution of the portal-pre-upgrade task
Adjust HTTP server time out values to never time out, ideally the connection for the export process should use the internal WAS HTTP server port.
If using delegated user administration, 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, and specify the optional parameter to export groups when running the portal-pre-upgrade command.
202020
Agenda
Overview
Migration
Preparing for migration
Migration Process Overview– Migration Scenarios
– JCR Data Migration
– Validation
Framework
Problem Determination
Common User Errors and Best Practices
212121
Migration Scenarios
Portal configurations supported–Clustered
–Standalone
–Portal with process integration
Simplified over previous releases
High level perspective from v5.x–Export all portal artifacts
–Import all portal artifacts
High level perspective v6.0–Export required portal artifacts
–v6.0 includes direct reuse of database information in some portal domains
–Import required portal artifacts
222222
V6.10 Portal
V5.1 or v6.0.1.x Portal
Migration Scenarios, Cluster migration
V5.x or v6.0 DeploymentManager
Step 0Initial configuration
V6.10 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.10 Portal
V6.10 Portal
V6.10 Portal
V5.1 or v6.0.1.x Portal
V5.1 or v6.0.1.x Portal
V5.1 or v6.0.1.x Portal
232323
JCR Data Migration
Document Manager is no longer available in WebSphere Portal. Before migrating data, Web content previously stored as documents in a document library will need to be replaced with either file resource components or file resource elements stored in authoring templates, content items, sites or site areas
If document manager is in use, a solution to migrate PDM documents will become available in a future release of Quickr.
DB reuse when migrating from v6.0 eliminates the export/import of WCM and PZN data.
242424
Validation
Before clustering and resuming deployment, validate the migration
Verify the following components migrated correctly:– User attributes
– User groups roles access control
– Collaboration portlets
– Clients
– Pages and places
– User customizations
– Credential vault data
– Themes and skins
– Portlet applications
– Portlet configuration
– Virtual resources
Verify performance after clustering
Additional details, see the migration topic in the Portal v6.1 Infocenter.
252525
Agenda
Overview
Manual Migration
Preparing for migration
Migration Process Overview
Migration Scripts– Directory and file structure
– Commands
– Extended Migration Commands
– v5.1 Additional Components
– Filtering
– How migration works
Problem determination
Common User Errors and Best Practices
262626
Directory and file structure
The migration directory is located in <wp_root>/migration
Migration plugins live in <wp_root>/migration/components
272727
Commands Automated core migration tasks:
– portal-pre-upgrade – Executed against the source server– Run using the supplements CD if in a remote migration scenario– Run from the v6.1 installed image for same server migration– Generates a backup directory which contains the artifacts to move to v6.1
– Portal-post-upgrade – Executed against the target server– Imports the old configuration into v6.1
Migration is extendable, currently this extensibility framework is not available for customer usage. The documentation and support is not ready for general use. L2 or L3 may provide patches through the extensibility framework.
– Currently used by some components to provide IBM Portlet to JSR 168 conversion and to manage other changes in Portlets from release to release.
– Additional custom migration tasks can be plugged into the migration framework.
– Additional filtering can be added
282828
Extended Migration Commands Deployment manager security migration
– migrate-wmm-to-vmm – Executed on the primary node immediately after federation to restore security.
– Copy backup dir to DMgr host under the same path where it exists on the primary node
update-nodetypes– ConfigEngine task
– Use in the case where a “re-migration” of the JCR data is required
292929
V5.1 Additional Components - WCM Install WCM migration tool
– ConfigEngine configure-wcm-migration
Migrate all the WCM data– 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
303030
V5.1 Additional Components - PZN
1. Migrate from 5.1– WPmigrate migrate-pzn-50x
– WPmigrate migrate-pzn-51x
2. Migrate exported 5.1 data– WPmigrate migrate-pzn-svData-transform-51x
313131
How it works Migration from v5.x to v6.1
– Requires full export and import of all data
– Very similar to v5.x to v6.0 migration
Migration from v6.0 to v6.1– New approach which allows for DB sharing and DB reuse
– Significantly reduces down time some scenarios can be migrated with zero downtime
323232
Shutdown previous Portal Server
JCR
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
Community
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
How it works – DB Reuse approach
LDAP
Release
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
Install v6.1 portal
Execute Portal migration tasks
Move required v6.0 resources into the v6.1 portal
Connect to existinguser repository
Customization
LM,FB,Sync
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
Community
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
....
Release
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.
Resource
prod.
Resource
Resource
prod.
Resource 2
prod
Resource 3
Resource
prod.
Resource 2
prod.
Resource 2
prod
Resource 3
prod
Resource 3
Resource
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential
Integrity
Referential
Integrity
DBSchema
Resource 2
Resource x
Resource 1abc
Resource 2
Resource x
Resource 1abc
Weak References
....
Connect to previouscustomization, LM,FB,Sync,and copied JCRdomains
v6.0 portal
Copy JCR domain
DB transfer release and Community domains
JCR
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Action Set 2User @ MyPortal
Action Set 1Admin @ Content Node
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Portal
Portlets Content Nodes Templates
Wps.content.root
My Portal
Applications
…..
Resource
prod.Resource
prod.Resource
Resource
prod.Resource 2
prodResource 3
Resource
prod.Resource 2
prod.Resource 2
prodResource 3
prodResource 3
Resource
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1
....
Resource 3Resource 2
Resource yResource x
Resource 3Resource1 ....
valueResource 2
valueResource x
valueResource1
....
valueResource 2
valueResource x
valueResource1
Referential IntegrityReferential Integrity
DBSchema
Resource 2..
Resource x..
Resource 1abc
Resource 2..
Resource x..
Resource 1abc
Weak References
333333
Agenda
Overview
Manual Migration
Preparing for migration
Migration Process Overview
Migration Scripts
Problem determination– Log files
– Information to be Collected
Common User Errors and Best Practices
343434
Log files
Log files are created using the command line scripts
The logs created by the command line script help you debug migration process failures. The following log files are useful for debugging issues
– <wp_profile_root>/PortalServer/log/MigrationTrace.log – <wp_profile_root>/ConfigEngine/log/ConfigTrace.log
Log files may refer to other files created in the migration backup directory.– XmlAccess import result files
353535
Information to be Collected OS
– OS level
– Fix packs
Portal levels – Including fix pack and iFix levels for previous and v6 Portal
Log files:– <wp_root>/log/MigrationMessages.log
– <wp_root>/log/MigrationTrace.log
– <wp_root>/migrationwizard.log
– <wp_root>/migrationwizardlog.txt
All temporary work files and previous portal information used in the migration process. This includes the allout.xml, importAll.xml, template files, previous wpconfig.properties, etc…
– Instruct the user to zip the Portal backup directory or a subset of the backup directory
363636
Agenda
Overview
Manual Migration
Preparing for migration
Migration Process Overview
Migration Scripts
Problem determination
Common User Errors and Best Practices
– Limitations
– Common Errors
– Custom XmlAccess Migration
– Portal Resources
373737
Migration limitations Manual recreation of all process tasks required if the customer is using WBI. WBI ->
WPS conversion is not automatic. Limitation in the WPS product.– V5.1 Requires a re-write
– V6.0 If using a local process container the migration complexity is high
XmlAccess can not migrate large numbers of users– Export requires a significant amount of resources.
Admin Portal access control is not migrated.– Permissions on default admin portlets must be manually recreated
– Permissions on clones on non OOB admin pages do get migrated
– Some cloned admin portlets may require the manual setting of configuration parameters
Changes to admin pages must be manually recreated.– Includes additional portlets added to pages, themes, skins, etc…
– Admin page access needs to be recreated as well.
v5.10 transformations have been modified, there are manual steps required to fix the transformation.
There is no undo, the changes made during the migration process can not be automatically undone,
– Imperative that the user backs up their initial portal configuration if it is faster than a reinstall.
383838
Migration limitations Migration of portlets within EAR files requires the user to manually deploy the portlets
but not register them prior to executing the portal-post-upgrade migration command– Update the ear mapping file for custom deployment paths
Services and services settings are not migrated automatically.– Service jar files need to be manually redeployed
– service-settings must be manually re-created
Some wires may not be migrated– Private wires for instance
Search indexes must be recreated
Taglib for people awareness has been changed in v6.1, requires updating in older themes
– Not compatible with v5.1
– V6.0 taglib slower performance
MS SQL Server 2000 is not supported– v6.0 must be upgraded to use MS SQL Server 2005 prior to migrating
Customized migration, by default is not part of the migration framework.– The migration framework allows customization code to be plugged in.
393939
Common Errors and Best Practices Information in the infocenter is not read and understood before migration is
attempted.
All required pre-migration steps are not performed– Corrective service not applied to the previous Portal.
Attempting to connect through the HTTP server which times out and drops the connection.
– This problem may occur during the export and may manifest itself on the during import, the symptom is an allout.xml that is not a properly formatted xml file.
Improper WAS admin uid/pwd specified
Improper Portal admin uid/pwd specified
Database URL not in the proper format for portal-pre-upgraderelease.DbUrl=jdbc:db2://<your db server>:50000/wps60db:returnAlias=0;
Should be:
release.DbUrl=jdbc:db2://superman2.raleigh.ibm.com:50000/wps60db
404040
Common Errors and Best Practices (cont)
Current portal installation has not been verified.– User never attempted to log in
User is attempting to migrate into a clustered node, this is not supported
After federation of migrated node the security settings have disappeared– migrate-wmm-to-vmm task needs to be executed against deployment manager
Not enough memory is allocated to the process that is performing migration.
User resources not removed from portal when they have been removed from LDAP.
– Execute the clean users task to re-assign ownership
Users do not restart the v6.1 Portal after migration, migrated themes and skins or pages may not show up properly
Attempting to migrate Portal on a machine with limited resources or other servers running on them. Severe resource contention will cause failures, timeouts on DB or LDAP connections
414141
Common Errors and Best Practices (cont) Rational Application Developer
– Portal Toolkit v5/v6.0 projects must be migrated to a RAD which supports Portal v6.1 (TBD)– RAD can help with some manual portlet upgrade
Transfer LDAP users if needed– This is not recommended to be done before migration. The customer should migrate using the same user
repository. The user should verify the migrated portal, then change the LDAP repositories.– For migration from v6.0, special care must be taken to propagate the extID if users must be moved into a new
repository
Validate WMM configuration is valid before attempting migration– Ensure cross registry groups are not configured in WMM unless the backing registry supports this
configuration– Ensure base entries exist– Ensure LDAP server information is valid– Deploy required SSL certificates in the default trust store for v6.1
Values in the WmmVmmDBMigration.properties not configured correctly– Need to specify the full DN for the previous portal admin user and group– DB driver needs to be same as what is used by WAS– DB driver must be copied to AppServer/lib directory
Old and new Portal and WebSphere user ID must be the same– Short login name and password must be valid in both the old and new portal
Custom versions of OOB portlets fail– Different war file names can cause a conflict when doing an update
424242
Common Errors and Best Practices (cont) Custom content may require manual updates to get new function.
– Custom themes and skins – Custom themes from v5.0 Express will require modifications– Changes in Search will require manual modifications to themes– Change to people component components will require manual updates to themes– Manual modification is required to take advantage of the v6.1 features such as drag and
drop, fly out, context menus, etc…
– Custom portlets – C2A Portlets and Struts portlets may require updating– Most other portlets should run as is– If the customer wants to upgrade their portlets, it is recommended they migrate their
previous portal first then upgrade their portlets.
Custom xmlaccess scripts – XmlAccess is forward compatible.– If the customer has existing XmlAccess scripts they used to create their previous portal and
they do not wish to perform a full migration, they can use the XmlAccess script used to set up their previous portal.
Other manual steps– Rational Application Developer – Refer to the Portal and RAD infocenter for
migrating the development environment.
– Redeployment of custom services
434343
Common Errors and Best Practices (cont)
Most custom portlets run unchanged on WP v6, portlets built that take advantage of WMM API’s will need modification
Migrating Struts and C2A portlets require repackaging with updated jars– Details on this conversion is covered in the infocenter.
If using CredentialVaultService.getDefaultUserVaultSegmentId() API– Migrating the credential vault is covered in the infocenter.
– Change com.ibm.wps.util.ObjectId com.ibm.portal.ObjectId
Portlets deployed using the portal interfaces are automatically migrated
Migration scripts will install custom portlets
Pre-deployed portlets now only need to be installed on v6.1
444444
Common Errors and Best Practices (cont)
Modified admin portlets cause failures–If a modified admin portlet has been deployed in a previous version, manual steps
may be required.
Ensure DbSafe mode is not enabled when applying iFix PK64247
Ensure a backup is made for the <AppServer>/lib directory–Will be required to be restored if changes to the VMM DB repository configuration are needed
and SqlServer and DB2 z/OS are used
454545
Custom XmlAccess Script Migration
Use of the WebSphere Portal migration scripts is not required, existing XmlAccess scripts may be sufficient, provided certain conditions are met
–WMM UR is not in use
–No customizations are enabled
–No admin portlets are included in the deployment scripts
–No dependencies on OOB content,
–etc…
WebSphere Portal v5.x/v6.0 XML access scripts are fully compatible with WP 6.1–These scripts are compatible however the expected results after import may be unexpected. A
full export of a previous server and import of the export into a v6.1 portal may not work.
–Your v5.x/v6.0 XmlAccess scripts used to prime your previous portal will work on v6.1.
–LPID -> GUPID my be an issue. The use of the identification mapping service may be required to create unique object ID’s in the new Portal.
How migration handles domains for v5.x migrations:–The content is automatically stored in the default domain, core migration does not explicitly set
domain attributes
464646
Portal Resources
Best resource for migration commands
474747
Portal Resources
White papers for migration from v5.1 and v6.0– http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg27012698
WebSphere Portal Documentation– http://www-128.ibm.com/developerworks/websphere/zones/portal/proddoc.html
6.1 Information Center:– http://infocenters.lotus.com/help5/index.jsp (Preview)
Developerworks: WebSphere Portal Zone– http://www-106.ibm.com/developerworks/websphere/zones/portal/
Questions or concerns regarding the migration content in the WebSphere Portal 6.1 Information Center?
– Please contact Mary Carbonara (mary_carbonara@us.ibm.com, 617-693-7988) for further assistance
Migration Central - Support Web Site – http://www-01.ibm.com/support/docview.wss?
rs=688&context=SSHRKX&context=SS3JLV&context=SS3NNG&context=SSYJ99&context=SSRUWN&context=SS6JVW&q1=migration&uid=swg21296071&loc=en_US&cs=utf-8&lang=en
484848
Thank You
Questions & Answers
top related