Composer is based on the Eclipse Integrated Development Environment (IDE) and thus adopted a similar terminology to comply with the Eclipse guidelines. The following table describes some of the new terminology that is used in Composer and relates it to the terminology that was used in DAB.
|
Composer Terminology |
Description |
DAB Terminology |
|
Artifact |
A component of an application, such as an alias set, lifecycle, or method, packaged into a project. |
Repository object |
|
Project |
A project contains the components (artifacts) that make up an application. A project resides on the local machine. |
DocApp |
|
Workspace |
A directory on the local machine which contains the project’s artifact files. A project must be imported into a workspace before you can build, update, or install it. As a best practice you should set up at least three separate workspaces, as follows: • One workspace for UI‑based Composer projects. • One workspace for importing and build projects using headless Composer. • One workspace for installing DARs using headless Composer. |
Repository |
|
DAR |
This file is the installable binary file that is created by building a project. The file cannot be modified directly. |
DocApp Archive |
UI-based Composer
The Composer GUI should be used for all development tasks, such as developing an application from
scratch or modifying an existing project. You also need to use the Composer GUI for importing
5.3 DocApps and DocApp archives.
Note: You cannot import a DAR file into Composer. A DAR file is similar to an executable file. It
contains only the binary code and no source files.
Headless Composer
Headless Composer is most useful when you do not want to make any changes to a project but want to
automate compiling an existing project and installing the DAR into a repository.
Note: Headless Composer cannot be used to create new projects or new artifacts.
Reference:
Documentum strongly recommends users of DAB and DAI to migrate to Documentum Composer.
Documentum Composer is an Eclipse‑based toolset used to create Documentum applications.
Documentum Composer 6.5 contains new features including a DFS Service Catalog Viewer,
and Smart Container. In future, all new Documentum Platform features will be exposed through Documentum Composer.
Information on Documentum Composer 6.5 is in the Documentum Composer Quick Start Guide, version 6.5 and Documentum Composer User Guide, version 6.5.
“I must say my first experience with the Documentum Composer (very much awaited by me and my
team-mates) wasn’t as much pleasant as I wanted it. At first the software seems *very* buggy -
attributes names kept disappearing when I navigated away from the page, sometimes the
workspace would crash for no reason…
As one of my colleagues said – “you have to do things in the exact order they should be done. No
going back for checking that “repeating” check-box anymore”. I really hope they will improve this as
it will be the only tool available to create your application’s model (and it’s the only tool that works
on Windows Vista).
I completely accept your comment, I was really excited when composer 6 was initially launched ..
but that didnt last for a very long time, it corrupted my repository, Even the EMC support team
couldn’t find out what was the exact issue, luckily it was my testing repository so there was not
many damages. Even with the 6.5 Composer I was getting lots of issues and now i am using
Application builder SP 6.5<Dan’s comments: I haven’t found this patch in DCTM’s sites, but DAI 5.3 SP2 or above is supposed to support DCTM 6.*.
Woody used DAI 5.3SP6 for Pyramid upgrade>,
Even EMC Support suggested me to use this, I really hope to see a bug
free composer soon”
porrfilmer…
[...]Documentum Composer | UKoom[...]…