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.13 Summary

In this chapter we talked about Content Server, the backbone of Documentum architecture, hosting Docbases. A Docbase can be thought of a logical repository, consisting of content files and their associated metadata. A DocApp, on the other hand is a packaging unit of a Docbase, consisting of objects from the Docbase.

We went on to discuss DocBrokers, which act as an intermediary allowing clients to make connections with Content Servers.

We saw how the Documentum system treats all entities in the form of objects. Objects can be treated as run-time instances of templates called object types in Documentum. Objects in Documentum have their own metadata, which is termed properties or attributes.

We saw an example of using DQL (Document Query Language) and Server API commands to query and manipulate objects in the Docbase.

We also touched upon the versioning capabilities of Content Server and had a brief introduction to lifecycles and workflows. While lifecycles represent the logical stages...

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.13 Summary

Unlock this book and the full library FREE for 7 days

Personalised recommendations for you