With UCF there are two types of logging available for diagnostics. There are client side (browser) and server side (application server) logging available.
Client Side Logging:
To enable client side logging, 2 files will need to be modified. Both of these files can be found in the folder:
C:\Documents and Settings\<USERNAME>\Documentum\ucf\<HOSTNAME>\shared\config\
where USERNAME is the windows user ID and HOSTNAME is the machine hostname where the testing is being done.
The first file to be edited is ucf.client.config.xml. The following entry should be changed to true:
<option name="tracing.enabled">
<value>true</value>
</option>
The following entry will need to be added as well:
<option name="debug.mode">
<value>true</value>
</option>
The next file to be edited is ucf.client.logging.properties and set the .level entries to FINEST (all caps). The debugging levels available are (from least informative to most):
- SEVERE (highest value)
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST (lowest value)
Once these changes are made, UCF will begin logging on the client side starting with the next invocation. All output will be logged to: C:\Documentum\logs\ucf.client.*.log.
App Server Logging:
To enable UCF tracing, the following file in the WDK application will need to be edited:
../WEB-INF/classes/ucf.server.config.xml
In this file, the following entry will need to be set to true:
<option name="tracing.enabled">
<value>true</value>
</option>
UCF will log on the app server to $DOCUMENTUM_SHARED/logs/trace.log and/or wdk.log (depending on how log4j is configured). These changes will require a restart of the app server.