Packt+ | Advance your knowledge in tech

You're reading from Web Content Management with Documentum Setup, Design, Develop, and Deploy Documentum Applications

Product type Paperback

Published in Jun 2006

Publisher Packt

ISBN-13 9781904811091

Length 484 pages

Edition 1st Edition

Languages

Java

Tools

Documentum

Concepts

CMS

Table of Contents (33) Chapters

Web Content Management with Documentum

Credits

About the Author

Acknowledgements

1. Preface

1. Content and Documentum FREE CHAPTER

2. Documentum Essentials

3. Documentum Advanced Concepts

4. Web Content Management System

5. Setting Up the Documentum Suite

6. Creating Our First Docbase

7. Setting Up Publishing

8. Setting Up Documentum Application Builder

9. Setting Up Documentum Administrator and Web Publisher

10. Designing Documentum Applications

11. Designing and Creating Custom Object Types

12. Creating Lifecycles, Alias Sets, and Permission Sets

13. Working with Web Publisher Template Files

14. Creating Rules Files

15. Creating Presentation Files

16. Folder Mapping

17. Using Instruction Files

18. Automatic Property Extraction (APE)

19. Working with Workflows

20. Testing Custom Workflows

21. Publishing from Docbase Using SCS

22. Web Viewing Content Files

23. Using DFC

24. Configurations and Customizations Using WDK

25. Documentum Deployment

26. Using DQL and API Commands

Frequently Asked Questions and Answers

New Features and Enhancements in Release 5.3

2.2 Docbase

Docbase should be thought of as a huge centralized repository that stores content and metadata in the form of 'objects' and their properties.

Metadata for the content is nothing but the different attributes that describe the content; for example its owner, creation date, version number, etc.

Some attributes can be 'single-valued' having just one value, for example the name of the content, while others can be 'multi-valued' having multiple values, for example the keywords describing the content.

Documentum relies on the underlying RDBMS to store the metadata for various objects in various tables. On the other hand, the content files for the numerous objects are stored in any of these storage types:

The host server's OS file system
In an RDBMS as BLOBs (Binary Large Objects)
A content storage device (for example: EMC Centera)
An external system outside Documentum's boundaries

Additionally, Content Server has an embedded full-text search engine, Verity, and so the Docbase repository contains...

The rest of the chapter is locked

You're reading from Web Content Management with Documentum Setup, Design, Develop, and Deploy Documentum Applications

Table of Contents (33) Chapters

2.2 Docbase

Unlock this book and the full library FREE for 7 days

Personalised recommendations for you