Documentum Composer 1.

September 14, 2007

© 2007 EMC Corporation. All rights reserved. 1

Agenda

y Introduce Composer 1.0

y Screenshots
y Extensible plug-in model
– Introduction
– Use Cases
– How to

© Copyright 2007 EMC Corporation. All rights reserved. 2

Composer 1.0

y Eclipse-based IDE
y Industry-standard
platform
y Open & extensible
through plug-ins

© Copyright 2007 EMC Corporation. All rights reserved. 3

Composer 1.0

y Users
– Internal Software Developers
– Customers, Systems Integrators
– Partners

y Enables Documentum Application Lifecycle

– Build
– Customize
– Deploy
– Migrate

© Copyright 2007 EMC Corporation. All rights reserved. 4

Composer D6 Product Roll-out Plan

Artifact DAB/DAI Composer LD Composer GA – D6 SP1

Type 9 9 9
Relation Type 9 9 9
Modules 9 9 9
Java Lib 9 9 9
JAR Def 9 9 9
Folder/Cabinet/Sysobject 9 9 9
Procedure 9 9 9

Aspects 8 9 9

Web Services 8 9 9

Format 9 8
Method 9 8
Sep-07
Life Cycle 9 8
Permission Set 9 8
Group/Role 9 8
Workflow 9 8 Oct-07

Forms 9 8
Alias Sets 9 8
Job 9 8 Nov-07

XML app 9 8
DTC Customization 9 8 8
© Copyright 2007 EMC Corporation. All rights reserved. 5
Composer Plug-ins

y Real power of Composer is the extensible plug-in framework

y Intended users
– Customers and SI’s with a base application, and many customized
versions deployed
– Partners in “Designed for Documentum” program

© Copyright 2007 EMC Corporation. All rights reserved. 6

 Composer Screenshots

© Copyright 2007 EMC Corporation. All rights reserved. 7

© Copyright 2007 EMC Corporation. All rights reserved. 8
© Copyright 2007 EMC Corporation. All rights reserved. 9
© Copyright 2007 EMC Corporation. All rights reserved. 10
© Copyright 2007 EMC Corporation. All rights reserved. 11
Composer Plug-ins

y Your base application consists of:

– Documentum artifacts
• Customizable types
• Java classes (via TBO)
• Web Services (via DFS)
– Your artifacts
• Other code
• UI elements (JSP pages, CSS)

© Copyright 2007 EMC Corporation. All rights reserved. 12

Composer Plug-ins: Customers and SI’s

y For customers or SI’s, custom application means:

– Copy code base
– Modify specific code
– Build, test, deploy
y Results in multiple copies of a code base
– Difficult to maintain
– High level of knowledge required for customization
y Build a plug-in!
– Design editors to customize specific areas
– Configure application and build

Result: Rapidly deploy custom applications

© Copyright 2007 EMC Corporation. All rights reserved. 13

Composer Plug-ins: Partners

y For partners, customizing your application means:

– Knowledge of Documentum artifacts
– Customers learn a different tool set
– Unique steps for build, install, migrate

y Build a plug-in!
– Offer customers higher level of abstraction for customization
– Unified development and deployment environment

Result: Rapidly deploy custom applications

© Copyright 2007 EMC Corporation. All rights reserved. 14

Composer Plug-ins

y Eclipse and Composer provide the infrastructure for

additional plug-ins

y Plug-ins consist of:

– Metadata model
– UI
– Event overrides
• Build
• Install
• Validate

© Copyright 2007 EMC Corporation. All rights reserved. 15

Custom Plug-in Example

y Your base pharmaceutical application consists of:

– Documentum artifacts
• 3 configurable types
– Add or delete attributes
• 2 configurable lifecycles
– Attach one of two lifecycles to each type
• 3 JSP pages
– Show or hide menu options and tabs

y Use a plug-in to:

– Configure types and lifecycles
– Specify UI options
– Build application
– Deploy

© Copyright 2007 EMC Corporation. All rights reserved. 16