InfoSphere® MDM Custom Domain Hub validates all data submitted through InfoSphere MDM Custom Domain Hub transactions to ensure that all data satisfies the requirements expressed in the validation rules.
Data can be validated by level (for controller or business components) and by type (for internal or external types).
InfoSphere MDM Custom Domain Hub validates
data by two levels:
- Controller
- Used to process as many validations as possible at the pre-transaction stage. Most validations are performed at the controller level as opposed to the business component level.
- Used for accumulating and returning as many error messages at pre-transaction to improve performance for users who will then not have to cope with as many validations during their session.
- Important for performance reasons.
- Business component – Used for validating transactions as they are carried out. For example, when an add party is a suspect duplicate, the system completes additional business component validations.
InfoSphere MDM Custom Domain Hub validates
data by two types:
- Internal – Intended to maintain database integrity at both the controller level and the business component level. This code is generally not accessible to developers and administrators.
- External – Validates content and uses information that is accessible and modifiable by developers and administrators at the controller level only.
Sometimes, data is validated by both internal and external types. The following diagram depicts this relationship:
For more information on data validation, see the configuring external validations topic in the IBM® InfoSphere Master Data Management Custom Domain Hub System Management Guide.
In this section, you will learn:
