About Documentum Composer and existing productive settings

ArthyTrip · 2021-12-03T15:55:03+00:00

There was an error rendering this rich post.

Hi all,

I would like to consolidate the objects of an already existing Documentum installation (production environment) into one or more Composer projects, to have more control and precision on the next evolutionary deployments.

Before proceeding to import in Composer the existing artifacts I would like to be absolutely sure that a subsequent installation via Composer or DarDeployer will not be destructive.

I have already experimented several times with the use of Composer with Type artifacts but, for example, never with Groups or Permission Sets. In the latter case I have a doubt.

By reinstalling Groups and Permission Sets, are you sure that the already existing relationships between - for example - Groups and Users are preserved? Or reinstalling Groups deletes those relationships?

Thanks.

Find more posts tagged with

Comments

DCTM_Guru

If you right mouse click on the object and select properties, under Documentum Artifact, there is picklist called upgrade options. Here you can decide whether you want to 1) overwrite matching objects, 2) ignore matching objects, or 3) create new version (which would not apply to groups/ACLs).

ArthyTrip

Do I have to deduce that if I select "overwrite matching objects" for Groups artifacts, these are destroyed and recreated thus losing the assignments with users?

The doubt arises because I normally use "overwrite matching objects" on Types artifacts and the installation is not destructive, ie not only the objects (DB information) but also the relationships, permissions, etc. between objects are preserved.

DCTM_Guru

I dont think group membership gets overwritten, but I have always used ignore matching for groups.