Logs to collect for UCF problems

Symptoms:
UCF errors prevent users from running content transfer.

Cause:

UCF communication is a very complex process. Since it passes through multiple network devices, there are many reasons that may cause this process to fail. To determine what is the exact cause of the problem, a complete set of logs and the network traffic data is are necessary. Network traffic data reveals complete data and messages between the UCF client and the server, including the network devices that may inject additional data into the communication channel. That information is not revealed by the trace logs.

Resolution:

There are common solutions for the UCF problems: For example, removing the UCF folder in client workstation and cleaning the IE cache and disabling ACS in wdk/app.xml. But sometimes these steps could not fix the problem. The following logs are needed to provide to Engineering for troubleshooting:

On the App Server side:
Open file /WEB-INF/classes/ucf.server.config.xml, change the option "tracing.enabled" from false to true. The App server must be recycled during scheduled maintanence hours for this option to take effect.

On the client side:
- Close all browser windows.

- Open C:\Documents and Settings\\Documentum\ucf\\shared\config\ucf.client.config.xml, change the option "tracing.enabled" from false to true.

- Open C:\Documents and Settings\\Documentum\ucf\\shared\config\ucf.client.logging.properties, change the line ".level=WARNING" to ".level=ALL"

- Under C:\Documentum\Logs, remove files named ucf.*

- Launch a new browser instance.

- Log into Webtop.

- In the browser window, launch Java Console from its Tools menu, and in the console window press key 5.

- In browser window, press ctrl+N to open a new window.

- In the new browser window, access: http://host:port/webtop/wdk/tracing.jsp, and check the following options "HTTP_MANAGER", "UCF_MANAGER", "Tracing is enabled for current session".

- Launch Ethereal or Wireshart (network sniffer) and start to capture all the network traffic between this client workstation and the web server/app server.

- In the first browser window, reproduce the problem.

- Record the time the problem takes to be reproduced and see if there is any time difference between the client workstation's clock and the web server/app server machine's clock.

- Collect the log files under C:\Documentum\Logs

- Collect the traces in Java Console.

- Collect the network traffic data file generated by Ethereal/Wireshark.
Download from http://www.wireshark.org/download.html.
Put the filter as tcp port xxxx or host ipaddress to capture all the traffic.

On the Web Server/App server side:
- Collect the wdk.log* and trace.log* under $DOCUMENTUM_SHARED

- Collect the web server logs.

- Collect the app server logs.