Upgrading from (D6.6 + xCP1.5) to (D7.1 + xCP2.1) environment

Hi All,

I am very new to xCP tools.

We have a project where customer is on D 6.6 + xCP 1.5 and wanted to move to D7.1 + xCP 2.1.

What i have seen in the fourms that first I have to upgrade all existing DCTM products to D7.1.

So my questions are :-

Can i directly upgrade from xCP 1.5 to xCP 2.1, if yes what are the high level steps, any documentation will be very helpful.

If no, then what is the best possible approach.

Can you please provide me details about it?

Regards,

Rohit Madar

Find more posts tagged with

Comments

jsilver

The are your best bet.

One thing that may not be clear - there is currently no direct migration from xCP 1.x to xCP 2.x because of fundamentally different architectures. However, xCP 1.x is supported on Documentum 7.x. See the comments to for more information.

rohitmadar1

Thanks for your reply Jerry!

I now understood that there is no direct way but the good part of our environment is that we are on D6.6 with below tools.

BPS, Content Server, CTS, DFC, DA, TaskSpace, MWS, Webtop, xPlore, IDS and DAM.

In first step, customer wants 6.6 to 7.1 in place upgrade, which i think is the stright forward.

In second step, we need to move from xCP 1.5 (Taskspace , form builder and process builder) to xCP2.1. So my question is, can we only create frontend, workflows with forms in xCP 2.1 and can we leverage rest of the 7.1 environments.

Or do we have to create all object types, roles, groups, users, acls in xCP 2.1 environment followed by content migration?

Regards,

Rohit Madar

rohitmadar1

While going through documentations, I have understood that we first have to move from 6.6 to 7.1 and then we have to check xCP 2.1 product suites. Then we have to only installed mandatory tools which are not available in 7.1 environment. Then we by using xCP designer we have to develop new forms, workflows and application (client frontend).

Kindly correct if I am wrong in above understanding.

Another point which i was trying to understand is, I have understood that we can simply use the AS-IS object model by using type adoption feature. But if there will be any change required in the existing object type then first we have to import that object into xCP designer and then need to change it. But in this case, prefix would be added in it and it would be considered as a new object type in repository.

Kindly correct if this understanding is wrong.

Apart from it, we can be able to use other objects of the repository in xCP 2.1 without any change required like groups, users, jobs, methods, permission set, alias etc. Please correct if this is not correct.

Kindly provide your assistance.

Regards,

Rohit Madar

Malthi

Hi Rohit,

Correct, the content server needs to be upgraded first. After this when you upgrade the application, the object model/types can be migrated. With type adoption you can adapt the type in xCP and further modify. Please do not delete any attribute else it may break other applications and will not support interoperability. Even if the type is modified in xCP, it can continue to be used as-is in any other client application consuming that type.

The UI and process part of the application needs to be redone.

The user management is not affected as it is still done in DA.

Hope this helps.

Best Regards

Malthi

ricardobacelar

I'm doing a migration from version 6.6 to version 7.1, but I will first go through version 6.7 SP2 and then I migrate to version 7.1;

I believe it is a path that I find less problems.

rohitmadar1

@Malthi,

Ok based on your response, it seems that after using type aduption we can even modify the object in xCP 2.1 designer and can load it into repository. But need to clarify one thing here, what i have read that xCP 2.1 would add prefix in the starting which might create malfunctioning in the repository. Is this correct?

Regards,

Rohit Madar

Malthi

Hi Rohit,

That is correct that you can continue to use the existing type with type adoption. xCP does not add any prefix in type adoption. In other cases when you want to create a copy of a type using "Import type from Composer project" then a prefix is added and it can be then only consumed in xCP 2.1 app.

Hope this helps.

Regards

Malthi

rohitmadar1

Thanks Malthi,

does it mean that after using type adoption, if there is any change required in the object model like adding new custom attribute in one type, then i first need to import object into composer 6.7 SP2 and then once I will load it into repository, prefix will be automatically added in front of object type.

If this is correct, then it means in case of any change with the object type, new object type will be created, there is no possibility of existing object type change. Please correct.

Regards,

Rohit Madar