PK71761; 7.0: Migration of deployment manager fails to stop active dmgr

Download Description

PK71761 resolves the following problem:

ERROR DESCRIPTION:?
In secure migrations to v7, a signer exchange prompt may appear in the logs or trace during the migration when the WASPostUpgrade process attempts to stop the running dmgr process. This prompt cannot be responded to and so the stop action fails to stop the old dmgr process.

LOCAL FIX:?
Stop the active dmgr process prior to attempting WASPostUpgrade, or perform the dmgr migration specifying the option "-keepDmgrEnabled true", to keep the previous release deployment manager enabled.

PROBLEM SUMMARY:?

USERS AFFECTED:
IBM® WebSphere® Application Server Migration Tools users using Network Deployment

PROBLEM DESCRIPTION:
Migration cannot find the correct SSL keys when trying to stop a running deployment manager that is being migrated.

RECOMMENDATION:
Apply this fix, or stop the old deployment manager process, or run the migration specifying the -keepDmgrEnabled true option

The runtime tools cache the V7 autogenerated default keystores early in WASPostUpgrade processing. This cache is not updated during the migration, so the incorrect keys are located when the WASPostUpgrade tool attempts to stop the running deployment manager process. This will only occur if the original configuration uses the default keystores, and those keystores match the names used by the v7 autogenerated default keystores. This case occurs for customers using default *.p12 keystores in v6.1 migrating to v7.

PROBLEM CONCLUSION:?
The migration has been updated to flush the keystore cache prior to connecting to the deployment manager process so the migrated keystores will be used.

The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1.

Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980