CMS Sync Tool

If you are using multiple Open Text Web Solutions Management Server with the same projects you face the problem to keep the projects synchronized. An easy Dev/QA/Production environment already has three servers to keep in sync. Also a migration from Management Server 9 to Managment Server 10 can be hard work if you need to do adjustments to the projects during migration.

Scenario 1 - Dev/QA/Production:

The development of new functions and problem solving happens on the development server (Dev). After the development is finished the changes are moved to the test server (QA). Finally during the release process the changes are moved to the production server (Prod).

Every single step could introduce errors as every change has to be moved (new elements, element changes, template changes, etc.). Even more complex migration becomes if not every single change shall be moved because there are required differences between the environments.

Scenario 2 - Migration to newer version:

The migration to a new version of the Management Server (e.g. version 9 to 10) requires many tests of existing projects. Very often changes in the content classes are required to that there are differences between the different versions that cannot be migrated back. At the same time there are changes on the old server that needs to be migrated to the new server.

Only in a few situations the projects can be frozen during the migration. As soon as complex parent/child-projects exists it is nearly impossible to freeze the project work at all. This leads to projects that differ more and more between the servers.

Using the CMS Sync Tool

With the CMS Sync Tool you can synchronize the projects between multiple servers. This is especially important for content classes. Mapping the content classes is semi-automatic. This means the tools tries to find the mapping and suggests you the changes to be done. You can choose which changes you want to migrate. There is no need to have the same GUIDs between the content classes.

In the next step the content classes are compared. Both, the elements and the templates are compared to each other. Every single change (attributes of elements and single lines in templates) can be migrated or ignored. Even full content classes can be migrated, ignored or deleted.

All steps are done in a browser and there is no need for an installation on the clients. Just use the CMS Sync Tool where you use the Management Server.

If you are interested we are happy to show you how to use the CMS Sync Tool and provide you with a demo version.