D2 Architecture


D2 Client consists of three layers:

  • The Browser layer denoting the web browsers that are used by end users to connect to D2. D2 uses standard HTTP requests for all communication between the browser client and the D2 web application. For requests for static resources such as images, D2 uses GWT RPC calls backed by the D2FS services layer, to retrieve dynamic data
  • The web application server layer corresponds to the installation and configuration of D2.war which mainly includes most of the presentation logic, including the GWT and GXT libraries, custom interface controls, static web resources, and pass-through services to allow web browsers to invoke the D2FS services. The layer does not link to the DFC or DFS client libraries because all communication between the D2 web application and the Documentum repository passes through the D2FS interface.
  • The Documentum Content Server layer that consists of the installed DAR files. Includes most of the Documentum types necessary for storing configuration objects in the repository. Configuration objects are subtypes of d2_module_config or d2_moduledoc_config, depending on whether the configuration is stored as object metadata or as XML content.

D2 Config is comprised of three layers:

  • The Browser layer denoting the web browsers that are used by end users to connect to D2 Config.
  • The web application server layer that corresponds to the installation and configuration of D2–Config.war and the D2-Widget plug-in. This includes most of the presentation logic, including the ActiveX controls.
  • The Documentum Content Server layer.

Comments

Post a Comment

Popular posts from this blog

Using Java reflection to reduce Code and Development time in DFS

  Java reflections are one of the most powerful API’s of Java Language, this can be used to reduce code significantly. Most of the Current Enterprise application consists of different layers and they  use Value objects to transfer data from one layer to another. An inefficient way of using getters and setters of the attributes of Value objects can increase code and development time of application. Effective use of reflection can reduce code and development time significantly. So let’s take a Scenario,  I have an Object type MyObjectType extending from dm_document with 50 additional attributes, so dm_document as of Documentum 6.5 has 86 attributes adding additional 50 attributes that means we have 139 attributes for this object type. Consider a standard Web Application using DFS behind which needs to manipulate (add or edit) instances of this object type, The Service needs to add all these attributes to the  PropertySet    of the  DataObject  repre...
Read more

Virtual Documents in Documentum

Image
  What is a Virtual Document Simplistically speaking Virtual document is a document that can contain another documents . After reading the above statement first question that might arise to all is if it can contain documents how is it different from a folder? Let me make few bullet points about Virtual Document here, which will clear most of the confusions that you might have about virtual documents.   ·   A Virtual Document is a Document which can contain the type or the sub type of SysObjects  with an exception given below ·   A Virtual Document cannot contain any folders or cabinets, or any sub types of these. ·   A Virtual Document object may or may not have a content (dmr_content) attached to it but a folder or a cabinet will never have any content attached to it. Though most of the time a Virtual Document might not be having a Content file attached to it. ·   Any Object type that extents from SysObject can be converted as a Virtual Document. The ...
Read more

Few Important Object Types in Documentum

    Documentum is an Object Oriented Content Management Systems. Everything in Documentum is considered as Objects, This includes all the things that user manipulates, or the content server saves. From the User to Document, everything in Documentum is different type of Object. The whole Object types in Documentum has been structured in a Hierarchal model. Means All the Attributes from the super types are extended to the sub types. In other sense the attributes of Super types are visible and accessible from the Subtypes.   Lets see some of the important and most commonly used object types here.    Note: This is just to give an insight of Documentum Object model. Please read Object Reference Manual for very detailed information on All Object types and its attributes. Persistence Object  This type is the super type of all the object types that are saved in Documentum. Each time user creates an object instance of Persistence object type they are objects stored ...
Read more