Portal V7.0 cluster: Upgrading the node profiles

To migrate properties, upgrade database domains, and apply other updates that are needed to bring the node profiles to the latest level, run the upgrade-profile task on the primary node and the secondary nodes.

Before you begin, make sure the Deployment Manager and node agents are running.

Also verify in the Deployment Manager console that all nodes are in sync before upgrading the node profiles. If the nodes are not in sync then synchronize them at this time.

Open a command prompt on the primary node.
Change to the wp_profile_root/ConfigEngine directory and then run the following command:
- Windows: ConfigEngine.bat upgrade-profile -DWasPassword=WasAdminPwd -DPortalAdminPwd=PortalAdminPwd
- Linux : ./ConfigEngine.sh upgrade-profile -DWasPassword=WasAdminPwd -DPortalAdminPwd=PortalAdminPwd
- IBM® i: ConfigEngine.sh upgrade-profile -DWasPassword=WasAdminPwd -DPortalAdminPwd=PortalAdminPwd
Important:
- If you updated the database schemas manually, you must include the parameter -DDbSafeMode=true. For example: ConfigEngine.bat upgrade-profile -DWasPassword=WasAdminPwd -DPortalAdminPwd=PortalAdminPwd -DDbSafeMode=true
  Do not specify this parameter if you want the migration process to update the database schemas for you.
- If you are migrating a large amount of content in the JCR repository (for example, Web Content Manager data), include the parameter -Dwcm.transactionTimeout=timeout_value. A value of at least 1200 is recommended and has been used successfully in IBM testing. For example: ConfigEngine.bat upgrade-profile -DWasPassword=WasAdminPwd -DPortalAdminPwd=PortalAdminPwd -Dwcm.transactionTimeout=1200.
Repeat the previous step on each secondary node.
Verify the migrated portal.
1. Start the portal server, if it is not running.
2. Open a web browser and enter the URL for the migrated portal.