Last updated on OCTOBER 03, 2011
Applies to:Oracle Communications ASAP - Version: 5.2.4
Information in this document applies to any platform.
ASAP 5.2.4 PatchSet 6 is not deploying correctly to a managed WebLogic server because the installer is getting mixed up between the admin and managed servers.
This was a normal installation, where the provided installer was executed after being invoked through Exceed. Weblogic user Name & passwords were provided when prompted in the pop up window.
From the drop down of Weblogic Servers, the Managed Server was chosen.
The installer went on progressing fine and at the end, it threw the following exception.
IOException Caught. Check stacktrace of exception for more details: Unable to resolve 'weblogic.management.mbeanservers.edit'. Resolved 'weblogic.management.mbeanservers'
Exiting Application and closing open connection
Unable to connect to 't3://wlsAsapMngdA1.sup.corp.telenet.be:8401': Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms