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

Troubleshooting and Limitations – WebLogic Discovery

Troubleshooting

  • Problem: When running the WebLogic 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 WebLogic server and configure UCMDB JMX credentials; do not use an SSL connection

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

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

Limitations

  • For Weblogic versions 8.x and earlier, DFM discovers only those domains created by the WebLogic Configuration Wizard.

  • For versions earlier than WebLogic 9, the JEE WebLogic by Shell job can run only on admin server hosts. For WebLogic version 9 or later, the job can run also on hosts that contain managed nodes only.

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

  • The WebLogic installation includes an example that is filtered out by default. You can remove the filter in the weblogic_by_shell.py Jython script. Look for WL_EXAMPLE_DOMAINS = 'medrec'.