AWI 12.0-12.2 Tomcat and AWI Tracing

Document ID : KB000107695
Last Modified Date : 25/07/2018
Show Technical Document Details
Introduction:
AWI and Tomcat trace settings are needed by support when there is no error displayed on the AWI or the error is too generic. Turning the trace on gives support and devs a more detailed log, making it easier for them to narrow down the component where the cause of the unexpected function behavior.
Environment:
Tomcat version 7.0+
Instructions:

A.) Modify uc4config.xml for AE Client Trace:

-- Located at <Apache Tomcat Installation>/webapps/<ECC Name>/config/uc4config.xml

    Change the line reading:

     <trace count="10" xml="0"></trace>

      to

      <trace count="10" xml="3"></trace>

 

B.) Modify logback.xml for Tomcat Trace:

-- Located at <Apache Tomcat Installation>/webapps/<ECC Name>/config/logback.xml

   Change the line reading:

    <root level="INFO">

    to

    <root level="TRACE">

C.) Backup current Tomcat log directory (<Apache Tomcat Installation>/logs) in case the error is not easily reproducible.

D.) Remove contents of log directory.

E.) Restart the Tomcat Server. 
    
This is usually done via Services.msc

F.) Replicate the issue.
     
Log into AWI and reproduce the issue.

G.) Stop the Tomcat Server.
    
This is usually done via Services.msc

H.) Change the values back to original settings in steps A and B.
     If this is not changed, then the logs will keep growing in size.

I.) Provide all the Tomcat logs, Tomcat traces, AWI logs, and AWI traces.
     Zip it up and send it.

J.) Get new set of WP logs.

K.) Restart the Tomcat Server.
    
This is usually done via Services.msc