After upgrade web sphere from version 6 to 8.5 agent is unable to connect to Application server

Document ID : KB000090452
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
After upgrade web sphere from version 6 to 8.5 agent is unable to connect to Application server
Resolution:

Symptoms

After upgrade websphere servers from version 6 to websphere 8.5, agent is unable to connect to application server 

Error message in the job:

The connection to the MBean Server could not be established: java.io.IOException: ADMC0016E: The system cannot create a SOAP connector to connect to host

Error message in the agent trace file:

Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty; targetException=java.lang.IllegalArgumentException: Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty]


Cause by the default setting of agent

in the INI file of the Agent: 

20140225/152821.296 - [WEBSPHERE] 

20140225/152821.296 - javax.net.ssl.trustStore=/opt/IBM/WebSphere/AppServer/profiles/Custom01/config/cells/PRDcell02/trust.p12 

20140225/152821.296 - javax.net.ssl.keyStore=/opt/IBM/WebSphere/AppServer/profiles/Custom01/config/cells/PRDcell02/key.p12 

20140225/152821.296 - javax.net.ssl.keyStoreType=PKCS12 

20140225/152821.296 - soapTimeout=43200 



Resolution

Since WebSphere version 7 and higher the values for javax.net.ssl.trustStore and javax.net.ssl.keyStore should be removed if the Agent is deployed as a web application. 

The Agent does not use the value javax.net.ssl.keyStoreType therefore this entry should also be removed.

and section of WEBSPHERE should have the following information

[WEBSPHERE] 

soapTimeout=43200 

It is  also important to use the value "websphere_soap" in the field "Initial Context Factory" of the Job.