Overview

The current web service interface is generic and data model agnostic, but suffers from poor usability. The primary problem is generic representation of data services which makes it difficult for the user to define a web services client for it. The schema is not rigorous and has limited validation capabilities. Another problem is the use of 'special' keywords (not schema exposed) which have to be understood before proper use. For example for record services, the specific name 'PRODUCTID' has to be used in order to identify the primary record identifier.

The primary goal for the dynamic services is to make the web services simple and easy to use.

The dynamic services will especially be useful for record services based on an actual Repository, including attributes and information, to allow a more meaningful and syntactically tight schema. The number of such services can be different for each repository, hot deployed and redeployed if any changes are required.

The user will define a specific data repository, with all the needed attributes and will generate from this definition a repository specific web service in form of a WSDL definition and an associated implementation. This web service has six fundamental methods for record data management available (Add, Modify, Delete, Find, Validate, and Build Relationship). This newly generated web service can then be deployed onto a MDM Server instance to be used.