+

Search Tips   |   Advanced Search

Portal, V6.1

 

Run migration tasks for composite applications

Use the WPMigrate script to migrate composite applications from IBM WebSphere Portal v6.1.3 to V6.1.x. When you migrate a portal environment using the portal-pre-upgrade task and the portal-post-upgrade task, composite applications that have been enabled for backup are also migrated. You can also choose to migrate composite applications independently of the core portal migration by running the migrate-ai-export and migrate-ai-import tasks.

Prerequisites

Preparing to migrate composite applications

To migrate composite applications independently of the core portal migration tasks, follow these steps on the source and target server machines of the portal environment:

Always use the forward slash (/) as the path delimiter when specifying the values of the parameters DbackupDirectory and DcurrentPortalDirectory regardless of the operating system. If you fail to do this, the WPmigrate.bat migrate-ai-export task will indicate timeouts.

If you are running the composite application migration tasks on two different server machines and the migrate-ai-export does not work properly the first time, run this task again from the CD_root/migration/portal_migration directory on the WAS ND V6.1 Supplements CD. This CD comes with WebSphere Portal and can be used on either Windows or UNIX. Then run the migrate-ai-import task on the WebSphere Portal V6.1.0 server machine.

Run WPmigrate with the portal-pre-upgrade task .

  1. To back up and export the composite application artifacts and data of the source portal environment, run the following task:

    Windows: WPmigrate.bat migrate-ai-export -DbackupDirectory=dirname_exported_application_data -DcurrentPortalDirectory=dirname_version6013_portal_server

    UNIX: ./WPmigrate.sh migrate-ai-export -DbackupDirectory=dirname_exported_application_data -DcurrentPortalDirectory=dirname_version6013_portal_server

    i5/OS: WPmigrate.sh migrate-ai-export -DbackupDirectory=dirname_exported_application_data -DcurrentPortalDirectory=dirname_version6013_portal_server

  2. To import the backed-up artifacts and data that you exported in Step 1 into the target portal environment, run the following task:

    Windows: WPmigrate.bat migrate-ai-import -DbackupDirectory=dirname_exported_application_data

    UNIX: ./WPmigrate.sh migrate-ai-import -DbackupDirectory=dirname_exported_application_data

    i5/OS: WPmigrate.sh migrate-ai-import -DbackupDirectory=dirname_exported_application_data

  3. After you complete the previous steps, run the script that resolves references to application categories and template names in the business rules that are defined for application policies. If you do not run the $Application migratepznrules script and you have defined policies for composite applications in your source environment, the application policies will not work in the target environment because the policy rules defined for composite applications will not be available. The script can be invoked multiple times and will only modify policy rules if it can resolve references to application categories and template names. Only policy rules for composite applications are modified; other business rules defined and controlled by the Personalization component are not affected.

    1. Change to the directory portal_server_root/bin and invoke the Portal Scripting Interface for your operating system using the appropriate command and administrator credentials:

      Windows: wpscript.bat -user portal_administrator_userID -password portal_administrator_password

      UNIX: ./wpscript.sh -user portal_administrator_userID -password portal_administrator_password

      i5/OS: wpscript.sh -user portal_administrator_userID -password portal_administrator_password

    2. Run the following scripts:

      $Portal login portal_administrator_userID portal_administrator_password

      $Application migratepznrules

    3. When you have finished running the scripts, log out:

      $Portal logout

  4. When you have finished migrating composite applications, verify the expected results:

    1. Check the migration log.

    2. Open the Template Library and the Application Library in the target environment (the upgraded portal site) and verify that all composite application artifacts and data from the source environment are available and working as expected.

    3. If you discover that some application artifacts or data did not migrate completely or properly, restore the artifacts or data from the source environment by either copying resources or resetting properties. For example, applications marked as Favorites in the source environment lose this designation when they are migrated. You will need to mark applications as Favorites again in the upgrade portal environment.

 

Parent topic

Migrating composite applications

 

Previous topic:

Preparing to migrate composite applications

 

Related concepts


Work with the Portal Scripting Interface

 

Related tasks


Migrating product configuration
Exporting configuration for migration to a remote machine