You can use properties files to create or change trace
service properties and the associated trace log under a server.
Before you begin
Determine the changes that you want to make to your trace
service configuration or its configuration objects.
Start the
wsadmin scripting tool. To start wsadmin using the Jython language,
run the wsadmin -lang jython command from the bin directory
of the server profile.
Note: 이 주제는 하나 이상의 애플리케이션 서버 로그 파일을
참조합니다. 권장되는 대안은 분배 및 IBM® i 시스템에서 SystemOut.log, SystemErr.log, trace.log 및 activity.log 파일을 사용하는 대신
HPEL(High Performance Extensible Logging) 로그를 사용하고
인프라를 추적하도록 서버를 구성하는 것입니다. 원시 z/OS® 로깅 기능과 연계하여 HPEL을 사용할 수도 있습니다. HPEL을 사용하는 경우
서버 프로파일 바이너리 디렉토리의 LogViewer 명령행 도구를 사용하여
모든 로그에 액세스하고 정보를 추적할 수 있습니다. HPEL 사용에 대한 자세한 정보는
HPEL을 사용한 애플리케이션 문제점 해결 정보를
참조하십시오.
About this task
Using a properties file, you can create, modify, or delete
a trace service object and its configuration properties.
Run
administrative commands using wsadmin to change a properties file
for a trace service, validate the properties, and apply them to your
configuration.
Table 1. Actions
for trace service properties files. You can create, modify,
and delete trace service properties.Action |
Procedure |
create |
Not applicable |
modify |
Edit properties and then run the applyConfigProperties command. |
delete |
Not applicable |
create Property |
Set properties and then run the applyConfigProperties command. |
delete Property |
Specify the properties to delete in the properties
file and then run the deleteConfigProperties command. |
Optionally, you can use interactive mode with the commands:
AdminTask.command_name('-interactive')
Procedure
- Create trace service properties.
- Specify TraceService properties in a properties file.
Open an editor and specify trace service properties and an
associated TraceLog under a server in a properties file. You can copy
the following example properties into an editor and modify the properties
as needed for your situation. The example shows a property under TraceService
with name myName and value myVal.
#
# Header
#
ResourceType=TraceService
ImplementingResourceType=GenericType
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}:TraceService=
AttributeInfo=services
#
#
#Properties
#
startupTraceSpecification="*=info"
enable=true #boolean,default(false)
context=!{serverName}
memoryBufferSize=8 #integer,required,default(8)
traceFormat=BASIC #ENUM(LOG_ANALYZER|BASIC|ADVANCED),default(BASIC)
traceOutputType=SPECIFIED_FILE #ENUM(SPECIFIED_FILE|MEMORY_BUFFER),default(MEMORY_BUFFER)
#
# Header
#
ResourceType=TraceLog
ImplementingResourceType=GenericType
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}:TraceService=:TraceLog=
AttributeInfo=traceLog
#
#
#Properties
#
maxNumberOfBackupFiles=5 #integer,default(1)
rolloverSize=20 #integer,default(100)
fileName="${SERVER_LOG_ROOT}/trace.log"
#
# Header
#
ResourceType=TraceService
ImplementingResourceType=GenericType
ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}:TraceService=
AttributeInfo=properties(name,value)
#
#
#Properties
myName=myVal
#
#
EnvironmentVariablesSection
#
#Environment Variables
cellName=WASCell06
serverName=myServer
nodeName=WASNode04
- Run the applyConfigProperties command
to create a TraceService configuration.
Running the applyConfigProperties command
applies the properties file to the configuration. In this Jython example,
the optional -reportFileName parameter produces a
report named report.txt:
AdminTask.applyConfigProperties(['-propertiesFileName myObjectType.props -reportFileName report.txt'])
- Modify existing trace service or associated TraceLog properties.
- Obtain a properties file for the trace service that
you want to change.
You can extract a properties file
for a TraceService using the extractConfigProperties command.
- Open the properties file in an editor and change the
properties as needed.
Ensure that the environment variables
in the properties file match your system.
- Run the applyConfigProperties command.
- Delete the trace service properties.
To delete
one or more properties, specify only those properties to delete in
the properties file and run deleteConfigProperties.
AdminTask.deleteConfigProperties('[-propertiesFileName myObjectType.props -reportFileName report.txt]')
Results
You can use the properties file to configure and manage
the trace service object.
What to do next
Save the changes to your configuration.