Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Use JMS from stand-alone clients to interoperate with service integration resources
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 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.
- 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.
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