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

  1. Edit the TWSCCLog.properties file, located in the following path:
    On Windows operating systems
    <TWA_home>\TWS\
    On UNIX operating systems
    <TWA_DATA_DIR>/TWS/
  2. Modify the tws.loggers.msgLogger.level property.
    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.
  3. Save the file. The change is immediately effective.
  4. Modify the Conman.ini to customize logging levels for conman commands.
    The Conman.ini file is located in the following path:
    On UNIX™ operating systems
    TWA_DATA_DIR/ITA/cpa/config
    On Windows™ operating systems
    TWA_home\TWS\ITA\cpa\config
  5. Save the file. The change is immediately effective.

See Engine log and trace customization for more details.

Modifying HCL Workload Automation tracing level

  1. Edit the TWSCCLog.properties file, located in the following path:
    On Windows operating systems
    <TWA_home>\TWS\
    On UNIX operating systems
    <TWA_DATA_DIR>
  2. 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.
  3. Save the file. The change is immediately effective.
  4. Modify the Conman.ini to customize logging levels for conman commands.
    The Conman.ini file is located in the following path:
    On UNIX™ operating systems
    TWA_DATA_DIR/ITA/cpa/config
    On Windows™ operating systems
    TWA_home\TWS\ITA\cpa\config
  5. Save the file. The change is immediately effective.

See Engine log and trace customization for more details.

Modifying Dynamic Workload Console tracing level

To activate the Dynamic Workload Console traces at run time, locate and edit the trace.xml template.

To modify the trace.xml template, follow this procedure:

  1. Copy the template file from the templates folder to a working folder.
  2. Edit the template file in the working folder with the desired configuration.
  3. Optionally, create a backup copy of the relevant configuration file present in the overrides directory in a different directory. Ensure you do not copy the backup file in the path where the template files are located.
  4. Copy the updated template file to the overrides folder. Maintaining the original folder structure is not required.
  5. Changes are effective immediately.

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

Modifying WebSphere Application Server Liberty Base tracing level

To modify the trace level on the WebSphere Application Server Liberty Base, edit the trace.xml file as necessary.

  1. Copy the template file from the templates folder to a working folder.
  2. Edit the template file in the working folder with the desired configuration.
  3. Optionally, create a backup copy of the relevant configuration file present in the overrides directory in a different directory. Ensure you do not copy the backup file in the path where the template files are located.
  4. Copy the updated template file to the overrides folder. Maintaining the original folder structure is not required.
  5. Changes are effective immediately.

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.