HCL Workload Automation, Version 9.4

Setting up to log traces on WebSphere Application Server

By default, the SMSE adapter is traced only at start up, and only errors due to the incorrect configuration of the adapter (in the smseadapter.properties file) or that happen during the startup process are logged in the SystemOut.log file of WebSphere Application Server (located in <WAS_profile_path>/logs/server1/SystemOut.log or <WAS_profile_path>\logs\server1\SystemOut.log in the master domain manager).

If you want the complete logging of the SMSE adapter, you must activate the tws_smseadapter trace on WebSphere Application Server.

To do so, run the following procedure on the master domain manager:
  1. Access the <TWA_home>/wastools directory.
  2. Run the script:
    ./changeTraceProperties.sh [-user <TWS_user> 
                               -password <TWS_user_password>]
                               -mode tws_smsadapter
    changeTraceProperties.bat [-user <TWS_user> 
                              -password <TWS_user_password>]
                              -mode tws_smsadapter
    [-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.
    -mode <tws_smsadapter> is one of the following values:
    All communications involving the event correlator are traced.
    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, HCL Software Support.
    All HCL Workload Automation communications are traced.
    Resets the trace level to the default level imposed at installation.
    Only the messages issued by the workload broker workstation are traced.
    All dynamic workload broker communications are traced.
    Only the communication between dynamic workload broker and the agents is traced.
    All HCL Workload Automation command line communications are traced.
    All HCL Workload Automation connector communications are traced.
    All HCL Workload Automation database communications are traced.
    Only information messages are traced. The default value.
    All HCL Workload Automation planner communications are traced.
    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, IBMHCL Software Support.
    All the activities of the Solution Manager External (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
    All HCL Workload Automation utility communications are traced.
  3. Stop and restart the application server.
All the SMSE adapter actions will now be logged in the <WAS_profile_path>/logs/server1/trace.log or <WAS_profile_path>\logs\server1\trace.log file.

To disable complete logging, run the command again to change the tracing level from all to info.

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