Home > Release Notes

4.0.1 (Development Release)

Release Date  : March 13, 2007

 

Bug fixes:

  • [01380] If the action "manage agreements" is permitted, but not the action "create a child", the button "create agreement" is not disabled and an error is returned if the user clicks ont it.
  • [01381] When an instance is deleted in a branch, the merge process does not work well afterwards.
  • [01382] For renaming repository database tables, the property "mdm.persistence.table.prefix" does not rename correctly relational tables.
  • [01384] At repository startup, if repository is not installed, the exception is not properly caught so the installation on RDBMS instance is not done (only for DB2 and Oracle).

Optimizations:

  • Load process has been optimized for instances with large number of tables.
  • Validation process has been optimized. On some repositories, it is 35 times faster.

API:

  • Added a method for exporting a webMethods MDM archive. See ProcedureContext.doExportHomeToArchive(Archive).
  • Added a method for importing a webMethods MDM archive. See ProcedureContext.doMerge(Archive).
  • A pre-release of webMethods Master Data Manager Component API is provided.
    WARNING: The API to webMethods Master Data Manager Component is still under review. It will be fully stabilized for release 4.1.
    See classes com.softwareag.mdm.ui.UIHttpExternalComponentLink and com.softwareag.mdm.ui.UIHttpInternalComponentLink.

Known limitations:

  • Performance: for large number of tables (in the order of 10,000 tables) and for large number of occurrences (in the order of 10,000,000 occurrences), optimizations are not yet available.
  • Merge process: in case of instances' add-add conflict, tables in the source are ignored.
    Workaround: first create instances and merge, then tables may be populated and merged.
  • Comparison and Merge: Header informations are not yet included in the comparison user interface nor in the merge process.
    Workaround: for merging header informations, a least one value must be updated on instance.
  • Repository locking: it is not yet detected when two Java virtual machines share the same physical repository.
    Workaround: Repositories' administrator must take care that a repository is not refered by two environments.
  • Permissions management: a user without the built-in PROVIDER role cannot access on adaptation instances above agreements.
    Workaround: the user must have the built-in PROVIDER role.
  • Access right management: a node can be set as ReadWrite even it is not adaptable according to schema definition.
  • Manager Components: UI Services can not be addressed through Manager components API.

 

Home > Release Notes