Search Tips   |   Advanced Search

Portal V6.1.x on application server V6.1 cluster: Upgrade the node profiles

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

Before beginning, make sure the dmgr and node agents are running.

Also verify in the dmgr 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.

On the primary node.

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

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

  • Repeat the previous step on each secondary node.

  • Verify the migrated portal.

    1. Start the portal server

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

      The migrated portal URL takes this form:


      For example, if the original portal URL is http://www.example.com:10040/wps/portal, the URL for the migrated portal is...


      During migration, the following changes are made to wkplc.properties stored in the WP_PROFILE/ConfigEngine/properties directory:

      • WpsContextRootOriginal is set to the original value of the context root before migration was performed. This property is for reference only and is not used by the migrated portal.

      • WpsContextRoot property is set to the migrated value original-context-root_migrated (for example, wps_migrated).

    Troubleshooting tip: During migration, applications might not synchronize correctly after being redeployed. This is typically due to a problem with how the LTPA keys are regenerated. If this occurs when the upgrade-profile task fails, the SystemOut.log file shows the Portal version still at the V6.1.x level, and the SystemOut.log file on the node agent shows errors indicating the failed synchronization:

    6/22/10 12:10:40:684 EDT] 00000051 NodeSync      E   
    ADMS0005E: The system is unable to generate synchronization request: 
    javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getRepositoryEpoch operation on 
    ConfigRepository MBean because of insufficient or empty credentials.
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:933)
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplateOnce(SOAPConnectorClient.java:901)
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:667)
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:657)
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:643)
     at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:465)
     at $Proxy2.invoke(Unknown Source)
     at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:224)
     at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:381)
     at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:237)
     at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)
     at java.lang.Thread.run(Thread.java:736)

    To correct the problem, refer to Technote 1405907, and then run the upgrade-profile task again.

    Parent: Portal V6.1.x on application server V6.1: clustered environment
    Plan for migration: Security

    Technote 1405907 - Managed node fails to synchronize