HCL Workload Automation, Version 9.4

Setting the traces on the application server for the major HCL Workload Automation processes

About this task

The application server handles all communications between the HCL Workload Automation processes. The trace for these communications is set to "tws_info" by default (information messages only). The application server can be set to trace "all" communications, either for the whole product or for these specific groups of processes:

Command line
Connector
Database
Planner
Utilities
Dynamic workload broker

Significant impact on performance: Activating traces for the WebSphere Application Server leads to a significant impact on performance, especially if you set the tracing to "all". Thus you are strongly advised to identify the process group where the problem that you want to trace is occurring, and only set the trace to that group.

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.

To reset the traces to the default value, either run the above procedure with trace_mode as tws_info, or just stop and start the server, 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
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.