What is Documentum?
Documentum is organization content material administration software that presents management of content material and attributes such as check-in, check-out, workflow and model management. Documentum offers administration skills for all sorts of content such as commercial enterprise documents, images, video, e-mail, Web pages, constant content, XML-tagged documents, etc. The core of Documentum is a repository in which the content is saved securely underneath compliance rules.
Documentum additionally presents a suite of offerings which encompass document management, collaboration, search, content classification, input management, commercial enterprise method administration (BPM), client communication management, Web content management, digital asset management, types processing, statistics rights management, compliance and archiving etc.
What is an object ID? How Documentum object are named?
Each object saved in the repository is recognized through a special recognized known as object ID.
Documentum object are named as:
Dm_visible to users and applications.
Dmi_ represents object types that are used internally by Documentum Content Server and client products.
Dmr_ represents object types that are generally read-only.
What Key Characters does Documentum possess?
• Extensible
• Open
• Scalable
• Reliable
• Secure
• Portable
• Global
What is the Content Server?
Content Server is the basis of Documentum’s content administration system. It is a multi-featured product that gives get right of entry to to the information and content archives that represent a docbase. It stores content files, their indexes and properties in the docbase. So it controls the get admission to the docbase. It controls the user’s access to objects in the repository with the aid of offering ACL. It is the core performance that lets in users to create, capture, manage, supply and archive agency content.
What is a docbase?
The location where the data about a file is saved is referred to as as Docbase. It’s the mixture of the operating device (file system) and the database. The authentic file (content) is saved in the file machine and the data or attributes of the report are saved in Data base.
What is a docbroker/Connection broker?
Connection broking mainly recognize as docbroker offers repository connection facts to the customer application. Before putting in a WDK application, one desires to gain the names of the connection brokers to which the suitable repositories venture and the port numbers on which the connection brokers listen. The connection brokers used via WDK purposes are described in the dmcl.ini file on the application server host.
What is DFC?
DFC – Documentum Foundation Classes.
This is an object-oriented software programming interface (API) and framework for accessing, customizing and extending Documentum functionalities, carried out as a set of Java interfaces and implementation classes.
What do you know about UCF?
UCF – Unified Content Facilities
It is a light-weight applet that is accountable for transferring content material between the content server, application server and the client machine for the duration of operations such as check-in, checkout, import etc. UCF is a Java-based patron software that is set up at run-time. Since WDK application makes use of UCF content switch it downloads a light-weight applet to the browser when the consumer makes use of the Documentum operations for the first time.
What do you understand by WDK?
WDK – Web Development Kit
It is a developer’s toolkit that enables the improvement of complicated net primarily based functions that connect to Documentum content repositories and Documentum content material server. It consists of massive library of reusable elements and controls to function frequent Documentum administration functionalities.
What is a DocApp?
A DocApp is nothing however a packaging unit for Documentum objects. DocApps are used to bundle more than a few factors for customization (such as customized Object Types, Lifecycles, etc.) so that they can be ported from one repository to any other easily. Using Documentum Application Builder (DAB) you can create and package all your objects within a DocApp. A DocApp archive is a transportable illustration of a DocApp in a file on the file system. DocApps simplify developing and redeploying applications.
What is Business Objects Framework (BOF)?
Documentum BOF offers a framework and a methodology to enhance reusable enterprise logic elements known as Business Objects. This framework is constructed into DFC and on hand from purposes written the usage of DFC.
Do you know how Documentum manages the passwords?
Documentum supports a variety of options for implementing user authentication:
1) In-line password: A user can be authenticated using an encrypted password that is stored in the user_password attribute of the user object.
2) LDAP directory server: If you use LDAP directory server, you have the following options:
Authenticate against the directory server directly, using a secure or a non-secure connection
Authenticate using an LDAP-enabled dm_check_password program
3) Custom password checking program: One can create a custom password checking program and set up the servers to call that program for user authentication. This option is particularly useful if you want to use Windows domain authentication for UNIX users.
4) Authentication plug-in: Documentum provides authentication plug-in which supports Single Sign-On and strong authentication. (Strong authentication is the use of authentication tokens such as smart cards or biometrics.)
How can applications use Documentum?
Custom functions can be developed the usage of DFC (Documentum Foundation Classes) or WDK (Web Development Kit). DFC exposes Content Server API whilst WDK gives a framework and model for constructing a web application.
However, there are numerous factors and preferences when creating a custom application the use of Documentum. Custom workflows can mannequin business tactics and lifecycles can encapsulate enterprise regulations around documents. SBO’s (Service-based Business Objects) and TBO’s (Type-based Business Objects) can encapsulate business logic.
Documentum abilities can additionally be encapsulated in Web Services opening up a considerable array of possibilities. D6 (Documentum 6.0) provides DFS (Documentum Foundation Services) which consists of some core offerings as well as equipment for developing web services for Documentum. Then there are widespread interfaces such as FTP and JDBC, which permit a Documentum repository to be accessed the use of these protocols. Specialized connectors and portlets provide additional alternatives. PIA (Primary Interlope Assembly) approves access from .NET platform
What is a workflow and how can we create workflows in Documentum?
A workflow is a process that electronically passes documents and instructions from user to user. A workflow automates the process, ensuring that the right file goes to the right people in the right order.
Workflow tools: used to create the workflow definition called the workflow template are:
1) Workflow Manager
2) Business Process Manager
What is the difference between a workflow and lifecycle?
Lifecycles and workflows are equipment for implementing business policies within Documentum.
A lifecycle is a sequence of a file going between its advent and expiration states. Typical lifecycle states consist of Draft, Work in Progress, Approved, launched etc. Thus the focus of the lifecycle is an object.
A workflow represents a community of activities that electronically passes documents and directions from user to user. It automates the method making sure the right go with the flow of work in a system. For example, an approval workflow can take a file from the writer who created the document to an editor for evaluate and ultimately a manager for approval. Thus the workflow technique may additionally end result in altering lifecycle states of the document.
What is Rendition?
Rendition is an illustration of the document in a distinct format. Renditions can neither be edited nor versioned. A rendition is no longer stored as a separate file within the repository. Each rendition is connected to a current document. In fact, the only properties tied to a rendition are the object ID of the main format
document and the format of the rendition itself. When a document has versioned the usage of check in, the rendition of the preceding version is no longer copied to the new version. Each version wants to get its very own renditions.
What is app.xml and web.xml?
App.xml: The app.xml is an application configuration file wherein one can configure the application wide behaviour. In Documentum each application layer (webtop, wdk, webcomponent etc…) has an app.xml file. It is made of application elements tag such as for failover, content_transfer, authentications, formats, plug-in, listeners etc. To inherit and override settings in another application layer, the application definition can extend an application definition in another layer.
Web.xml: The web.xml file is a Web Application Deployment Descriptor for a web application. The web.xml file provides configuration and deployment information for the Web components that comprise a Web application. Examples of Web components are servlet parameters, servlet and Java Server Pages (JSP) definitions, and Uniform Resource Locators (URL) mappings.
What is the difference between Group and Role?
Group – A crew is a set of users, groups, or a combination of both. It is commonly used to assign permissions on an object.
Role – A role is a unique variety of group; it too can incorporate a set of users, different groups, or both. The difference is that a role is used through a client utility to filter out certain operations. WDK framework helps scoping of WDK aspects by role. For example, the Administration node in Webtop is only visible if the user is an administrator. Roles are NOT used to assign permissions on an object.
What are virtual documents?
A virtual document is a file that carries elements or children documents. It is composed of different components, every aspect being an individual object. The dmr_containtment object stores data about every person aspect of a virtual document.
Virtual documents are used in general for the following scenarios:
1) When there are more than one authors of a document, digital document creates individual element providing owner, security and different characteristics for the document.
2) Virtual files are beneficial in managing more than one file formats For E.g. if there are sub attachments like an excel sheet and a presentation attached to some phrase document. In this case a virtual file creates three heterogeneous file formats maintaining a single logical document.
3) Virtual files are beneficial when order of the children matters. By default the ordering relies upon on including or removing sequence of the components. But it can additionally be completed manually.
What are the major difference in Documentum 5.3 and Documentum 6.x?
Following are some of the major features introduced in Documentum 6.x which were not present in 5.3
– Webtop performance improved by reducing the number of refreshes and by making better utilization of the AJAX framework
– Documentum functionality presented as service in 6.x (Documentum Foundation Services i.e. DFS)
– Introducing Documentum Composer – which Supplies an Eclipse-based platform for Documentum tools, allowing you to configure application elements such as workflow templates, lifecycle definitions, security settings, aspects, and object types
– Introduces Aspects – new member in BOF family. Aspects are a mechanism for adding behavior and/or attributes to a Documentum object instance (and not object type) without changing its type definition
– XML Store as the underlying architecture for metadata and Web 2.0 content types in D6
– In the Documentum 6.5 release, the DocApp was migrated to the new Documentum Archive (DAR) format, which is compatible with Eclipse?based Documentum Composer development tool
– Unification of dfc.properties and dmcl.ini file. The dfc.properties file replaces dmcl.ini file to define behavioural preferences for client and application
– New DFC tracing capabilities and configuration. Tracing is now controlled by entries in dfc.properties rather than log4j file.
What’s the difference between a component and a container?
A element is composed of one or more JSP pages, assisting behaviour instructions and an XML configuration file.
A container is a specialised component. Many elements share frequent UI and state. For example, dialogs have a title, content area, and a button panel. Containers provide these frequent format and state for more than one components.
Components can be used inside more than one container, inheriting their UI and state from the container.
What are a component’s main features?
A component consists of
1) A component definition within a XML file that defines the following elements:
Unique . The optionally available component inheritance from a parent component definition is particular in the “extends” attribute.
element which defines the context in which the component definition is applied.
element containing the parameter used in the behavior class.
element consists of all presentation pages.
element specifying the behavior class
element specifies the category that consists of externalized strings for the component category and JSP pages. Properties documents in the bundle can be localized.
2) JSP pages: Layout is described in the JSP pages, the use of HTML and configurable Documentum tags. The definition described in the aspect of the definition XML as noted above.
3) Component behaviour class: has the logic of the component. This is described in the factor of the XML file as referred to above.
4) String resource file described in the component of the XML configuration
What are the major lifecycle methods of a component in Documentum?
The major lifecycle methods of a component are listed below:
OnInit, onRender, onRenderEnd, onCommitChanges, onOk, onCancel etc.
What do you mean by Documentum object model?
The Documentum object model is used to characterize content in the repository. The object model is hierarchical as in an object-oriented programming language. Child objects inherit all attributes and behaviors of the parent object.
