HCL Workload Automation, Version 9.4

Quick reference: how to modify log and trace levels

Quick reference information about how to modify log and tracing levels for all components.

Modifying HCL Workload Automation logging level

Edit <TWA_home>/TWS/TWSCCLog.properties
Modify tws.loggers.msgLogger.level.
This determines the type of messages that are logged. Change this value to log more or fewer messages, as appropriate, or on request from IBM® Software Support. Valid values are:
INFO

All log messages are displayed in the log. The default value.

WARNING

All messages except informational messages are displayed.

ERROR

Only error and fatal messages are displayed.

FATAL

Only messages which cause HCL Workload Automation to stop are displayed.
Save the file. The change is immediately effective.

See Engine log and trace customization for more details.

Modifying HCL Workload Automation tracing level

Edit <TWA_home>/TWS/TWSCCLog.properties
Modify tws.loggers.trc<component>.level.
This determines the type of trace messages that are logged. Change this value to trace more or fewer events, as appropriate, or on request from IBM Software Support. Valid values are:
DEBUG_MAX

Maximum tracing. Every trace message in the code is written to the trace logs.

DEBUG_MID

Medium tracing. A medium number of trace messages in the code is written to the trace logs.

DEBUG_MIN

Minimum tracing. A minimum number of trace messages in the code is written to the trace logs.

INFO

All informational, warning, error and critical trace messages are written to the trace. The default value.

WARNING

All warning, error and critical trace messages are written to the trace.

ERROR

Only error and critical messages are written to the trace.

CRITICAL

Only messages which cause HCL Workload Automation to stop are written to the trace.
Save the file. The change is immediately effective.

See Engine log and trace customization for more details.

Modifying Dynamic Workload Console tracing level

Follow these steps to activate the Dynamic Workload Console traces at run time:

Log in to the Dynamic Workload Console as administrator of the WebSphere Application Server
In the Dynamic Workload Console navigation pane select Settings > WebSphere Admin Console
Click Launch WebSphere Admin Console.
In the navigation tree, click Troubleshooting > Logs and Trace > server name (for example tdwcserver) > Diagnostic Trace.
Select:
Configuration

If you want to apply the changes to the trace settings after having restarted the server.

Run time

If you want to apply the changes to the trace settings without restarting the server.
Click Change Log Detail Levels under Additional Properties.
Choose the packages for which you want to activate the traces. For the Dynamic Workload Console traces, make this selection:
1. Scroll down to com.ibm.tws.* and expand the tree
2. Click com.ibm.tws.webui.*
3. Either select All Messages and Traces or click Messages and Trace Levels and choose the trace level you require.
4. Click OK > Save.
Stop and start the server, if necessary.

Alternatively, you can activate the Dynamic Workload Console traces as follows:

Edit the following XML file:
Installed on the WebSphere Application Server:
```
JazzSM_profile_dir/config/cells/JazzSMNode01Cell/n
odes/JazzSMNode01/servers/server1/server.xml
```
where, the default value of JazzSM_profile_dir is:
On Windows operating systems

C:\Program Files\IBM\JazzSM\profile

On UNIX operating systems

/opt/IBM/JazzSM/profile
Change the value assigned to the property startupTraceSpecification from:
com.ibm.tws.webui.*=info

to:

com.ibm.tws.webui.*=all.
Save the changes
Stop and start the server.

See: Activating and deactivating traces in Dynamic Workload Console for more details.

Modifying WebSphere® Application Server tracing level

The procedure for changing the trace level on the WebSphere Application Server is as follows:

Log on to the computer where HCL Workload Automation is installed as the following user:
UNIX

root

Windows

Any user in the Administrators group.
Access the directory: <TWA_home>/wastools
Run the script:
UNIX
```
./changeTraceProperties.sh [-user <TWS_user> 
                           -password <TWS_user_password>]
                           -mode <trace_mode>
```
Windows
```
changeTraceProperties.bat [-user <TWS_user> 
                          -password <TWS_user_password>]
                          -mode <trace_mode>
```
where:
[-user <TWS_user> -password <TWS_user_password>]

The user and password are optional. By default, the script looks for the credentials in the soap.client.props file located in the properties directory of the WebSphere Application Server profile.

<trace_mode> is one of the following values:

active_correlation

All communications involving the event correlator are traced.

tws_all_jni

All communications involving the jni code are traced. The jni code refers to code in shared C libraries invoked from Java™. This option is used by, or under the guidance of, IBM Software Support.

tws_all

All HCL Workload Automation communications are traced.

tws_alldefault

Resets the trace level to the default level imposed at installation.

tws_bridge

Only the messages issued by the workload broker workstation are traced.

tws_broker_all

All dynamic workload broker communications are traced.

tws_broker_rest

Only the communication between dynamic workload broker and the agents is traced.

tws_cli

All HCL Workload Automation command line communications are traced.

tws_conn

All HCL Workload Automation connector communications are traced.

tws_db

All HCL Workload Automation database communications are traced.

tws_info

Only information messages are traced. The default value.

tws_planner

All HCL Workload Automation planner communications are traced.

tws_secjni

All HCL Workload Automation jni code auditing and security communications are traced. The jni code refers to code in shared C libraries invoked from Java. Only use this option under the guidance of, IBM Software Support.

tws_smseadapter

All the activities of the Solution Manager Scheduling Enabler (SMSE) adapter on the master domain manager are logged in the trace.log file. The only exceptions apply to errors due to missing libraries or errors incurred during the startup process, which are recorded in the SystemOut.log file

tws_utils

All HCL Workload Automation utility communications are traced.
Stop and restart the application server, as described in the section on starting and stopping the application server in the HCL Workload Automation: Administration Guide.

See Setting the traces on the application server for the major HCL Workload Automation processes for more details.

Managing dynamic agent tracing level

To manage traces for the dynamic agent, refer to the following sections:

You can also configure the traces when the agent is not running by editing the [JobManager.Logging] section in the JobManager.ini file as described in Configuring the agent section. This procedure requires that you stop and restart the agent.