A.) Modify uc4config.xml for AE Client Trace:
-- Located by default at <Apache Tomcat Installation>/webapps/<AWI>/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 by default at <Apache Tomcat Installation>/webapps/<AWI>/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 on Windows (sometimes in the service manager if the One Installer was used to install the product). Linux/UNIX will be done elsewhere; a system admin should know more.
F.) Replicate the issue.
Log into AWI and reproduce the issue.
G.) Stop the Tomcat Server.
This is usually done via Services.msc on Windows (sometimes in the service manager if the One Installer was used to install the product). Linux/UNIX will be done elsewhere; a system admin should know more.
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.
Logs and traces can be found by default in the Tomcat directory <Tomcat>/logs/
The AWI logs by default are named <host>_<AWI>_LOGxx.txt and <host>_<AWI>_TRCxx.txt
The Tomcat logs by default are named catalina.YYYY.MM.DD.log
Zip them and send them to our support team
J.) Get new set of WP logs.
By default, the WP logs will be found in the automation engine's \temp\ directory and will have a name like WPsrv_**_log##.txt
K.) Restart the Tomcat Server.
This is usually done via Services.msc on Windows (sometimes in the service manager if the One Installer was used to install the product). Linux/UNIX will be done elsewhere; a system admin should know more.