IBM InfoSphere MDM Custom Domain Hub, Version 10.1This section describes the set of capabilities in the InfoSphere® MDM Custom Domain Hub Platform that services can leverage.
InfoSphere MDM Custom Domain Hub provides a comprehensive set of capabilities for auditing and logging. These capabilities include:
The data audit feature provides the ability to record, manage, and inquire on data. Data audit enables you to capture all changes to operational data in a separate set of database tables known as history tables. Each operational table in InfoSphere MDM Custom Domain Hub can have a mirror history table that contains the same set of columns as those in the operational table, with an additional set of columns that hold data audit information.
Any database activity performed by the services will cause audit records to be inserted into the history tables. Depending on how it is configured, history tables can contain current data plus changed data, or just changed data.
With the data audit feature enabled, all inquiry services provide organizations with the ability to perform point-in-time inquiries that return a snapshot of what the data looked like at any given point-in-time date.
The transaction audit feature provides the ability to record, manage, and inquire on transactional activity. Transaction audit enables you to capture transactional activity from the application. The transaction audit records can be searched and inquired upon. When combined with the data audit feature, you can determine what transactions have run in the application, and what the data looked like before and after the transaction.
The performance tracker feature provides the ability to log performance statistics during the execution of services. Performance tracker supports the Application Response Measurement (ARM) 4.0 standard.
The level of detail that is logged by this feature is configurable, and ranges from coarse-grained service execution times to very detailed measurements of a service's execution path through the various layers and frameworks of InfoSphere MDM Custom Domain Hub, including database interactions.
The Service Activity Monitor provides the ability to capture transaction statistics during the execution of services. These statistics can be used to gain an understanding of how the application is being used, and for management reporting and capacity planning. The Service Activity Monitor logs details including the service name, start and end times, request and response sizes, outcome, and service header elements.
The Service Activity Monitor is implemented using Java™ Management Extension (JMX) notifications with a default listener that logs activity to log files. If required, you can plug in an alternate listener, as long as it follows JMX standards.
.InfoSphere MDM Custom Domain Hub supports comprehensive system logging based on standard logging levels. The system can log a number of logging levels, from errors-only to detailed debugging.
InfoSphere MDM Custom Domain Hub supports data-driven error messages that are configurable.
The Entity Suspect Processing framework can be used to deliver a set of capabilities to manage a single version of truth for entity data. This consists of activities such as:
The framework can be leveraged to preview the collapse of two or more entities, collapse two or more entities, and split entities apart, all with fully maintained data lineage. As required, you can plug in custom rules, such as survivorship rules for collapse. You can use the InfoSphere MDM Custom Domain Hub Workbench to generate data stewardship services.
The framework can be leveraged to manage relationships (known as suspect entries) between entities that either may be duplicates, are duplicates, or are known not to be duplicates. InfoSphere MDM Custom Domain Hub manages information such as the state of the suspect entry, match categories, and match results. The suspect duplicate tracking services publish notifications as entries are created, updated, and deleted.
The Entity Standardization framework provides the ability to plug in standardizers that will put any out-of-the-box or custom entity into a standardized format. To perform the standardization, standardizers can use a set of inline Java rules or can invoke an external product such as IBM® InfoSphere QualityStage®.
The Entity Standardization framework provides the ability to automatically invoke standardizers during the course of service execution, based on constraints that are defined within InfoSphere MDM Custom Domain Hub metadata. You can use the InfoSphere MDM Custom Domain Hub Workbench to generate skeleton code for new standardizers.
The Notification framework provides the ability to send out Java Message Service (JMS) messages in either a publish-subscribe or point-to-point model. The Notification framework is leveraged with other InfoSphere MDM Custom Domain Hub features such as Event Manager and Entity Suspect Processing, and can also be leveraged within custom features whenever outbound messages are required.
InfoSphere MDM Custom Domain Hub provides a common code table framework. A number of code tables are provided out-of-the-box to support common business services. You can introduce new code tables using the InfoSphere MDM Custom Domain Hub Workbench.
From an administrative perspective, code table services exist to manage code types and values by locale.
As part of their execution, services use code table services to validate codes (either by type or value) and return code descriptions for the required locale.
InfoSphere MDM Custom Domain Hub provides the ability to expose rules with an External Rule framework. Existing services provided out-of-the-box have rules exposed in this framework so that you can tailor them to your organization's unique requirements. Rules can be written either in Java or ILOG JRules rulesets.
New services created using the InfoSphere MDM Custom Domain Hub Workbench can also use the External Rules framework to separate rules from service implementations and leverage JRules.
InfoSphere MDM Custom Domain Hub provides the ability to define all or part of an entity model using specifications, or specs. Specs use XML Schema technology to provide the means to manage data (spec values) within the database as XML documents.
You can use the InfoSphere MDM Custom Domain Hub Workbench to author and deploy specs.
InfoSphere MDM Custom Domain Hub provides the ability to define inquiry levels. An inquiry level dictates what type of information to return for an inquiry service. This feature provides a means to prevent service proliferation while tailoring the services to your business requirements.
Inquiry levels are defined in metadata. You can leverage the framework using custom inquiry services.
InfoSphere MDM Custom Domain Hub features register their configuration options with the Configuration and Management component. This component provides the ability to control the configuration and behavior of the various features within the implementation.
This feature includes a Configuration and Management console to aid with deploying and undeploying full configurations, as well as to configure individual features. Some features can be configured dynamically.
