Can we programatically associate a Content.xml from one template to another template?

Ravikanth

Can we programatically associate a Content.xml from one template to another template?

We have done a redesign of our webcabinet and copied the whole content to a new web cabinet. Now we want to associate each of the content.xml to a new content template.

We can do this manually, but it will take some good amount of time. So, can it be done programtically.

Ravikanth

I am adding this information to make myself clear.

We have upgraded to Documentum 6.5 SP1 and also have plenty of WebCabinets in our repository.

As a part of revamp, we are reorganizing the cabinets. Which itself is a big task. We have created a new web cabinet, which is a combination of two or more websites and is concise. Now, the templates are still pointing to the old cabinets. We have already created the templates for the new webcabinet and would want to point all the files in the new web cabinet to point to the newly created templates. As such, we have plenty of files and going through each one and pointing to the new template will become very tedious. We tried to do this programmatically. Initially, we tried to manipulate using DQL. We found that we have a table called dm_relation. Which connects the Content to the templates using i_chronicle_id. We updated these rows to point to the new templates. But, it was not much of a help. It didn’t work. Then we tried the WDK way. We made a WcmContent object of the document and tried doing the following way – IWcmContent myWcmDoc = (IWcmContent) appContext.getObject(new DfId("090000018024fd0d"),                    (IWcmContent.class).getName(), theSession);                                    System.out.println("my doc name"+ myWcmDoc.getObjectName()); myWcmDoc.removeAllLayoutTemplateIds();myWcmDoc.setLayoutTemplateId(new DfId("0900000180282f2e"), "WCM_LAYOUT_TEMPLATE", "en_US", "html.HTML Document"); This did compile and also executed with out error. But still nothing much happened. The Content file is still pointing to the old templates. The next way we had is to export the file and import it back. While Importing it back, associate it with the new template. Similar to the way we do it in WP. But, we wanted to know, if this can be done programmatically. We are aware of the Object ids etc. that are needed. Is it possible to do in this way? What is the easiest way out? Any kind of help is appreciated.