+

Search Tips   |   Advanced Search

Portal V7.0 cluster: Upgrade the node profiles


Run the upgrade-profile task to upgrade the profile and copied databases to v8. Pages are not modified.

  1. Start dmgr and node agents

  2. In dmgr console, synchronize all nodes.

  3. On the primary node.

    cd WP_PROFILE/ConfigEngine 
    ./ConfigEngine.sh upgrade-profile  \
                      -DWasPassword=WasAdminPwd  \
                      -DPortalAdminPwd=PortalAdminPwd  
    

    If you updated the database schemas manually, include the parameter -DDbSafeMode=true...

    ConfigEngine.sh 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 we are migrating a large amount of content in the JCR repository (WCM data), include the parameter -Dwcm.transactionTimeout=1200

    ConfigEngine.bat upgrade-profile \
                     -DWasPassword=WasAdminPwd \
                     -DPortalAdminPwd=PortalAdminPwd \
                     -Dwcm.transactionTimeout=1200
    

  4. Repeat the previous step on each secondary node.

  5. Verify the migrated portal.

    1. Start the portal server

    2. Open a web browser and enter the URL for the migrated portal.

If upgrade-profile fails, we can restart using:

For example:

For troubleshooting, use -DskipCleanup="true" to preserve work folder.

If using both parameters, clean contents of...


Parent: Portal V7.0 clustered environment
Related:
Plan for migration: Security