Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Troubleshoot Client applications
Add tracing and logging for stand-alone clients
We can add tracing and logging to help analyze performance and diagnose problems with stand-alone clients. This information applies to the following WAS stand-alone clients:
- Thin Client for JMS with WAS
- Thin Client for EJB with WAS
- Thin Client for JAX-WS with WAS
- Thin Client for JAX-RPC with WAS
Procedure
- 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. For further information, see the information on the trace user interface for stand-alone clients.
- 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. For further information, see the information on the First Failure Data Capture user interface for stand-alone clients.
Trace user interface for stand-alone clients
First Failure Data Capture user interface for stand-alone clients