Discovery > Discovery Modules > Middleware > Java EE Application Servers > WebSphere Discovery > Troubleshooting and Limitations – WebSphere Discovery

Troubleshooting and Limitations – WebSphere Discovery

This section describes troubleshooting and limitations for WebSphere discovery.

Troubleshooting

  • Problem: When running the Websphere by JMX job, using the SSL protocol, and the UCMDB server and Data Flow Probe are connected using the SSL protocol, the job is unable to connect to the target node.

    The following are alternative solutions:

    Solution 1: Configure an HTTP connection between UCMDB server and the Data Flow Probe.

    Solution 2: Allow a non SSL connection to the Websphere server and configure UCMDB JMX credentials; do not use an SSL connection

    Solution 3: Update the parameter remoteJVMArgs of the jobs (JEE WebSphere Connections by JMX job and JEE WebSphere by Shell or JMX job) by adding the following argument:

    Djavax.net.ssl.trustStore=..\runtime\probeManager\discoveryResources
    \j2ee\websphere\UCMDB_store.jks

Limitations

  • If DFM finds two cells with the same name on the same host, only one cell configuration (j2eedomain topology) is reported.

  • EJB and Web Service CIs are not discovered.

  • DFM can discover a J2EE application only when its .ear file is unzipped to a folder.

  • A job (script) works with a certificate in jks* key format only.