Post-migration activities

After migrating IBM® WebSphere® Portal, additional tasks may be needed depending on how you customized the source portal environment and which components you used.

  • Upgrading default themes
    When you migrate from previous version, Portal keeps the default themes for administration at the previous version you migrated from. In order to use the themes for the current version, you need to use the ConfigEngine.
  • Enabling remote rendering portlet themes
    After you completed migration, some additional steps are required to fully enable the remote rendering portlet themes.
  • Updating web content after migration
    After you migrated to Version 8.0 and successfully tested it, update your Version 8.0 web content with the latest version data from your source environment.
  • Enabling JCR text search indexing
    Before beginning with migration, you disabled JCR text search indexing. Now that the migration is complete, you need to re-enable JCR text search indexing.
  • Create JCR search collection
    After completing migration, create the JCR search collection.
  • Enabling automatic synchronization
    Before starting with migration, you disabled the automatic synchronization to avoid nodes getting out of sync. Now that you have completed migration, it is safe to enable this feature again.
  • Migration consideration for Tivoli Access Manager integration
    The IBM WebSphere Portal migration process migrates the security configurations. However, there is no provision for the automatic migration of any junction definitions that exist for the previous version of WebSphere Portal in WebSEAL. You must replace the old junction definitions with the new virtual host junction definitions.
  • Virtual Portal post migration steps
    If you configured WebSphere Portal to use virtual portal, there are some additional steps needed to complete the migration.
  • Mashup integration post migration steps
    Mashup integration feature was removed in WebSphere Portal Version 8.0. This step is an optional if you actively used this feature in previous releases and you still want to continue using it in portal Version 8.0. If that is the case, then you need to manually enable mashup integration after migration.
  • Blogs and wikis post migration steps
    After migrating from WebSphere Portal Version 7.0 to Version 8.0, you must run a configuration task to update the presentation templates used by blogs and wikis to apply the correct styling. You must run this task for content in your blogs and wikis to render properly.
  • Updating custom theme Dojo references
    The default Dojo context root in WebSphere Portal is /WpsContextRoot/portal_dojo. You can find the value of WpsContextRoot in wp_profile_root/ConfigEngine/properties/wkplc.properties.
  • Analytics post migration steps
    If you use site analytics on your migrated WebSphere Portal, you need to create the analytics tag root label.
  • Portlets no longer available
    Some portlets that used to be available on previous releases of WebSphere Portal are no longer including in Version 8.0. These portlets are not migrated as part of the WebSphere Portal migration process.
  • Setting up Tag Center
    If your target environment does not have a Tag Center page, run the following command to create one along with all the associated portlets.
  • Removing Person Tag hidden pages
    Remove Person Tag hidden pages from migrated environments where Search for Portal Site was previously configured.
  • Themes on secondary clusters
    After completing migration of multiple clusters, secondary clusters do not have their original themes configured correctly. You must update the primary node on all secondary clusters.
  • Upgrading secondary navigation that displays consecutive labels
    The secondary navigation is dynamic, and shows only two levels of navigation at a time. When a page on the last level of navigation is selected, only that level of navigation is displayed. It is possible to select a page where both the parent level of navigation and the grandparent level of navigation are both labels. In this case, the sibling navigation for the parent level is not accessible.
  • Sending parameters to the JSR 286-based Web Content Viewer portlet from external applications
    If you converted portlets from IBM Portal API viewer-based to JSR-286 viewer-based, and you are sending parameters to your portlets from external applications, then you need to update the method for sending portlets.
  • Parent topic: Migrating
    • Related concepts:
  • Migration overview
  • Migrating Portal on AIX IBM i Linux Solaris Windows
  • Migrating Portal on z/OS
    • Related tasks:
  • Setting up the target environment
  • Deploying new functionality in a migrated portal
    • Related reference:
  • Deploying new functionality in a migrated portal on z/OS

    • Related information