|
| Problem | Steps to setting up SAS and Security Tracing using the WSCP. | | | | Solution | The WSCP tool provided with WebSphere Application Server can be used to enable tracing on application server(s). Following are the steps that can be used to enable SAS and security traces:
List all application serverswscp>ApplicationServer list
{/Node:pigpen/ApplicationServer:Default Server/} Show specified attribute settings for a specific application server (i.e. Default Server):wscp>ApplicationServer show {/Node:pigpen/ApplicationServer:Default Server/} -attribute {TraceSpec TraceOutput CommandLineArgs}
{CommandLineArgs {}} {TraceOutput {}} {TraceSpec {}} (1) Set SAS Traces on a specific Application Server(i.e. Default Server):wscp>ApplicationServer modify {/Node:pigpen/ApplicationServer:Default Server/} -attribute {{CommandLineArgs {-Dcom.ibm.CORBA.securityDebug=console -Dcom.ibm.CORBA.securityTraceLevel=advanced}}}
(2) Set Trace Output File for a specific Application Server(i.e. Default Server):wscp>ApplicationServer modify {/Node:pigpen/ApplicationServer:Default Server/} -attribute {{TraceOutput C:\Temp\trace.out}}
(3)Set Security Traces on Application Server(i.e. Default Server):wscp>ApplicationServer modify {/Node:pigpen/ApplicationServer:Default Server/} -attribute {{TraceSpec com.ibm.ejs.security.*=all=enabled}}
Show specified attribute settings after doing 1, 2, and 3 (i.e. Default Server):wscp>ApplicationServer show {/Node:pigpen/ApplicationServer:Default Server/} -attribute {TraceSpec TraceOutput CommandLineArgs}
{CommandLineArgs {-Dcom.ibm.CORBA.securityDebug=console -Dcom.ibm.CORBA.securityTraceLevel=advanced}} {TraceOutput {C:\Temp\trace.out}} {TraceSpec com.ibm.ejs.security.*=all=enabled} Stop and Start a specific Application Server(i.e. Default Server):wscp> ApplicationServer stop {/Node:<NodeName>/ApplicationServer:Default Server/}
wscp> ApplicationServer start {/Node:<NodeName>/ApplicationServer:Default Server/}
List all nodes on the WebSphere Application Server installation:Stop a specific node:wscp> Node stop /Node:porkypig/
To complete the SAS and security tracing, you may also want to enable it on the Administrative Server. This is done via the admin.config file and not via the WSCP tool, as follows:
Security Trace at the Administrative Server Add the following lines to the admin.config file com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.security.*=all=enabled com.ibm.ejs.sm.adminServer.traceOutput=c:\your_trace_directory\sectrace.log
SAS Trace at the Administrative Server Add the following lines to the admin.config file com.ibm.CORBA.securityDebug=console com.ibm.CORBA.securityTraceLevel=advanced
Restart the Administrative Server in order to activate these trace settings.
Note: When backing out of the sas traces, you should also remove the sas.server.props.futures file to ensure the trace settings don't get reset. | |
| |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, System Management/Repository Operating system(s): Multi-Platform Software version: 3.5, 4.0 Software edition: Advanced Edition, Enterprise Edition Reference #: 1041610 IBM Group: Software Group Modified date: 2003-11-26
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|