MDM v 11.4 some Issues and resolutions

1.       After successful addition of a CBA and its linking to EBA from Server view, sometimes an error is observed which is misleading.

<ErrorMessage>DWLParser Exception. An error has occurred while parsing the xml.</ErrorMessage>

Finding & Resolution:- Though it gives an impression of CBA successfully associated with EBA from server view. But when checked from admin console it is found CBA doesn’t get linked with EBA for some valid error of project. Try to associate the CBA to EBA from admin console. If any error message is encountered fix in project and then re-try associating CBA to EBA again. Once EBA gets associated successfully, the above error should go.

2.       While trying to run any transaction from a migrated Project from MDM 9.0.2 to 11.4 an error may be  encountered which misleads

<Error Message>Transaction not defined in the properties file.</ErrorMessage>

Finding & Resolution:- The services entries which are present in blueprint.xml which are to be exposed of a Hub Module project has to be present under Export-Package of CompositeBundle.MF of CBA.

It might happen sometimes while migrating a project that this entries are not present in CompositeBundle.MF and this error may be encountered. Add the appropriate service entries by clicking on the add button of Exported-Services in OverView tab of CompositeBunle.MF of CBA to fix this.

Further read on this:

http://www.ibm.com/developerworks/data/library/techarticle/dm-1409mdm11-osgi/index.html

3.       When Projects are migrated from MDM 9.0.2 to 11.4 code has to be regenerated from module.mdmxmi to generate osgi related artefacts required for OSGI Migration of MDM.

This may lead to overridden of some of components customised by us.

Finding & Resolution:- Make sure @generated-Not annotation is appropriately placed at all the places wherever customised code is present. After code generation manually check the Customised code remains good. Rest all code will be appropriately upgraded to new Standards(eg: Generics Collections- Type safe are added) which shall work fine.

4.       Crashing of Server is reported with immediate power shut down of Development machines owing to antivirus definitions upgrade.

Machines were kept ON with Build, Deployment tasked in line. Once the Machine is restarted and Server is restarted again, transaction fails to run. The EBA on admin console shows red cross symbol against it.

Alternative Fix1:- Remove all the CBA and there associations. Uninstalled the EBA. Re add the EBA again from admin console. Add all CBA and associate them with EBA. It should work now.

Alternative Fix2:- Stop the server. Go to Server installed directory from Windows directory. Delete the content of temp, wstemp, translog folders. Restart the Server. It should work now.