Web Content Management with Documentum

Book Image

Web Content Management with Documentum

Book Image

Web Content Management with Documentum

Overview of this book

One of the world leaders in Enterprise Content Management, the EMC Documentum family of applications helps you manage all types of content across multiple departments within a single repository. With the Web Content Management suite of applications, you can efficiently manage content and underlying processes for your Web properties, and ensures that they are responsive to business needs. To fully realize the power of this system can seem daunting, but this book will help you achieve that. With easy to follow examples, this book will take you the simplest and most straightforward route to success. Along the way, you will learn insights that only a seasoned professional would know. Packed with practical examples, you will get hands-on with the powerful features of Documentum to grow your skills and confidence. You will see tips and tricks to handle complexities of the system, and avoid the common errors that waste your time. From installing and getting started with Documentum, you will see how to design and develop Documentum applications, before rounding off with deployment.

Web Content Management with Documentum

Web Content Management with Documentum

Credits

About the Author

About the Author

Acknowledgements

Acknowledgements

Preface

Free Chapter

Content and Documentum

Content and Documentum

1.1 Need for an Effective CMS

1.2 Qualities of a Good CMS

1.3 Why Documentum?

1.4 Documentum Features

Documentum Essentials

Documentum Essentials

2.1 Documentum Cornerstone

2.5 Object Types

2.9 Cabinets and Folders

2.10 Versioning

2.11 Lifecycles

Documentum Advanced Concepts

Documentum Advanced Concepts

3.5 Web Publisher

3.8 Users and Groups

3.10 Registered Tables

3.11 Data Dictionary

3.12 Methods and Jobs

Web Content Management System

Web Content Management System

4.1 When Should you Use a WCM System?

4.2 When Should you Not Use a WCM System?

4.3 Documentum WCM Architecture

4.4 How do you Enter Content in the System?

4.5 Where and How is the Content Stored?

4.6 How do you Perform System Administration?

4.7 How do you Create Multiple Renditions of the Content?

4.8 How do you Publish Content to a Website?

4.9 How do you Query the Published Content for Displaying on Websites?

4.10 How do you Deploy Website Content to a Server Farm?

Setting Up the Documentum Suite

Setting Up the Documentum Suite

5.1 Installing Content Server

5.2 Installing Content Server 5.2.5

5.3 Installing Content Server 5.2.5 SP2

Creating Our First Docbase

Creating Our First Docbase

6.1 Creating a Docbase

6.2 Installing Web Publisher Server Files and DocApp

6.3 Beginning Installation

6.4 Stopping and Starting Docbase and DocBroker

Setting Up Publishing

Setting Up Publishing

7.1 SCS Source 5.2.5

7.2 SCS Target 5.2.5

Setting Up Documentum Application Builder

Setting Up Documentum Application Builder

8.1 Documentum Application Builder

8.2 Installing DAB 5.2.5 SP2

Setting Up Documentum Administrator and Web Publisher

Setting Up Documentum Administrator and Web Publisher

9.1 Documentum Administrator

9.2 Web Publisher

Designing Documentum Applications

Designing Documentum Applications

10.1 Case Study—Simple Newspaper Website

10.2 Beginning Documentum Design

10.3 Using Documentum Application Builder (DAB)

10.4 Creating Custom Objects in DocApp

Designing and Creating Custom Object Types

Designing and Creating Custom Object Types

11.1 Creating Object Types

11.2 Designing and Creating Custom Attributes of Object Type(s)

11.3 Adding Attributes to an Object Type

11.4 Querying Registered Tables using DQL for Value Assistance

11.5 $value() Keyword

Creating Lifecycles, Alias Sets, and Permission Sets

Creating Lifecycles, Alias Sets, and Permission Sets

12.1 Alias Sets in a Lifecycle

12.2 Creating an Alias Set

12.3 Creating Permission Sets

12.4 Creating a Custom Lifecycle

12.5 Promoting and Demoting Content through a Lifecycle

12.5 Expiring Content

Working with Web Publisher Template Files

Working with Web Publisher Template Files

13.1 Creating a Template File

Creating Rules Files

Creating Rules Files

14.1 Creating a Rules File

14.2 Final Template in Web Publisher Editor

14.3 Miscellaneous Rules File Widgets

Creating Presentation Files

Creating Presentation Files

15.1 Creating a Presentation File

15.2 Viewing Content Renditions

15.3 Reapplying Presentation Files

15.4 Using XDQL in Stylesheets

15.5 XDQL Example in XSL Stylesheet

15.6 Create_Dynamic_Content Job

Folder Mapping

16.1 Anatomy of the FolderMap.xml File

16.2 Limitations of Folder Map

16.3 Folder Mapping Examples

Using Instruction Files

Using Instruction Files

17.1 Limitations of Instruction Files

17.2 Instruction File Examples

Automatic Property Extraction (APE)

Automatic Property Extraction (APE)

18.1 How Automatic Property Extraction Works

18.2 Simple Example for Automatic Property Extraction

18.3 Testing our First XML Application

18.4 Populating Repeating Attributes using Automatic Property Extraction

18.5 Testing the Second XML Application

18.6 Using Two-Way Attribute Extraction

18.7 Testing the Two-Way Attribute Extraction XML Application:

Working with Workflows

Working with Workflows

19.1 Designing Custom Workflows

19.2 Setting Up a Custom Workflow Template

19.3 Creating a Custom Workflow Template

19.4 Adding a Package to Connection Flows

Testing Custom Workflows

Testing Custom Workflows

20.1 Creating Users for Workflow in Documentum

20.2 Submitting Content to the Custom Workflow

Publishing from Docbase Using SCS

Publishing from Docbase Using SCS

21.1 Limitations of SCS

21.2 Publishing Types

21.3 Steps for Setting Up a Site Publishing Configuration

21.4 Testing and Publishing Using Site Publishing Configuration

21.5 Published Data

21.6 Unlocking Locked Publishing Operations

21.7 Monitoring the SCS Source Status

Web Viewing Content Files

Web Viewing Content Files

22.1 Prerequisites

22.2 Setting Up and Using Web View

22.3 Testing Web View

Using DFC

23.1 Introduction to DFC

23.2 Environment Readiness

23.3 Simple Example Demonstrating DFC Usage

23.4 Creating and Linking a File in a Docbase Cabinet

23.5 Running Docbase Methods via DFC

23.6 Creating Users in Docbase with DFC

Configurations and Customizations Using WDK

Configurations and Customizations Using WDK

24.1 WDK Directory Structure

24.2 WDK Application Elements

24.3 A Simple WDK Configuration Example

24.4 A Simple WDK Customization Example

Documentum Deployment

Documentum Deployment

25.1 DocApp Migration

25.2 Configuring DocApp Objects and Creating/Installing a DocApp Archive

25.3 Deployment of Web Publisher Code and Custom Scripts

Using DQL and API Commands

Using DQL and API Commands

Frequently Asked Questions and Answers

Frequently Asked Questions and Answers

New Features and Enhancements in Release 5.3

New Features and Enhancements in Release 5.3

B.1 Content Server Changes

B.2 Object Types Changes

B.3 API and DQL Changes

B.4 DFC Changes

B.5 BOF Changes

B.6 Application Builder and Application Installer Changes

B.7 WDK Changes

B.8 Documentum Administrator Changes

B.9 Web Publisher Changes

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

7.2 SCS Target 5.2.5

We will first install SCS Target software on the web server machine and then apply the SP2 pack over it.

7.2.1 Prerequisites

Figure 7.7 lists some of the prerequisites for installing SCS Target on the web server host:

Entity	Comments
SCS Target installation owner	On Windows machines, the user should: Be a member of Windows 'Administrators' group Have "act as part of operating system" privilege (Go to Programs \| Administrative Tools \| Local Security Policy ) Have access to the SCS directories
Transfer user	User name and password for a valid OS user on the SCS Target machine should be known
Web Server	The web server for application servers or web applications should be up and running
Database	If configured with SCS Target software, the database instance should be accessible User name and password for Database connectivity should be available DB system user name and password should be available for allowing Site Caching Services to create database/tablespaces.
Hardware...