InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.2: WebSphere Control Program (wscp) >
6.6.0.2.2.3: Advanced usage of wscp >
6.6.0.2.2.3.7: Tracing the administrative server, application servers, and the wscp client

6.6.0.2.2.3.7: Tracing the administrative server, application servers, and the wscp client

Use either of the following methods to enable tracing for a wscp client:

  • Set trace properties (on the Java command line or in the .wscprc file).

  • Load the com.ibm.ejs.sm.ejscp.DrAdminExtension extension and then set trace properties by using the -setTrace option of the DrAdmin local operation. See 6.6.0.2.2.3.8: Enabling tracing with DrAdmin for details.

The following example lines set trace properties. The first line enables all tracing for all of the wscp classes; the second line enables tracing for only the wscp.commands classes.

wscp.traceString=com.ibm.ejs.sm.ejscp.*=all=enabled
wscp.traceString=com.ibm.ejs.sm.ejscp.commands.*=all=enabled

You can also use the DrAdmin extension to enable and set tracing for the administrative server and for application (enterprise bean) servers.

If you are not using the DrAdmin extension, you must use the console to enable tracing for an application server. You can, however, use wscp to set trace for these servers by modifying the TraceSpec attribute of the server object.

See Administering the product messages, logs, and traces for additional information on tracing.

Go to previous article: 6.6.0.2.2.3.6: Use of qualified home names in the administrative server Go to next article: 6.6.0.2.2.3.8: Enabling tracing with DrAdmin

 

 
Go to previous article: 6.6.0.2.2.3.6: Use of qualified home names in the administrative server Go to next article: 6.6.0.2.2.3.8: Enabling tracing with DrAdmin