| .NET |
 |
|
This convenience class allows developers to access Documentum Service-based
Business Objects (SBOs) from .NET languages. The class allows .NET developers
to make use of the existing Java-based business objects that ship with
Documentum products or are downloaded from the Component Exchange.
|  |  | Article |
 |
|
These custom ASP.NET controls provide some Documentum functionality such as
Login, Querying and Tree Navigation. These controls leverage new features
available in ASP.NET 2.0 (Visual Studio 2005).
|  |  | Component |
 |
|
This example illustrates how to invoke a Service Business Object from ASP.NET. The sample user control applies an XSL stylesheet to an XML file in a Documentum Repository and displays the results. The XSL file may contain XDQL statements. This example references the SBO Bridge that was discussed in a separate article on the Developer web site.
|  |  | Component |
 |
| Application Templates |
 |
|
This application template uses WDK, XML and business objects to illustrate how to build a pharmaceutical labeling solution. When drugs are released to market, certain information must be printed to support the drug, including the label on the bottle, the insert in the box, and more. This application template allows a user to manage the label data and produce the variety of output data using Documentum.
|  |  | Article |
 |
|
Common Technical Document (CTD) is an emerging standard used by the pharmaceutical industry for submissions to regulatory agencies. This month we are proud to present SAM, a prototype electronic CTD submission application built using the Webtop platform. Included in the prototype are all of the following:
- An overview of the eCTD standard,
- An AVI recording of the prototype demonstration and storyboard,
- A high-level architectural overview,
- Low level technical descriptions of the SAM components,
- Links to generic 'utility methods' written specifically for SAM,
- Comprehensive installation instructions,
- The components and source code to install SAM on your own development system.
|  |  | Article |
 |
|
This article demonstrates how to utilize a general-purpose component for an industry-specific application. Using the 'Document Bin' component, which can be downloaded form the Documentum Developer Program Component Exchange, we will create a solution for creating an engineering transmittal package and notice that can then be electronically sent to a supplier.
|  |  | Article |
 |
|
This document provides a guide to developers using Documentum Collaboration
Edition. It includes sample code and javadocs for the collaboration code
packaged under com.documentum.services.collaboration. The code samples provide
examples of how to use and leverage the collaboration API.
|  |  | Component |
 |
|
This sample ASP.NET application implements the basic Documentum library functions login, import, view, checkin and checkout. It also implements a hierarchical tree view of the Documentum repository using Microsoft's free ASP.NET tree control. The code manages the user's authentication and sessions throughout the application providing a 'user context' containing all of the current session's information.
|  |  | Tutorial |
 |
| ApplicationXtender |
 |
|
This NT service monitors a XS License Server. This service utilizes a script
to deliver configuration and process license server information. The script
provides the License Server connection information and polling interval.
|  |  | |
 |
| Business Objects Framework |
 |
|
This TBO automatically populates some of a documents attributes based on the
folder it is linked to.
|  |  | |
 |
|
DFC 5.3 introduced the concept of modules. A generic definition of a module
is that it is a discrete, self-contained unit that can be combined with other
modules to create a larger application. Service-based Business Objects(SBOs)
and Type-based Business Objects(TBOs) are types of modules. This article
discusses the process for creating a custom module.
|  |  | Article |
 |
|
This sample code describes the utility methods used in our samples to create WDK virtual links and URLs, and to get an object's linked folder information.
|  |  | Article |
 |
|
Learn how to execute XDQL using DFC. This article contains a snippet of code and instructions to show you the way.
|  |  | Article |
 |
|
This sample code describes the utility methods used to generate a checksum for a repository object's content using the Java Crypto API.
|  |  | Article |
 |
|
This sample code describes two utility methods designed to help you to find the relationship between two object types. The first determines whether one type is a supertype of a second. The second method gets all the subtypes of a specified type.
|  |  | Article |
 |
|
This sample code describes a utility method to do a 'deep folder create'. The method takes a string representing a cabinet/folder hierarchy and creates all levels of the path that do not already exist.
|  |  | Article |
 |
|
We often choose to store an application's configuration information in an XML file and business objects are no exception. To this end, we previously developed a standard XML configuration file framework to read XML configuration files. This updated version leverages a more standard and powerful XML storage model to support access using standard Xpath expressions
|  |  | Article |
 |
|
These sample service-based and type-based business objects provide a starting point for your business object development. The code samples illustrate how to implement a type-based business object that invokes methods that are provided by a service-based business object.
|  |  | Article |
 |
|
Download the most comprehensive guide to developing applications using Documentum business objects; the Documentum Developer Guide will walk you through details of the architecture, the different types of business objects and some basic examples. The examples in this guide have been implemented as code samples on the Component Exchange.
Please note: This is the BOF 5.1 Developer's Guide; the BOF guide has been merged in to the DFC Developer's Guide for version 5.2 and higher.
|  |  | Article |
 |
|
Log4j is an open source project that provides a reliable, fast and extensible logging library for Java. The Documentum DFC class, DfLogger is available with DFC 5.1 or higher and can only be used with Java. It uses the log4j logging library to enable logging from DFC applications. This paper gives an overview of how to use DfLogger in existing and new applications.
|  |  | Article |
 |
|
This paper is essential reading for anyone interested in the Documentum Business Objects Framework. The paper gives a clear and concise technical overview of business objects; it covers the reasons for using them, the different types of business objects and how they are implemented.
|  |  | Article |
 |
|
We often choose to store an application's configuration information in an XML file and business objects are no exception. To this end, we have developed a configuration file framework which includes a general purpose XML configuration file and a Java class that provides methods to access its content. This package also includes a simple Java application that illustrates how to use the XML Configuration Framework.
|  |  | Article |
 |
|
This article discusses means of trapping the import functionality using a
Type business object (TBO). For example,a common scenario when you might want
to do this is if you wanted to apply a lifecycle to objects when they are
imported, or apply a certain value to a property.
|  |  | Article |
 |
|
Documentum engineers have gained considerable experience over the years developing reusable business objects for our client applications. In an effort to capture lessons learned from this experience, several key engineers collaborated to produce a collection of best practices and guidelines for business object development. These are now used internally by all Documentum engineers when developing and unit testing business objects.
We are pleased to make this development guide available to our developer community. Please remember that the goal is to facilitate component reuse, extendibility, and quality; they are not intended to be an exhaustive list of requirements.
|  |  | Best Practice |
 |
|
This document contains best practices, tips and lessons learned by the Developer Program team through our experience writing the business objects found on the Component Exchange. This document will be updated frequently - please check back for new information.
|  |  | Best Practice |
 |
|
In 5.3 SP2, full-text indexing includes a new feature that allows the Index
Agent to skip certain documents from being indexed. A common example is job
reports because there are so many of them. This article discusses the process
of writing a custom index filter and provides a sample index filter that skips
documents in system cabinets such as 'System', 'Resources', 'Temp' and
'Templates'.
|  |  | Component |
 |
|
The service is used to perform a deep import of a local file system folder. The internal hierarchy (structure) of the local folder including the contained documents is recreated in the Docbase.
|  |  | Component |
 |
|
This service-based business object extends the original 'Web Content Downloader' code to include asynchronous downloads and multiple, simultaneous downloads. The code imports content from specified URLs into a repository, it will attempt to 'guess' the objects' formats, object_names, and titles if they are not supplied.
|  |  | Component |
 |
|
This Webtop customization allows you to send repository documents, or folders, as attachments in an email. The standard Webtop product only allows you to send URL links to repository objects as email attachments, however this customization exposes the functionality through a WDK mail component and uses an SBO to send the messages using the Java Mail API and a SMTP server.
Updated January 2005
|  |  | Component |
 |
|
The service provides utility functions related to zip archives and Docbase objects. The following types of utilities are included - creating a zip of a Docbase folder contents and storing it in the Docbase, extracting a zip into a Docbase folder, exporting a Docbase folder contents as a zip, and creating a zip of a file system folder and importing it.
Updated January 2005
|  |  | Component |
 |
|
This service-based business object executes asynchronous, multi-repository queries and can be used through any Documentum client that uses DFC 5.2.5 or above. The enclosed WDK component illustrates how to display the combined results of a multi-repository search.
|  |  | Component |
 |
|
Running a process asynchronously can significantly improve the user experience. This set of classes provides the means to execute business object code in an asynchronous manner by using a thread pool. The code is used in some of our other examples but has been packaged separately here to help you to decode and re-use it.
|  |  | Component |
 |
|
It is possible to 'wrap' a service-based business object, (SBO), in a Web service and then invoke it remotely. This Web service provides a wrapper for the Autonaming SBO, in this example we used BEA's Weblogic Workshop 7.0 product to simplify the development of the wrapper.
|  |  | Component |
 |
|
This service-based business object returns a string based on your company's own naming rules. Each rule is defined in your own custom class file and called by this business object. A typical use would be to call it from a type-based business object that overrides an object's setObjectName() method inorder to get a new object name.
|  |  | Component |
 |
|
Provides a service to generate unique numbers that can be used to number or name Docbase objects. The example shows a type-based business object that stores, increments and validates the number against a set of simple business rules. It also contains a service-based business object that shows how to call the type-based business object
|  |  | Component |
 |
|
This type-based business object (TBO) extends the checkin method of our 'dp_checkinwithlifecycle' object type and applies a lifecycle upon checkin. An XML configuration file is used to specify the lifecycle to be applied.
|  |  | Component |
 |
|
This service-based business object (SBO) is used to create a Docbase folder structure based on a template specified in a XML configuration file. The internal structure of the folder can consist of multiple folders and documents. The template to be used can be either defined in the XML configuration file of the SBO or supplied to the service by a method call that passes the Java Config class to the SBO.
|  |  | Component |
 |
|
This code implements functionality similar to the Microsoft Windows' Recycle Bin. A type based business object traps all calls to an object type's destroy() method and soft deletes objects; this behavior is independent of the client. Using a WDK component in Webtop, users can then view the recycle bin contents then restore, or permanently delete, the objects.
Updated March 2004 to include the version 1 BOConfig classes.
|  |  | Component |
 |
|
This service-based business object (SBO) provides an interface to send a rendition request for a document. The request is sent to Content Rendition Services (formerly AutoRender Pro).
|  |  | Component |
 |
|
This Webtop customization implements a document bin (aka shopping cart) to which users can add documents from the Docbase. The customization also includes functionality to create an archive package of the documents along with a manifest document.
To see the end results of using the document bin component see the 'Transmittal System Scenario' article which can be downloaded from the Component Exchange.
|  |  | Component |
 |
|
This service provides an interface to apply an XSL stylesheet to an XML document. It uses the DFC Transformation APIs to achieve its purpose and provides the result of the transformation as raw data that can be used by presentation layer for display. In the example provided, the output is saved to an HTML file.
UPDATED 31 March, 2005
|  |  | Component |
 |
|
This type-based business object (TBO) extends the checkin method of our 'dp_documentwithworkflow' object type so that a workflow is automatically started whenever a document of that type is checked in. The format of the document being checked in is used to determine which workflow is started. An XML configuration file is used to map content format types to workflow objects.
|  |  | Component |
 |
|
This type-based business object (TBO) checks in a document and performs a request for a rendition. This component is dependent on the service-based 'Rendition Service' business object.
|  |  | Component |
 |
|
Developers often have a need to export a Docbase folder including its
subfolders and content to the file system. Since this functionality is a common
requirement for several client applications, we wrapped it in a service-based
business object, (SBO) so that it can be called easily cross-platform and
cross-application. This SBO performs an export of a Docbase folder with its
internal structure and content to the file system. The folder structure can
contain virtual documents as well as simple documents and sub-folders.
Note: This functionality can be extended by using the 'Zip Service' business
object available from the component exchange. The zip service will take the
exported content and create a single zip file which can then be automatically
imported back into the Docbase.
|  |  | Component |
 |
|
With this service-based business object, developers can search the Internet and manipulate the results. The service uses the APIs provided by Google to access the Google search engine using a Web service.
|  |  | Component |
 |
|
This service-based business object provides methods to create templates, create documents from templates, search for templates and provide a listing of templates of a specific object type. It is used by the "Project Folder Creation" business object to populate the newly created folders.
|  |  | Component |
 |
|
This serviced-based business object (SBO) imports content from a specified URL into the Docbase. The service will attempt to 'guess' the object's format, object_name and title if they are not supplied.
|  |  | Component |
 |
|
The service-based business object (SBO) creates a zip archive file of a Docbase folder. It contains three utility methods. One will zip a file system folder structure and import the zip file into a Docbase. Another will export a Docbase folder structure including its content and zip it leaving the zip file on the file system. The third exports a Docbase folder structure with its content then zips it and imports the resultant zip file into a Docbase.
|  |  | Component |
 |
|
This Service business object(SBO) provides helper methods to attach/detach a
lifecyle and promote/demote all documents contained in a folder. One usage of
this SBO would be to invoke it from a workflow containing a folder as a package
to perform lifecycle-related operations on all documents in that folder. The
SBO is based on code submitted by David Hollister from CUNO.
|  |  | Component |
 |
|
This Service-based Business Object (SBO) allows the managing of MergeFields
inside Micorosoft Word Documents. The component allows update of MergeFields
with plain text or images from the repository. The SBO acts as a bridge between
Documentum Foundation Classes (DFC) and the WordWriter libraries from
OfficeWriter.
|  |  | Component |
 |
|
The ReplicationWrapper SBO allows the replication of Documentum object
attributes to remote data providers in an easy and transparent way. The
component permits extending its functionalities and the data providers
supported with the "DataSource" definition concept.
|  |  | Component |
 |
|
This code sample implements a 'Duplicate Object Name Checking Service'. It
is used to check whether a particular object name already exists in a folder,
if a duplicate object name is found then the code uses the Auto Naming Service
business object to change the new object name.
|  |  | Component |
 |
|
'DBORManage' is a utility for managing the Documentum Business Objects Registry. It allows you to register, remove and list the entries in the business object registry. This zip file contains the DBORManage jar file, the related JavaDocs, a set of batch files and an overview of both the Documentum Business Objects Registry and the DBORManage utility.
|  |  | Tool |
 |
|
In many of our examples we store our XML configuration file in the main Jar file. This application lets you edit these configuration files without having to first unpack the Jar file. The application will also edit standalone XML files and allow you to transform the XML content. It was written using the Eclipse Standard Widget Toolkit.
|  |  | Tool |
 |
| Business Process Manager (BPM) |
 |
|
The purpose of this article is to illustrate a convenient way to perform an XSL/T transformation as a part of an automated workflow activity. In addition to performing the transformation, this code provides a simple mechanism for configuring common business rules around how to perform that transformation, and where put the transformation results. For example, will the XSL come from a workflow package, or should we use the XSL associated with the XML via a dm_relation (the Web Publisher method)? Should we create a new rendition of the original XML object with the transformation results? Or should we create a new object? Should that new object be attached to the workflow? These are common requirements that in the past might have required the creation of a separate workflow method to solve each scenario.
With the introduction of 'Activity Templates' in Business Process Manager 5.2.5, we are able to create one single workflow method to implement all of this behavior, and a single Activity Template that can be used to describe which behaviors should be used in a particular situation.
|  |  | Article |
 |
|
This Modeler provides you a set of BPMN graphical objects with which you can
draw business process diagrams. Once completed, process flow diagrams can be
exported to XPDL, BPEL, or PAPX. Processes exported to PAPX, BPEL, and XPDL can
be imported into the Documentum Business Process Analyzer. Processes exported
to XPDL can be imported i |