nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cleanup UCF client directories

apriam_i

Hello!

I'm using Documentum Content Server 6.5 sp2 with Webtop (same version and sp).

Is there any way to cleanup directories from user profile for next use re-install of UCF?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

Francois Dauberlieu

In the Task Manager, kill the javaws.exe processes and if you use the application connector, kill the Documentum Application connector processes (you'll need to log out and back in Windows after cleaning up the ucf directory)

All comments

DCTM_Guru

What do you mean "... for next use re-install of UCF"? UCF has parameters that you can configure to do housecleaning of UCF directories.

Francois Dauberlieu

On top of Johnny's comment, if you set a higher version number in the UCF installer config file on the app server, to make sure, then it will automatically install and use it

GouravMukherjee

So, what exactly do you aim at achieving here.

1. Do you want a fresh UCF installation?

This can be done just by bumping up the version in the ucf.installer.config.xml on the app server. This file is available inside your deployed webapp in the contentXfer folder for Webtop like applications.

Change

<app id="shared" version="6.5.0.****" compatibilityVersion="5.3.0"/>

<app id="shared" version="6.5.0.****a" compatibilityVersion="5.3.0"/>

This will force a re install of UCF the next time it comes up.

2. Do you want to clean up the Viewed files?

This should be done when housekeeping kicks in.

3. Do you want to clean up all the folders?

This does not happen automatically, and is nor generally recommended.

Please revert back if you need more information on this.

apriam_i

Hi, Johnny!

I need a clean instance without any UCF traces.

I removed all java cache, browser cache, cookies, but failed to remove subrirectories in {user.home}/Documentum. Those directories seem to be locked by some process. I have no idea how to release this lock, only reboot helps to delete them.

Francois Dauberlieu

apriam_i

It was java.exe process.

GouravMukherjee

It's actually a javaw.exe process. This is also known as the UCF client engine. Besides this process, sometimes the browser also holds a lock to the folders. Ideally you should kill the javaw.exe process and close all the browser instances. This should allow you to clean up the UCF directory.

apriam_i

Gourav, hello!

Sorry, but the process which blocks subdirectory named ucf-java in {user.hoome}/Documentum has name "java.exe".

Deletion allowed only after stopping this process.

Here is additional info about this "blocking" process:

Module:                java.exe
Full path:             C:\Java\jre6\bin\java.exe
File version:          6.0.160.1
Description:           Java(TM) Platform SE binary
PID:                   3392
Parent PID:            1972  (IEXPLORE.EXE)
Priority:              8
Threads:               26
Owner:                 CRYPTOPROTEST\Administrator (S-1-5-21-4264230390-380640930-1931119571-500)
Session:               0Started at:            09.09.2009 17:58:05
Uptime:                16:48:01Command Line:
C:\Java\jre6\bin\java.exe -D__jvm_launched=4358006631 -Xbootclasspath/a:C:\Java\jre6\lib\deploy.jar;C:\Java\jre6\lib\javaws.jar;C:\Java\jre6\lib\plugin.jar -Djava.class.path=C:\Java\jre6\classes sun.plugin2.main.client.PluginMain write_pipe_name=jpi2_pid19Current Directory:     C:\Documents and Settings\Administrator\Desktop\

There were no any javaw.exe process on host.

GouravMukherjee

That's a bit unusual, I must say. Can you please tell me what your ucf.installs.config.xml (found in <USERHOME>/Documentum/ucf/config) folder says under the java tag in the exePath attribute. Here's a sample of what I want to check...

<java version="1.6.0" minVersion="1.5.0" exePath="C:\Program Files\Java\jre6\bin\javaw.exe"

apriam_i

Gourav, here is the lines from xml:

When I start working with Webtop 2 additional processes are started:

javaw.exe and java.exe

So you were right about javaw.exe process

Some info about javaw.exe:

Module:                javaw.exe
Full path:             C:\Java\jre6\bin\javaw.exe
File version:          6.0.160.1
Description:           Java(TM) Platform SE binary
PID:                   3132
Parent PID:            2940  (java.exe)
Priority:              8
Threads:               13
Owner:                 CRYPTOPROTEST\Administrator (S-1-5-21-4264230390-380640930-1931119571-500)
Session:               0Started at:            14:30:11
Uptime:                00:09:42

Some info about java.exe:

Module:                java.exe
Full path:             C:\Java\jre6\bin\java.exe
File version:          6.0.160.1
Description:           Java(TM) Platform SE binary
PID:                   2940
Parent PID:            2712  (IEXPLORE.EXE)
Priority:              8
Threads:               30
Owner:                 CRYPTOPROTEST\Administrator (S-1-5-21-4264230390-380640930-1931119571-500)
Session:               0

Started at:            14:30:04
Uptime:                00:12:19

As it shows - javaw.exe is started from java.exe

That's the point!

GouravMukherjee

Yeah, that's absolutely correct, the java is just the one that must have been spawned by IE to spawn the javaw and at a later point provide commands to the UCF client engine (javaw).

So here is how it works, you log into the Webtop, an applet gets launched, this is the java process. This applet then launches the UCF client engine, the javaw process. The java process writes and reads commands to the system directory in the UCF client side installation (in and out directories). This holds the lock when you try to delete the folder after you kill the javaw process and if you kill the browser, in turn killing the applet (the java process), this lock will be released.

Please excuse me for repeating anything that was already obvious to you.