"UCF Timeout Error" in Documentum Webtop,DA,DCM,WP,RM

If you receive the error "UCF Timeout error" when managing files in Documentum (Webtop) or in an XML editor (XMetal), please go through the following troubleshooting steps to ensure that your browser and Java settings are properly configured.

 

Verify Java settings

1. Close ALL open browsers and applications.
2. Stop Java:
1. Start the Task Manager (right-click on the Windows Task Bar at the bottom of the screen)
2. Choose the Processes tab and sort the list of processes by clicking on the Image Name column header.
3. Make sure that javaw.exe is not in the list.
4. If it is in the Processes list, select it and click End Process at the bottom of the popup. Make sure all your applications are closed so that nothing unrelated gets killed in the process. You must repeat this step for each javaw.exe process in the list.
3. Open the Java Control Panel popup: Start > Control Panel > Programs > Java or Java (32-bit)  
4. 1. Clear the Java cache:
   1. On the General tab, in Temporary Internet Files section, click Settings...
   2. In the Temporary Files Settings popup, click Delete Files, then click OK.
   2. Clear EMC Java Certificates:
   1. On the Security tab, click Certificates...
   2. Select and Remove all certificates issued to "EMC Corporation".
   3. When finished, click Close.
   3. Make sure one version of Java is enabled:
   1. On the Java tab, click View ...
   2. Make sure only one Java version has the Enabled checkbox selected. Click OK.
   4. Disable next generation Java plug-in:
   1. On the Advanced tab, expand the Java Plug-in list. Uncheck Enable the next-generation Java Plug-in and click Apply.
   5. Click OK to close to Java Control.
   Verify your browser settings
   1. Clear browser cache and restore browser defaults:
   1. In your browser, choose Tools > Internet Options.
   2. On the General tab, browsing history section, click Delete. In the popup, select all checkboxes and click Delete, which closes the popup.
   3. On the Advanced tab, click the Restore advanced settings button, and Apply..
   2. In IE 7 and 8, enable Automatic prompting:
   1. On the Security tab, select Trusted Sites. In the Security level for this zone section, click the Custom level button.
   2. In the Security Settings popup, scroll to Downloads, enable Automatic prompting for file downloads, and click OK.
   3. If prompted, confirm that you want to accept changes.
   3. Close the Internet Options window and close the browser.
   Clear the Documentum cache
   Important: Before performing the following steps, don't forget to check in any document that you have checked out in Webtop. Otherwise, you will lose all your changes to the document!
   1. Double-click on the My Computer icon on your desktop, or choose Start > Computer.
   • On Windows XP: Navigate to the C:\Document and Settings\\Documentum folder.
   • On Windows 7: Navigate to the C:\Users\\Documentum folder.
   2. Delete all content in the ucf folder and close the window.
   Validate the results
   1. Restart your PC.
   2. Open an Internet Explorer browser and open Webtop (https://cms.mcgill.ca/webtop).
   3. If you get either of the following popups, do the following:
   • "This is the first you have visited the [cms.mcgill.ca] site. Do you want to trust content from this site?" Click Yes.
   • "Java has discovered application components that could indicate a security concern: ResidentUcfInvoker_LaunchRuntimeApplet_0." Click Run.
   4. Wait 2 to 3 minutes before continuing to the next step.
   5. Try to do the file operation that originally gave you the error message.
    

EMC Documentum Virtual Document

 Introducing Virtual Documents


Virtual documents are a way to combine documents whose contents have a variety of formats into one document.


You can associate a particular version of a component with the virtual document or you can associate the component’s entire version tree with the virtual document. Binding the entire version tree to the virtual document allows you to select which version is included at the time you assemble the document.


Users create virtual documents using the Virtual Document Manager, a graphical user interface that allows them to build and modify virtual documents. However, if you want to write an application that creates or modifies a virtual

document with no user interaction, you must use the API.


Although the components of a virtual document can be any SysObject or SysObject subtype except folders, cabinets, or subtypes of folders or cabinets, the components are often simple documents or another virtual document.

Documentum imposes no limits on the depth of nesting in a virtual document.


Content Server does not allow you to remove an object from the Docbase if

the object belongs to a virtual document. This ensures that the referential integrity of virtual documents is maintained.



Virtual Document Architecture


Content Server uses two object types to store information about virtual documents:

• Containment object type (Internal name: dmr_containment)


• Assembly object type ( dm_assembly)

          

Containment objects contain information about the components of a virtual document. Each time you add a component to a virtual document, a containment object is created for that component. Containment objects store the information that links a component to a virtual document. For components that are themselves virtual documents, the objects also store information that the server uses when assembling the containing document. The connection between the parent and the components is defined in two attributes of containment objects: a_contain_type and a_contain_desc.


          The process of selecting individual components to produce a virtual

document is called assembling a virtual document. Assembly objects make up assemblies. An assembly is a snapshot of a virtual document at a particular time. An assembly records the exact components of the virtual document at the time the assembly was created. Each assembly object in an assembly represents one component of the virtual document.


Conditional Assembly:

Assembling a virtual document selects a set of the document’s components for

publication or some other operation, such as viewing or copying. When assembling a virtual document, you can identify which components to include. You can include all the components or only some of them.


Early and Late Binding:

Attaching a specific version of a component to a virtual document is referred to as binding. Early binding occurs if you bind a specific version of a component to a document when you add the component to the document. Late binding occurs if you bind a specific version of a component to a document when you assemble the document.

Freeze

Freeze methods allow you to freeze a virtual document and an assembly associated with that document. When you issue a Freeze method against a virtual document, if there is an assembly associated with that document, you have the option to freeze the assembly also. Users cannot modify the content or attributes of a frozen virtual document or the frozen assembly components. Nor can they add or remove assembly components. However, users are allowed to modify any components of the virtual document that are not part of the frozen assembly. Although users cannot remove those components from the document, they can change the component’s content files or attributes.


Freezing sets the following attributes of the document to TRUE:

• r_immutable_flag

This attribute indicates that the document is unchangeable.

• r_frozen_flag

This attribute indicates that the r_immutable_flag was set by a Freeze method

(instead of a Checkin method).


There are two attributes in containment objects that control how components that are themselves virtual documents behave when the components are selected for an assembly. The attributes are use_node_ver_label and follow_assembly.



·Persistent object Attribute:

r_object_id: The r_object_id attribute contains the object's identifier, its object ID. This number is

generated by the server when the object is created and is unique.


·SysObject Attributes:

r_is_virtual_doc: If the attribute is set to TRUE, the client applications always open the document in the Virtual Document Manager.

r_link_cnt:  records how many direct components belong to the virtual document. Each time you add a component to a document, the value of this attribute is incremented by 1.

i_chronicle_id :Object ID of the root object of the version tree that contains this object.


·Containment Type Attributes

component_id: Chronicle ID of the component.(The chronicle ID is the objectID of the original version of an object. If the object has no versions, then its object ID and chronicle ID are the same.)

parent_id:  Object ID of the object that directly contains the component.


·Assembly Type Attributes

book_id :Object ID of the topmost containing document in the virtual document structure that contains the component described by this assembly object.

component _chron_id :Chronicle ID of the component represented by the assembly object.

component_id: Object ID of the component of the virtual document



The main attribute of a document that has to do with virtual documents is r_link_cnt. This attribute contains the number of children that are linked to a virtual document. If r_link_cnt=0, the object is not a virtual document. If r_link_cnt is > 0 the object is a virtual document. Note that r_link_cnt will never have a value of 1, because the parent of the virtual document is also considered a child. So if you add one component, r_link_cnt=2. If you add a second component, r_link_cnt=3, and so on.

Also note that this same attribute applies to dm_folder, indicating how many objects are linked into the folder.

There is no attribute of a document to show that it is a component of a virtual document.
Object Types

Documentum uses a special object to keep track of all the virtual documents in the docbase. It is called dmr_containment, and it has 4 attributes: parent_id, component_id, order_no, and version_label.

The dmr-containment object contains pointers to the virtual document and its components.

Note that the parent_id is the r_object_id of a specific version of the parent. This means that the components and the order of the components can change from one version of the parent to the next.


The component_id attribute is actually the i_chronicle_id of the component. This makes sense because the i_chronicle_id represents the entire version tree of an object, and we don't know what version of the various components we want until we issue the query to gather the components up (for more on this, see Late Binding vs. Early Binding).