Chapter 3. Data Integration and Information Aggregation patterns 59
– Data Server/Services node
For an up-to-date list and a detailed description of runtime nodes, please refer to
the Patterns Web site:
http://www.ibm.com/developerWorks/patterns/
This chapter introduces the Business and Integration patterns and describes the
different Application patterns and corresponding Runtime patterns for the Data
Integration and Information Aggregation patterns.
3.2 Business and Integration patterns overview
Prior to examining specific Application patterns in more detail, it is important to
understand the relationship between the Business and Integration patterns
covered in this redbook, in particular the relationship between the Data
Integration patterns and Information Aggregation. Solutions based on these two
patterns tend to adopt the following model:
Data Integration patterns serve to integrate the information (or data) used by
multiple applications. Such integration occurs in advance of the actual access
to the data by an end user.
The basic premise is that existing data is available in both structured and
unstructured forms in application data repositories managed by other
applications.
A proven repeatable pattern is therefore needed for combining this data into a
single optimized form and place (or perhaps multiple forms and places). Data
Integration patterns provide this functionality.
Important: The patterns described here are a significant rework of those in
the Information Aggregation (User-to-data) and data-focused Application
Integration areas on the Patterns for e-business Web site
(http://www.ibm.com/developerWorks/patterns/). They also represent an
evolution of the thinking described in the redbook Patterns: Portal Search
Custom Design, SG24-6881-00.
The major change has been to consolidate the Application patterns for both
structured and unstructured into a single, self-consistent set. In this redbook,
the focus in the Runtime patterns is on the structured data area. When dealing
with unstructured data, and particularly Web-based content, the redbook
Patterns: Portal Search Custom Design, SG24-6881-00, should be read in
conjunction with this chapter.
60 Patterns: Information Aggregation and Data Integration with DB2 Information Integrator
Information Aggregation patterns allow users to access and manipulate data
that is aggregated from multiple sources. Conceptually, these patterns take
the data that is available from the multiple sources and applications via Data
Integration, and provide tools to extract useful information and value from
such large volumes of data.
A modern solution, however, is likely to require more than these two high-level
patterns. Applications that require both analysis activities and updates to the
base data are becoming the norm. For example, an Internet customer of a
financial institution may wish to do what-if analysis of investment options, consult
with a service representative via instant messaging, browse some assorted Web
sites, and then place an order based on the results of that activity. In such a
scenario, a combination of patterns will be required as follows:
Self Service and Collaboration business patterns
Data Integration and Information Aggregation patterns
Access Integration pattern to provide a consolidated portal for the user
Figure 3-1 on page 61 depicts this relationship between these categories of
Business and Integration patterns, and positions the key Application patterns of
interest within them.
Chapter 3. Data Integration and Information Aggregation patterns 61
Figure 3-1 Business, Integration, and related Application patterns
In Figure 3-1, the Data Integration patterns are used to move, copy, and
transform data and information between different stores and representations in
advance of such data being required by the user. Arrows are used to show this
prior data movement.
Three types of data store are characterized by how the data is managed and
whether the data is structured or unstructured:
Systems of record (or operational systems) contain structured data and are
managed by applications that are responsible for the transactional
consistency of such data.
Unstructured data stores hold data such as e-mail, voice, or images managed
through collaborative and other means.
Derived data stores contain structured data, unstructured data, or both, and
are managed though Data Integration processes that create and maintain
LEGEND:
Data sources and targets are represented by disks
Pale blue box represents a Business or Integration pattern.
Beveled box represents an Application pattern.
Arrows show data movement.
Data Integration
Access Integration
Collaboration
Information
Aggregation
Self
Service
Data
store
Application
Data
store
Presentation
Two-way
Synchronization
Data
store
Presentation
Presentation
Access Integration
User
Information
Access
Agent
Population
Population
Collaboration
And others
Federation Federation
Federation
FederationFederation
Unstructured
data stores
Systems of record
(Operational Systems)
User
Derived
data stores
(Informational
Systems)
Data Integration
Access Integration
Collaboration
Information
Aggregation
Self
Service
Data
store
Application
Data
store
Application
Data
store
PresentationPresentation
Two-way
Synchronization
Two-way
Synchronization
Data
store
PresentationPresentation
PresentationPresentation
Access IntegrationAccess Integration
User
Information
Access
User
Information
Access
Agent
PopulationPopulation
PopulationPopulation
CollaborationCollaboration
And othersAnd others
FederationFederation FederationFederation
FederationFederation
FederationFederationFederationFederation
Unstructured
data stores
Systems of record
(Operational Systems)
User
Derived
data stores
(Informational
Systems)
Get Patterns: Information Aggregation and Data Integration with DB2 Information Integrator now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
