Add tracing and logging for stand-alone clients

We can add tracing and logging to help analyze performance and diagnose problems.

This information applies to the following WebSphere Application Server stand-alone clients:

• Thin Client for JMS with WebSphere Application Server

• Thin Client for EJB with WebSphere Application Server

• Thin Client for JAX-WS with WebSphere Application Server

• Thin Client for JAX-RPC with WebSphere Application Server

• To enable trace, use either a long form or short form system property.

  Trace settings are determined from the system property values the first time that a WAS client is called. The trace settings are then fixed. Therefore, any subsequent changes to the system property settings do not change the trace settings that the WAS client uses.

• To enable First Failure Data Capture (FFDC), use either a long or short form system property.

  FFDC settings are determined from the system property values the first time that a WAS client performs an FFDC. The FFDC settings are then fixed. Therefore, any subsequent changes to the system property settings do not change the FFDC settings that the WAS client uses.

Subtopics

• Trace user interface for stand-alone clients
  To enable trace, we can either use a long form or a short form system property.

• First Failure Data Capture user interface for stand-alone clients
  To enable First Failure Data Capture (FFDC) output, we can either use a long or short form system property.

Related tasks

Use JMS to connect to a WAS default messaging provider messaging engine

Use JMS from a third party application server to interoperate with service integration resources