Migrate a stand-alone portal that runs on a V6.1 application server
Migrate an WebSphere Portal V6.1.x stand-alone on IBM WAS V6.1 involves the high-level steps outlined here.
1. Migrate the portal's V6.1 application server profile
The steps that you use to migrate the IBM WAS portal profile vary depending on whether the target portal is on the same server as the source portal or on a remote server.
2. Use copies of source database domains to minimize downtime
When you migrate from IBM WebSphere Portal V6.1.x on IBM WAS V6.1, the recommended way to keep the earlier portal environment in production and reduce the amount of downtime during migration is to copy the earlier portal server JCR and Release domains, connect to the domain copies, and then update the new portal server using the domain copies. The process of connecting to the domain copies must be done after you upgrade the ConfigEngine tool but before you upgrade the V6.1.x profile.
3. Retaining custom table spaces
If a database domain in the earlier portal server uses assigned custom table spaces that you want to retain for use on the new portal server (instead of using the default table spaces), you need to update the table space property file and the index space property file for the database table. Complete these updates only after you have upgraded the ConfigEngine tool.
4. Update the database schemas
Database schemas that you used with the earlier source portal need to be updated for use with the new target portal. The migration process handles these updates for you automatically. However, if the portal uses IBM DB2 Universal Database™ for z/OSas the backend repository, you can choose to view the SQL scripts that the migration process uses to update the database schemas.
5. Update the configured database driver for DB2 for z/OS
If WebSphere Portal is configured to use IBM DB2 Universal Database for z/OS, you need to update wkplc_dbdomain.properties to specify a type 4 database driver and then ensure that WebSphere Portal uses the new driver.
6. Upgrading the V6.1.x profile
To migrate properties, upgrade database domains, and apply other updates that are needed to bring the profile to the V7 level, run the upgrade-profile task.
7. V6.1 Web content post migration steps
Once you have completed the WebSphere Portal migration steps, you need to perform these additional steps to complete web content migration.
8. Configure resource management with site management
To ensure that the portal can retrieve metadata information for resource management on remote systems after migration, configure the Resource Manager portlet with information about the remote system and the settings used to handle communication with the system.
9. Update custom themes and skins for hardcoded context root references
If you have developed custom themes or skins that contain hardcoded references to the portal's context root, this can cause problems if the context root is changed. This is particularly an issue after migration because the context root is modified during migration, causing hardcoded references to break. Rather than modifying custom themes and skins manually each time you change the context root, you can update themes and skins to remove the hardcoded references and instead use dynamic references that work properly regardless of the context root.
Parent
Migrate V6.1.x on a V6.1 application server
Plan checklist: V6.1.x portal on a V6.1 application server
Related tasks
Premigration tasks
Migrate search components from V6.1
Migrate a V6.1.x clustered portal