Migrate Portal on AIX IBM i Linux Solaris Windows

Remove custom JVM properties

In WebSphere Portal Version 6.1.x, some custom JVM properties were introduced to improve performance. Since v7.0, these custom properties are no longer needed and are unavailable, hence they need to be removed before migrating.

The custom JVM property...

javax.xml.transform.TransformerFactory

...must be removed before migrating to WebSphere Portal v8.0. This custom JVM property is pointing to a class that no longer exists. If the property is not removed, the WebSphere Portal will not start after migration.

To remove, log in to the WAS admin console and go to...

Server | Application servers | servername | Server Infrastructure | Java and Process Management | Process Definition | Additional Properties | Java Virtual Machine | Additional Properties | Custom Properties

Find the javax.xml.transform.TransformerFactory property and remove it.

If the source environment is clustered, repeat these steps for each node in the cluster.

If we are migrating from v7.x, this property should not be configured.

Migrate WebSphere Portal Server to Enable or Extend versions

1. Install binary only WebSphere Portal v8.0 Enable or Extend

2. Run WasPreMigration and WasPostMigration.

3. Upgrade the ConfigEngine...

    
   upgradeConfigEngine.sh wp_profile  \
                          -conntype SOAP  \
                          -WasRemoteHostName host_name  \
                          -WasSoapPort 10025  \
                          -user wpsadmin  \
                          -password wpsadmin  \
                          -LocalHostName host_name
   

4. Upgrade the profile...
   ./ConfigEngine.sh upgrade-profile

   To include the deployment of WCM into the migration, specify...

   -DUpgradeServerToContent=true

   ...on the upgrade-profile call. This parameter allows the Web Content Manager to be displayed.

   If you chose not to do the full upgrade at this time to include the Web Content Manager. We can do it at any time later by running...

   ConfigEngine.sh upgrade-server-to-content-migration -DUpgradeServerToContent=true

Migrate from WebSphere Portal V6.1.x on a V6.1 application server

When you migrate from IBM WebSphere Portal V6.1.x on IBM WAS V6.1, we can migrate either a standalone, single server or a clustered deployment with nodes distributed across multiple servers.

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal.

When running migration commands, execute only one command at a time.

See

1. Migrate search components
2. stand-alone environment
3. clustered environment
4. Updating portlets URL
5. Update custom themes and skins to remove hardcoded context root references

Migrate from WebSphere Portal V6.1.x on a V7 application server

When you migrate from IBM WebSphere Portal V6.1.x on IBM WAS V7.0, we can migrate either a standalone, single server or a clustered deployment with nodes distributed across multiple servers.

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal.

When running migration commands, execute only one command at a time.

• Prepare the source environment
• Migrate search components
• Stand-alone environment
• Clustered environment
• Updating portlets URL
• Update themes and skins with hardcoded context root references

Migrate from WebSphere Portal V7.0

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal.

Migration tasks...

1. Prepare the source environment
2. Migrate search components
3. Stand-alone environment
4. Clustered environment
5. Update portlets URL

Deploy 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.

1. Update page templates after migration
2. Enable impersonation
3. Enable new Web Content Manager features
4. Enable managed pages after migration
5. Update blog and wiki templates after migration
6. Enable sample web content template items after migration
7. Enable new functionality in the Person menu
8. Move hidden pages
9. Enable new functionality in migrated themes

Parent: Migrate

See also

Migration overview
Set up the target environment
Post-migration activities

Remove custom JVM properties

In WebSphere Portal Version 6.1.x, some custom JVM properties were introduced to improve performance. Since v7.0, these custom properties are no longer needed and are unavailable, hence they need to be removed before migrating.

The custom JVM property...

javax.xml.transform.TransformerFactory

...must be removed before migrating to WebSphere Portal v8.0. This custom JVM property is pointing to a class that no longer exists. If the property is not removed, the WebSphere Portal will not start after migration.

To remove, log in to the WAS admin console and go to...

Server | Application servers | servername | Server Infrastructure | Java and Process Management | Process Definition | Additional Properties | Java Virtual Machine | Additional Properties | Custom Properties

Find the javax.xml.transform.TransformerFactory property and remove it.

If the source environment is clustered, repeat these steps for each node in the cluster.

If we are migrating from v7.x, this property should not be configured.

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows

Migrate WebSphere Portal Server to Enable or Extend versions

We can migrate from a source WebSphere Portal Server installation to a target WebSphere Portal v8.0 Enable or Extend.

1. Install binary only WebSphere Portal v8.0 Enable or Extend

2. Run WasPreMigration and WasPostMigration the way you typically would for any migration.

3. Run...
   upgradeConfigEngine.sh wp_profile -conntype SOAP -WasRemoteHostName host_name -WasSoapPort 10025 -user wpsadmin -password wpsadmin -LocalHostName host_name

4. Upgrade the profile...
   ./ConfigEngine.sh upgrade-profile

   To include the deployment of WCM into the migration, specify...

   -DUpgradeServerToContent=true

   ...on the upgrade-profile call. This parameter allows the Web Content Manager to be displayed.

   If you chose not to do the full upgrade at this time to include the Web Content Manager. We can do it at any time later by running...

   ConfigEngine.sh upgrade-server-to-content-migration -DUpgradeServerToContent=true

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows

Migrate from WebSphere Portal V6.1.x on a V6.1 application server

When you migrate from IBM WebSphere Portal V6.1.x on IBM WAS V6.1, we can migrate either a standalone, single server or a clustered deployment with nodes distributed across multiple servers.

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal.

When running migration commands, execute only one command at a time.

See

1. Prepare the source environment
   
2. Migrate search components
   
3. stand-alone environment
   
4. clustered environment
   
5. Updating portlets URL
   
6. Update custom themes and skins to remove hardcoded context root references
   

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows

Migrate from WebSphere Portal V6.1.x on a V7 application server

When you migrate from IBM WebSphere Portal V6.1.x on IBM WAS V7.0, we can migrate either a standalone, single server or a clustered deployment with nodes distributed across multiple servers.

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal.

For z/OS only. To migrate a stand-alone federated environment, an environment with one cell and two nodes, follow the instructions for migrating a clustered environment.

When running migration commands, execute only one command at a time.

• Prepare the source environment
• Migrate search components
• Stand-alone environment
• Clustered environment
• Updating portlets URL
• Update themes and skins with hardcoded context root references

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows

Migrate from WebSphere Portal V7.0

When installing the new version of portal, use the same OS user with equivalent access rights used to install the earlier portal. For z/OS only. To migrate a stand-alone federated environment, an environment with one cell and two nodes, follow the instructions for migrating a clustered environment. When running migration commands, execute only one command at a time.

Migration tasks...

1. Prepare the source environment
   
2. Migrate search components
   
3. Stand-alone environment
   
4. Clustered environment
   
5. Update portlets URL
   

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows

Deploy 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.

1. Update page templates after migration
2. Enable impersonation
3. Enable new Web Content Manager features
4. Enable managed pages after migration
5. Update blog and wiki templates after migration
6. Enable sample web content template items after migration
7. Enable new functionality in the Person menu
8. Move hidden pages
9. Enable new functionality in migrated themes

Parent: Migrate Portal on AIX IBM i Linux Solaris Windows