When upgrading WebSphere Process Server from 6.0.2 to 6.2, upgrade scripts hung during the deployment manager migration, in fact waiting for user input to add a digital certificate to trust store. Since upgrade app closed the stdin, I could not pass Y/N value.
Later found that actual problem is that I have another deployment manager running on the same box with WAS default ports, when migration scripts checking for the running WAS server it got a valid response from the running deployment manager causing a different path of execution in migration.
Things worked pretty smooth after I shut down other deployment manager and ran WBIPostUpgrade.sh script. So if you are planning for WebSphere Process Server upgrade and migrating deployment manager, make sure that you do not have another server running on the same machine with WAS default ports.
