Deploying new functionality in a migrated portal

The migration process collects configuration data and applications from an earlier installed version of IBM® WebSphere® Portal and merges them into the newer installed version so that the new environment is identical to the earlier environment. Taking advantage of new functionality that was not available in the earlier portal requires additional attention after migration is complete.

Before you begin

About this task

  • Updating page templates after migration
    With Version 8.0, there are several new features related to templates used to create portal pages. Some of these features cannot be automatically configured by the migration process. To fully support the page template features in Version 8.0, you must perform additional configuration manually.
  • Enabling impersonation
    If you migrate from an earlier release that did not support user impersonation (for example, Version 6.1.0.1), the migration process re-creates the earlier portal environment in Version 8.0 without enabling impersonation. Enabling impersonation in the migrated portal requires completing additional steps that update the master configuration and the appropriate users' access. For information and instructions, see the related links.
  • Enabling new Web Content Manager features
    You might need to update your old web content to take advantage of the new Web Content Manager features.
  • Enabling managed pages after migration
    After migration, you must manually enable support for managed pages. Without managed pages support, some features like the project menu are not available on the migrated server.
  • Updating blog and wiki templates after migration
    Perform the following steps to manually update the blog and wiki templates after migration.
  • Enabling sample web content template items after migration
    The sample web content template items are not installed by default during migration. This sample content includes examples of web content template pages and predefined portlets that you can add to pages to render content. You can add these features manually after migration.
  • Enabling new functionality in the Person menu
    Migrating from an earlier version of IBM WebSphere Portal does not upgrade the Person Card. To take advantage of new Person Card functionality that was introduced in Version 7.0, you must complete additional steps after migration is complete.
  • Moving hidden pages
    Portal scripts create hidden pages which can clutter the page topology, making it difficult for users to find the page they want, and also slow down portal performance. To clean up the page topology and ensure faster runtime performance, administrators can move these hidden pages to a different location after completing migration to IBM WebSphere Portal Version 8.0.
  • Enabling new functionality in migrated themes
    You can enable some key new functionality, such as a later version of Dojo, after your Page Builder-based and Portal 7.0.0.2-based themes are migrated to a WebSphere Portal 8.0 server.

What to do next

  • 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
  • Post-migration activities
    • Related reference:
  • Deploying new functionality in a migrated portal on z/OS

    • Related information