IBM Support

Configuration Manager cannot populate Application Server Cell field

Troubleshooting


Problem

When creating a new installation profile, FileNet Content Engine Configuration Manager fails to populate the Application Server Cell field and throws an error.

Symptom

Configuration manager throws the following error when populating Application Server Cell field:

An error occurred while retrieving the cell name information. java.lang.Exception: An SSL handshake failure occurred from a secure client. Add the server's SSL signer to the client's trust store.

or


Verify your application server port number and confirm that the application server is running

Cause

Scenario 1:

When the Application server SOAP port is set to a port that is being used by another WebSphere instance, it will give the error: "An SSL handshake failure occurred from a secure client. Add the server's SSL signer to the client's trust store." An example is given below: port 8879 is currently used by a WebSphere Deployment Manager instance, but it is mistakenly specified here as SOAP port in Configuration Manager. As a result, you'll will receive an error "An SSL handshake failure occurred from a secure client. Add the server's SSL signer to the client's trust store."




Scenario 2:

If the SOAP port is not being used by another WebSphere instance, it will give the error: "Verify your application server port number and confirm that the application server is running."

To fix: this problem, enter the correct SOAP port that corresponds to the specified Application Server Instance. To find the correct SOAP port, login to WebSphere console, access Application servers -> [server name] -> Ports (screenshot below), and use the port number of the SOAP_CONNECTOR_ADDRESS.


Note: The An "SSL handshake failure occurred from a secure client. Add the server's SSL signer to the client's trust store." error persists until CMUI is restarted.

Note: This could also occur if SSL is not configured correctly. Please refer to P8 documentation to configure SSL.

Resolving The Problem

  1. Access the IBM Websphere console
  2. Application Servers
  3. Server Name
  4. Ports
  5. Note the SOAP_CONNECTOR_ADDRESS
  6. Verify that port number is not being used by another instance
  7. Verify the correct port is entered in the Application server SOAP port:

[{"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Content Engine","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"4.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21427420

Page Feedback