Академический Документы
Профессиональный Документы
Культура Документы
Documentum Architecture
Interface Layer
Web Servers Clients and applications use the interface layer to communicate with
Content Server and interact with the content repository. The interface layer consists of
Documentum Foundation Classes (DFC) and a number of standard interfaces built on top
of DFC.
Web Services
DFC and BOF enable developers to encapsulate custom business logic that can be
exposed as Web service. They provide a way to call functions on other computers across
the intranet or World Wide Web. For example, a CRM system can communicate with
Documentum through Web service. For Documentum customers, this means broader,
industry standard access to content management functionality.
Developers can create their own service on our platform. Developers work with their
preferred development environments, toolkits, and application servers to develop Web
services over the Documentum API. Web services can be deployed on a Web server,
where they are available to any networked client a desktop application, a Web application
or portal, or even another Web service or remote client/system.
Standard interfaces
Documentum provides a number of standard interfaces in addition to the DFC API,
simplifying access to the repository from authoring applications, application servers, and
other components of the enterprise infrastructure.
The standard interfaces include:
• ODBC and OLEDB Many reporting tools, such as Crystal Reports and Microsoft
Access, leverage Microsoft data access protocols for communicating with the
Documentum repository using Documentum ODBC Reporting Services.
• JDBC Many application server applications use the standard Java data access protocol
to access content in the Documentum repository through Documentum JDBC
Services.
• WebDAV Documentum WebDAV Services provides a WebDAV server that enables
WebDAV-aware applications, such as Adobe Photoshop and Documentum Desktop
for Macintosh, to use this protocol to communicate with the Documentum repository.
• FTP Documentum FTP Services is a FTP server for the Documentum repository that
enables tools such as Macromedia Dreamweaver to integrate with the repository using
the Internet-standard file transfer protocol.
Client Layer
The client layer consists of basic applications for users to access the Documentum
repository. It includes end-user interfaces, administrator tools, and integrations with
popular authoring tools and enterprise applications.
Applications on the client layer are built from reusable components that build on the
content management service available from lower layers in the architecture. A
Documentum client application is a collection of components that work together to fulfill
a business purpose. The same components may appear in other client applications or as
Portlets in an enterprise portal. Because components of both Microsoft Windows-based
applications and Web-based applications share the repository’s data dictionary and
business objects, developers and users can be sure of consistent results from all client
applications.
Application Layer
Content Services Integration with Enterprise Applications
Documentum offers several products that enable interaction with the Documentum
content management system from within other enterprise applications. Among the
products are:
• Documentum Content Services for SAP
• Documentum Content Services for Siebel e-Business Application
• Documentum Content Services for Lotus Notes Mail
• Documentum Content Services for Portals
Also available are Content Service products for delivering content to various application
server, such as BEA Web Logic and IBM Web Sphere.
Content Services links content in Documentum repositories with objects in the enterprise
application, providing users with access to key Documentum functionality using the
familiar interface of the enterprise application, eliminating the tune and costs associated
with searching for, filing, and storing documents. For example, an accounts payable clerk
using an SAP application can instantly see a vendor’s contract, invoice, purchase
requisition, and paid check from a single click on an SAP transaction report. Project
managers can review standard operating procedures, material safety data sheets,
engineering drawings, and specifications from within an SAP material master form.
Key Features
Security
Documentum provides better security than a file system. With a file system, if someone
has access to your hard drive, they can pretty much read, edit, and even delete any file on
the hard drive. With Documentum, you can prevent any individual user (or group of
users) from seeing the file. In fact you can give Joe access to read the file but not change
it while Bob can change it but not delete it, while Fred can’t even see that it exists.
Version Control
In Documentum, each time you make a change to a file, it gets saved as a new version of
the file, and you can go back in time and access any old versions.
Search Engine
You can search Documentum like you search the web by looking for a certain word or
phrase in every file. But Documentum is even better than that. You can assign attributes
(also called meta-data or properties) to the document. For example, you can specify a
document’s author, title, subject, and any number of keywords to describe it. You can
even make up special attributes - if the document is a report, you can put in the report
number or if the document is a letter, you could enter the date the letter was written. Then
if someone is looking for the file and they know the report number or the date the letter
was sent, they can bring it right up. Of course, you can do wild card searches and date
range searches (for example, give me all the letters written last month that have the word
computer in the subject).
Workflow
You can route documents around for approval inside the Documentum system. Each user
has his own inbox that shows all the files that he needs to look at. You can approve the
file or reject it, and you can have a whole approval process where it goes to your boss
first and then to his boss, etc. It’s kind of like email, but it’s more automated and it keeps
track of everybody’s comments and who approved it when.
Lifecycles
A lifecycle in Documentum defines a chain of states that a document can pass through
during its lifetime. Each state has a name, like “Draft”, and can be configured to perform
certain actions as documents enter or leave it. Lifecycles can be built, maintained, and
packaged for deployment using Documentum Developer Studio. Lifecycles should not be
confused with workflows which route tasks among users and are built using
Documentum Workflow Manager
Virtual Document
A virtual document is a document that contains components or children documents. A
virtual document is similar to a folder. When you open a folder, you see the objects inside
that folder. When you open a virtual document, you see the objects inside that virtual
document. The main differences between a folder and a virtual document are that a
virtual document can have content (a folder cannot), and a virtual document can be
versioned-version 1.0 can have three children while version 1.1 can have five children
and version 2.0 has no children at all (in which case it is just a normal document).
Documentum WebTop
WebTop is a WDK based application. A WDK based application is built on WDK (Web
Development Kit) functionality. A WDK based application lets you access an EMC
Documentum repository over the web. WDK functionality lets you access, edit, and
manage content in multiple repositories. WDK functionality lets you distribute content
through automated business processes, restrict access to content according to permission
sets, and assign version numbers to content to help keep track of revisions.
A repository is a virtual storehouse for the content you work on, and share with other
employees. Each repository provides security, tools, and processes for sharing content
among many users. Processes control the automated routing of content, and assign
document Lifecycles to content. Processes allow you to create, edit, and forward content
regardless of your technical expertise.
A repository stores two kinds of information for a content file:
• The content, which is the text, graphics, sound, video, binary content, or other content
that makes up the file.
• The properties, which are descriptive characteristics about the file, such as creation
date, author, version number, and other information. Property values can only be
edited by the file’s creator or a user with high enough security settings.