Skip to main content

Application Integration::Population=Multi Step Gather variation::Runtime patterns

Population=Multi Step Gather variation::Runtime pattern

Population=Multi Step Gather variation::Runtime pattern Data Server Services Data Server Services Population Population Population Population
Design Last Updated: 10-20-2004
(Click a node to get a detailed explanation.)

The figure above shows the Runtime pattern for this Multi Step Gather variation, specifically aimed at gathering changes in a structured data source.

In this instance, the main Population pathway (Gather 2, Process, and Apply) handles both the initial load and the update of the target Data Server.

  • For the initial load, Gather 2 obtains the data from the source directly.
  • For update, however, a separate step is required (Gather 1), which reads the changes from the source and passes them to the main pathway.

Using the same main pathway for both initial load and updates is an important feature to help maintain data consistency and integrity.

The figure above allows for the possibility that some of the nodes may be combined - Process and Apply nodes in this case.

For examples of runtimes for unstructured data, please refer to the redbook: Patterns: Portal Search Custom Design, SG24-6881.

Next, review product mappings for this Runtime design.

Close [x]

Data Server/Services

A Data Server/Services node is a generic data storage node that provides managed, persistent storage of any type of data and a means to directly access and manipulate that data. The data may be stored in files and accessed through file I/O routines or may be stored in a database with more structured and managed access methods.

Close [x]

Population

A population node is a specialized application or data server that is optimized for record-oriented processing where the records must be gathered from one or more source data sets, processed singly and multiply and finally applied to one or more target data sets. A population node typically operates in an "off-line" mode to prepare data in advance of its business usage and based on rules that have been previously defined through a separate user interface module and stored in a metadata repository.

A population server may be further specialized for one or two of its inherent sub-functions--gather, process or apply (also known as extract, transform and load respectively). Such specialization may be for reasons of performance or physical placement.