Moving artifacts with composer, how does it work?

Hi Experts,

I have very interested in the way composer moves artifacts from one repository to another.When we move for example a process template from one repository to another in a dar file, composer is smart enough to find the process.And actually it finds and updates the process in the target environment. The process names are not unique, the r_object_id-s are always different so how it finds them?How composer knows whether create or update existing artifact?

Please share your knowladge.

Thanks in advance

Find more posts tagged with

Comments

tejrajs

for each artifact, you can specify the upgrade option whether to create new version,overwrite matching or ignore (by selecting artifact Properties->Documentum Artifact option)

DCTM_Guru

"The process names are not unique"

- So do you actually change the process template name after its been installed with Composer on target repository?

Imran_Yusubov

Hi,

tejrajs

,Thank you for the information.

Johnny Gee,

No Johnny I am not trying to do anything.What I am really asking is that if I create a process template in source repository and move it to target for the first time it will be created, so far everything is clear to me.

But if I modify the process template in source docbase and move it again with composer to the target environment, composer behaves very clever, it finds the process template and updates it instead of creating a second process template.The question is that , how it does that? Where does it know that it is not a new template actually it is one that already exist here and have been modified in the source docbase so I should update it instead of creating a new process template.

DCTM_Guru

I believe it just looks for the object name of the process (it assumes that it is unique in the application). Like you said, it can use object ID since IDs will be different for docbase. The installation behavior is dictated based on the settings you defined as tejrajs described.

I dont know if this behavior works as expected if you install two different processed (with the same process name) in two different application (each with its own application folder).

lastnitescurry

Imran wrote:But if I modify the process template in source docbase and move it again with composer to the target environment, composer behaves very clever, it finds the process template and updates it instead of creating a second process template.The question is that , how  it does  that? Where does it know that it is not a new template  actually it is one that already exist here and have been modified in the source docbase so I should update it instead of creating a new process template.

I always assumed that a Composer project docbases container acts like a virtual document. Hence It does not matter what the names are, as long as you update the process with the same Composer project. At a guess if you imported the process into a 2nd Composer project and installed that, you would now end up with two process in your target repository

tejrajs

I believe this is not the case. This also depends on how you set "Location" property for an artifact under Documentum Artifact property in addition to "Upgrade Option".

By default this property is default set to "DAR Install Folder" which is usually different for different composer project, however if you point "Location" to same location in docbase even in different composer project then depending on how you set "Upgrade Option" the artifact gets installed.