Using EMC Documentum Composer: Pitfalls, Best Practices and xCP Deployments: EMC World Developer Tra

Hi all,

In addition to an XML session, I'll also be leading a Composer session at EMC World. As the title implies, I intend to talk about best practices and pitfalls when using Composer, as well as walk through the steps of packaging and deploying an xCP application. I've attached the official session abstract and takeaways below. If there are any other areas that you'd like to see address, please feel free to let me know by posting to this discussion thread.

Thanks!

Abstract:

You may know Documentum Composer as a Documentum development tool, but did you know that it is also used to deploy xCP Applications? First, come learn about common pitfalls, and how to avoid them by following best practices. Then learn about using Composer for packaging and deploying xCP applications

Takeaways:

Learn how to more effectively use Documentum Composer
Learn how to use Composer for xCP application deployment

Find more posts tagged with

Comments

Colin_Hewertson

Hi David,

I'm looking at the general area of xCP and in particular case management. However I must admit to being little confused, aren't the discreet artifacts contained within a single DAR considered as accelerators (I certainly wouldn't recreate types I wanted to use them). The concept I can see being presented through something like Smart Containers, which in principle uses the artifacts contained in the DAR to build an end to end process although you still have to define the logic.

So as someone who will be actively using the mechanism of xCP over the coming months I would greatly appreciate some guidance on best practice, resources (Javadocs for Smart classes wouldn't go amiss) and perhaps more importantly a development road map for composer. Perhaps a discussion group for xCP with topics such as Smart Containers?

Regards

Colin

DCTM_Guru

Hi Colin,

Artifacts are the individual components that are assembled to build an accelerator. I would define an accelerator as backend configuration objects (eg object types, workflow templates, forms, etc), taskspace UI/app, and possibly BAM reports. Basically various components of xCP product line that would be use in a transactional application.

-Johnny

Colin_Hewertson

Hi Johnny,

Thanks for the prompt reply, I've just read my original post and perhaps I need to elaborate, a collection of discreet atrifacts in a DAR could be considered an accelerated application. For instance I have an Enterprise Core DAR, a Community DAR's and multiple solution DAR's that could be combined into one or used separately/developed. So in a sense I'm creating my own accelerators.

So if I understand it xCP products are basic assemblies that can be taken and worked upon to provide customer soultions and may include not only DAR elements but other content and configuration too?

The grey area for me is around Smart Containers which seems to sit somewhere between the traditional docapp and BPM with a little more blurring with David's comment regarding the deployment of xCP products using Composer. You only have to search for Case Management to see that there are several ways of approaching a solution.

As I said, clarification around the bigger picture would be good considering there such a wealth of information now coming from EMC and the user community too.

Regards

Colin

david.louie

Hi Colin,

Your observation that there appears to be multiple technologies within Documentum that could be used to model a case in Case Management is a good one. I know that right now, the xCP team is not leveraging Smart Containers. Let me ask around to see what the recommended approach is for modeling case components, relationships among case components, and business logic on top of case components.

Thanks,

Dave

ming62

Hi David,

We are looking for advice on regular composer best practice. Do you have any information on that?

Thanks,

Ming