How do you create a mapping file?

The repository migration assistant says it's 'highly recommended' that we use a mapping file when migrating the data. How do we do this? I can't find any way within the metastorm products to create one, nor any instructions or examples on how to do this. I could write one myself if only I knew what format it needed to be in, but I don't.

Migrating data is a fairly major feature of any upgrade path, I'm a bit surprised there's so little documentation on how to get it to work.

Please can somebody in Metastorm post an example .mappings file or some instructions on how to make one, so we can all start to think about migrating? That would be most helpful.

Find more posts tagged with

BPM

Comments

Jerome_Pearce

I have not read it yet.

What is this mapping file supposed to do, exactly? I'm not asking you, but the potential respondant.

Signed, concerned of Sydney......

achopra

This is from the v9 Repository Migration Guide (downloadable from the Customer Zone website)

"During the version 7.6 –> version 9 conversion process, a mapping file is output by the file migrator into the same folder as the solution. This mapping file provides the necessary reference information required to transform the version 7.6 stage, action, role and variable names into their version 9 equivalents, adhering to the tighter naming conventions that have been introduced in version 9."

(see attached file - Repository Migration Guide)

Joe Smith

As a follow-up to Ari's post, the Repository Migration Guide is available as a zipped CHM file from the BPM Documentation page of both the Customer and Partner Zones (provided you have access to them).

Jerome_Pearce

It is a bit ambigous to say the least!

I gather that the mappings file is created by the procedure migration tool when migrating the procedure from v7 to v9. This can (it must be assumed) be ammended, and in fact must be ammended if you have mande any changes to stage / action, form, field role(?) names during the wonderfully understated 'step 6' of the migration guide:

Test the newly converted version 9 version of the procedure at runtime. Make sure that it functions as you expect it to. If it does not the problems should be diagnosed and corrected and the solution redeployed. Repeat this cycle of test, fix and redeploy until you are satisfied that no further problems exist.

My guess is the best approach is to change no names at all. The captions can, I again assume, be changed at will without affecting this, so it should not be too difficult.

Carolyn Anderson

The migration guide is wrong. It outputs a conversion log, not a mapping file. I have just re-migrated my procedure and there is still no .mapping file.

Carolyn Anderson

Ok, the newest version does this now. The Repository Migration tool still throws the exact same errors when trying to migrate my data, but at least I know now it's not down to my not giving it a mapping file.