MDM4J to New API Migration

[Former Member]

Hi All

We are planning to upgrade a MDM interface, designed using MDM4J Java API to New Java API as we are migrating from MDM 5.5 SP03 to SP05.

We basically use the interface for the following

- Add / update Records

- Move the records from one repo to another repo

- few other customized functionalities

Need your help with the following queries.

- Do we need to re-write the whole application code?

- How much % of code can be reused?

Please share your experiance if you have worked on the same.

Thanks

Edited by: Prakash Nathan on Jan 4, 2008 3:56 PM

Edited by: Prakash Nathan on Jan 4, 2008 3:56 PM

[Former Member]

Hi, this is a very open question, since there are a lot of elements involved in the migration. Are you using Taxonomy Tables with attributes? Do you also create keys with the record creation? What are those custom developments that you mention? All the calls to MDM using the API are new with the new API, so far, there is not much of your MDM4J old code that you can use.

I hope this answer your question.

BR.

[Former Member]

Hi Nathan,

The amount of code that needs to be re-written depends on how well you have separated data manipulation and UI. Obviously every reference to MDM4J functions needs to be recoded.

Please note that your intended migration from SP03 to SP05 does not mean that you have to migrate custom applications to the new Java API, as SP05 still supports MDM4J. So you should consider the migration to the new API if you want to take advantage of functionality not included in MDM4J, or the much smaller memory footprint of the new API.

Regards,

Walter