Configuring traces using scripting
Use the wsadmin tool and scripting to configure traces for a configured server.
Before you begin
About this task
Perform the following steps to set the trace for a configured server:
Procedure
- Identify the server and assign it to the server variable:
Using Jacl:
set server [$AdminConfig getid /Cell:mycell/Node:mynode/Server:server1/]
Using Jython:
server = AdminConfig.getid('/Cell:mycell/Node:mynode/Server:server1/') print server
Example output:server1(cells/mycell/nodes/mynode/servers/server1|server.xml#Server_1)
- Identify the trace service belonging to the server and
assign it to the tc variable:
Using Jacl:
set tc [$AdminConfig list TraceService $server]
Using Jython:
tc = AdminConfig.list('TraceService', server) print tc
Example output:(cells/mycell/nodes/mynode/servers/server1|server.xml#TraceService_1)
- Set the trace string. The following example sets the trace
string for a single component:
Using Jacl:
$AdminConfig modify $tc {{startupTraceSpecification com.ibm.websphere.management.*=all=enabled}}
Using Jython:
AdminConfig.modify(tc, [['startupTraceSpecification', 'com.ibm.websphere.management.*=all=enabled']])
- The following command sets the trace string for multiple
components:
Using Jacl:
$AdminConfig modify $tc {{startupTraceSpecification com.ibm.websphere.management.*=all=enabled:com.ibm.ws. management.*=all=enabled:com.ibm.ws.runtime.*=all=enabled}}
Using Jython:
AdminConfig.modify(tc, [['startupTraceSpecification', 'com.ibm.websphere.management.*=all=enabled:com.ibm.ws. management.*=all=enabled:com.ibm.ws.runtime.*=all=enabled']])
- Save the configuration changes. See the saving configuration changes with the wsadmin tool information.
- In a network deployment environment only, synchronize the node. See the synchronizing nodes with the wsadmin tool information.
Related tasks:
Related reference:


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=txml_configtrace
파일 이름:txml_configtrace.html