Content Management - Roadmap - Building Custom Desktop-Based Applications

Documentum provides a powerful and flexible tool set for developing custom-built solutions on top of the eContent server. Programmers have the option of using DMCL, DFC or JDBC to develop desktop-based content management applications. Developers can also reduce development and QA time by making use of The Desktop Client (DTC) components in custom-built applications.

Uploaded by

tabalajir

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

17 views

Content Management - Roadmap - Building Custom Desktop-Based Applications

Uploaded by

tabalajir

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 1

content management: Roadmap - Building Custom Desktop-based Applica...

http://developer.emc.com/developer/roadmap/build_custom_dt.html

Options Overview || Roadmap || DeskTop Options

Building Custom Desktop-based Applications

Content Code Documentum provides a powerful and flexible tool set for developing custom-built solutions on top of the eContent server. Application programmers have the option of using DMCL, DFC or JDBC to develop desktop-based content management applications. Developers can also reduce development and QA time by making use of the DeskTop Client (DTC) components in custom-built applications. A discussion of the factors to consider when making the decision are presented below. The Big Picture Developers have the option of building component-based or non-component-based applications. Component-based applications use COM components to encapsulate functionality into reusable modules. To minimize your development effort, Documentum supplies a set of COM components that you can call from your applications. These components perform common content management functions like check in, check out and import. In addition, Documentum provides a component, the Component Dispatcher to discover and launch the appropriate component based on business rules. Non-component based applications make calls directly to the eContent server using DMCL, DFC or JDBC. The Desktop Client (DTC) Components Documentum's desktop components serve as building blocks for custom desktop application development on the Microsoft platform. These components are called into action when a user requests an operation. Examples include check in, check out, cancel check out, import, and open (for a complete list see Developing DocApps). Documentum's DeskTop Client and Microsoft Office integration are examples of applications that provide access to content management functionality through the DTC component set. For instance, when a user requests a check out on a document, a component called DcCheckoutComp is invoked to perform the operation. Developers should consider making use of the component set when developing their own desktop applications. Since components follow Microsoft's common object model specification (COM) developers can program with Visual Basic, C++, Java or any language that can call COM components. Documentum provides the Visual Basic Source code for several components so that developers can modify them to meet their requirements. To learn more see Customizing the DeskTop Client. DMCL and DFC The Documentum client library or DMCL, is a library of procedures and functions that implement the server API set. The Documentum Foundation Class library or DFC, implements the API and an additional layer of related business logic. It does so through a set of interfaces that client programs can use to access DFC from Java or COM. The diagram below shows the relationship between DMCL, DFC and the COM component set. It also shows the additional business logic contained within the DFC.

EDN Home Content Management Resource Management SNIA SMI-S Open Source

Programmers may write to the DMCL or the DFC layer, however, most developers choose DFC since it provides an object-oriented programming interface and offers access to the business logic layer. In addition, as new eContent server functionality becomes available (XML is an example), access to it is provided only through the DFC. While it isn't generally recommended, DMCL may be an option on those occasions where developers are accessing base DMCL functionality and require the highest possible level of performance. For instance, if you are executing a series of queries, DMCL may provide a performance edge in some cases. DFC provides "pass through" methods to DMCL (apiGet, apiSet, apiExec) allowing you to program at the DFC layer and drop down to DMCL when appropriate. Both DFC and DMCL can be accessed from Docbasic and a variety of languages including Java, Visual Basic and C++ (see the DFC and DMCL resource tables for details). For more information about the differences between programming with the DFC and the DMCL, see Chapter 8, DFC and DMCL in Using DFC in Documentum Applications . The JDBC Option JDBC provides programmatic access to relational data from the Java platform. Using the Documentum JDBC driver, applications written in Java can execute DQL statements, retrieve results and propagate changes back to an underlying Docbase. If you are familiar with the Docbase Server API and the JDBC CallableStatement then you can also execute API commands using the driver. Documentum's JDBC driver can also access content and metadata stored in a WebCache. Learn more about the JDBC driver. See the resource table for JDBC.

1 of 1

2/13/2012 4:00 PM