When setting up SSL connections between Enterprise Managers and Agents or Standalone Agents and 3rd party products e.g. WebSphere MQ, problems can sometimes occur that require more detailed tracing. How can that tracing be generated?
The Java Secure Socket Extension (JSSE) for both Oracle/Sun & IBM has a built-in debug facility that can be enabled by adding "-Djavax.net.debug=all" to the JVM parameter list.
If the output does not appear in the relevant EM log or agent log file it may need to be captured by redirecting standard out & error to a separate file e.g.
java...-Djavax.net.debug=all > trace.out 2>&1
Oracle Java Documentation > Debugging SSL/TLS Connections
IBM SDK, Java Technology Edition 8.0.0 > Security Guide > IBMJSSE2 Provider > Troubleshooting > Debugging Utilities