Pre-Installing UCF
| February 2006 | |
| Contributed by - Lani Hardage-Vergeer, EMC Documentum Tech Pubs |
Software Environment
| Feature | Tested on |
| Operating System | Windows 2000 Server SP4 |
| Compiler | Sun JDK 1.4.2_08 |
| Runtime | Sun JRE 1.4.2_08 |
| DFC | 5.3 SP2 |
| WDK | 5.3 SP2 |
| Webtop | 5.3 SP2 |
| Content Server | 5.3 SP2 |
Abstract
Prior to 5.3 SP2, UCF was installed solely through an application such as Webtop or Web Publisher. UCF installer binaries in SP2 contain a tool that enables administrators to pre-install UCF. You may wish to use this in locked environments or in order to provide a better user experience, avoiding the slow downloading UCF when the user accesses the application for the first time.
To pre-install UCF, invoke the following command from command line. Any version of java 1.1 or higher can be used to execute the installation command:
java -cp ... com.documentum.ucf.client.install.TestInstall
server_host relative_path_to_ucf.installer.config.xml
|
Where:
server_host is the URL to the WDK application server host
relative_path_to_ucf.installer.config.xml is the path relative to the WDK application root directory
For example:
java -cp "\\some network path\ucfinit.jar" com.documentum.ucf.client.install.TestInstall
"http://server_host:8080/webtop" "/wdk/contentXfer/ucf.installer.config.xml"
|
The classpath parameter cp refers to the path to one of the following jars:
-
For WDK-based applications, including Webtop, supply the path to ucfinit.jar. This is typically located in application_name/wdk/system, for example, webtop/wdk/system.
-
For other applications, supply the path to ucf-installer.jar in the application's installation directory on the application server host.
Successful installation returns the message "Installation successful". Failure returns an appropriate message with the corresponding stack trace.
Please note the following requirements and limitations:
-
The installation command should be executed physically for the OS user on the user's machine.
-
The tool won't work if the application server host or the ucf.installer.config.xml file is not accessible via a simple URL connection. For example, it may not work for SSO or proxy environments.
-
The tool is unsupported and is provided for administration convenience.
|
