Source Configuration Management in MII - How to do it?

Hello experts,

I have a general question related to how do you keep track of the different versions of a system developed in MII.

MII is proposed to be used in multi-plant scenarios, where each plant has a local MII server running the application. With this type of scenario usually comes the need for some kind of Configuration Management, to make sure that you control the different versions of the application that you have running in each plant. This is a simple scenario, but there could be still a lot more to it, such as code branching.

From my experience in MII, I don't know of any native support for version control. One option that I've tried to work with was exporting the project files and using a third party version control system (such as CVS or SVN), with not much success. The transaction files are XML, but usually come as a single line file. That makes it impossible to compare file versions and even if you run a XML formatting tool before commiting the files, you would have to understand the MII XML structure to do a version compare/merge.

Has anyone used any other type of Source Configuration Management in MII with success?

Thanks,

Marcelo Vieira