To enable trace for the WebSphere Application Server classes
in a client application, add the system properties shown in the following
example to the startup script or command of the client application. The location
of the output and the classes and detail included in the trace follow the
same rules as for adding trace to WebSphere Application Servers. For
example, trace the stand-alone client application program named com.ibm.sample.MyClientProgram,
enter the following command: java -DtraceSettingsFile=MyTraceSettings.properties
-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager
-Djava.util.logging.configureByServer=true com.ibm.samples.MyClientProgram
The file identified by file
name must be a properties file placed in the class path of the application
client or stand-alone process. You must create a trace properties file by
copying the app_server_root/properties/TraceSettings.properties file
to the same directory as your client application Java archive (JAR) file
You cannot
use the -DtraceSettingsFile=TraceSettings.properties property
to enable tracing of the ORB component for thin clients. ORB tracing output
for thin clients can be directed by setting com.ibm.CORBA.Debug.Output
= debugOutputFilename parameter in the command line.
The
java.util.logging.manager and java.util.logging.configureByServer system properties
configure Java logging to use a WebSphere Application Server-specific
LogManager class and to use the configuration from the file specified by the
traceSettingsFile property. The default Java Logging properties file, located in
the Java SE
Runtime Environment 6 (JRE6), will not be applied.