Migrate customized resources - WebSphere Portal v6.0
Some migration steps are optional depending on what customized resources you had in the previous version of IBM WebSphere Portal. You only need to migrate those resources that are relevant to the environment. Choose the following relevant customized resources to migrate:
- Migrate the themes and skins if you want to use new functionality with the existing themes and skins
- Recreate the Portal service configuration
- Migrate portlets using one of the following two methods:
- Copy the .war files into...
portal_server_root/installableApps
- Install the portlets before performing the migration.
- Migrate cooperative portlets that use IBM Portlet API
The term cooperative portlets refers to the capability of portlets on a page to interact with each other by sharing information. One or more cooperative portlets on a portal page can automatically react to changes from a source portlet triggered by an action or event in the source portlet. Portlets that are targets of the event can react so that users are not required to make repetitive changes or actions in other portlets on the page. This provides a coordinated and consistent behavior between the portlets on the page and enhances users' overall experience. Cooperation between source and target portlets is facilitated by a WebSphere Portal runtime entity called the property broker. Portlets on a page can cooperate in this way even if they were developed independently, without the programmer's awareness of the existence of the other cooperative portlets.
- Migrate portlets built with Struts Portlet Framework
- Migrate business process applications
If you have business process applications developed for previous versions of the portal, make changes to the business process and portlets.
Parent topic:
Migrating