|
Terminology |
Scroll |
Change Data Capture
Terms commonly used when discussing Change Data Capture:
Term |
Meaning |
Agent |
Individual components of the Connect CDC SQData product architecture. |
CDC |
Abbreviation for Changed Data Capture. |
Datastore |
An object that contains data such as a hierarchical or relational database, VSAM file, flat file, etc. |
Exit |
A classification for changed data capture components where the implementation utilizes a subsystem exit in IMS, CICS, etc. |
File |
Refers to a sequential (flat) file. |
JCL |
An abbreviation for Job Control Language that is used to execute z/OS processes. |
Platform |
Refers to an operation system instance. |
Record |
A basic data structure usually consisting of fields in a file, topic or message. A row consisting of columns in a Relational database table. Record may be used interchangeably with row or message. |
Segment |
A basic data structure consisting of fields in an IMS hierarchical database. Segments are records having parent and child relationships with other records defined by a Database Description (DBD). |
Source |
A datastore monitored for content changes by a Capture Agent. |
SQDconf |
A Utility that manages configuration parameters used by some data capture components. |
SQDXPARM |
A Utility that manages a set of parameters used by some IMS and VSAM changed data capture components. |
Table |
Used interchangeably with relational datastore. A table represents a physical structure that contains data within a relational database management system. |
Target |
A datastore where information is being updated/written. |
Apply Engines
Terms commonly used when discussing the Apply Engine:
Term |
Meaning |
Agent |
Individual components of the Connect CDC SQData product architecture. |
CDC |
Abbreviation for Changed Data Capture. |
Alias |
An alternative name that given to an object such as a Datastore, Description or field or column within a Description. |
Command |
Reserved words that define the environment, describe source and target datastores, specify variable, field and column level attributes and control the processing of source and target datastores. |
Column |
An individual data element in a relational datastore. Used interchangeably with field. |
Cursor |
A cursor provides the means to explicitly execute virtually any SQL statement. |
Database |
Refers to a collection of tables/segments/records in a database management system. |
Datastore |
An object that contains data such as a file, database table, IMS segment or WebSphere MQ. |
Description |
Defines the structure/layout of source and target. May be a COBOL copybook or DDL describing a relational table. |
Engine |
Refers to the SQData Apply and Replicator Engine components. |
Event |
Any condition that can be identified by a change in the value of data that has been Captured |
Exit |
In the Engine context, a program that performs functions not supported by the typical Integration/ETL tool but that can be called by the tool. |
Field |
An individual data element in a datastore. Used interchangeably with column in this manual. |
File |
Refers to a sequential (flat) file on any operating system platform. |
Function |
A built-in SQData routine that facilitates the transformation/manipulation of source data elements. |
Parser |
Refers to the SQData Parser component that validates an Apply Engine script and translates it into the form used by the Apply Engine component. |
Platform |
Refers to an operation system instance. |
Propagation |
Refers to capturing changed data and applying it to a target datastore(s). |
Queue |
Refers to Kafka or WebSphere MQ. |
Record |
A group of information within a file. Used interchangeably with row and message. |
Row |
A record within a relational database table. Used interchangeably with record and message. |
Script |
A collection of Apply Engine commands and functions that describe the target Platform, source and target datastores and the sequence of instructions that control the transformation of data moving from source to target datastore. |
Source |
A datastore from which information is being extracted/read. |
Table/View |
Used interchangeably with relational datastore. A table or view represents a physical structure that contains data within a relational database management system. |
Target |
A datastore to which information is being updated/written. |
Variable |
A temporary user specified value that can be used to assist with data transformation and controlling SQData processing flow. |
Replicator Engines
Terms commonly used when discussing the Replicator Engine:
Term |
Meaning |
Agent |
Individual components of the Connect CDC SQData product architecture. |
Alias |
An alternative name that given to an object such as a Datastore, Description or field or column within a Description. |
Alias |
An alternative name that given to an object such as a Datastore, Description or field or column within a Description. |
CDC |
Abbreviation for Changed Data Capture. |
Consumer |
Term used by Apache Kafka to describe client applications that subscribe to (read and process) Kafka topics. |
Database |
Refers to a collection of tables/segments/records in a database management system. |
Datastore |
An object that contains data such as a database table, IMS segment, Message Queue or source CDC data. |
Description |
Defines the structure/layout of source and target. May be a COBOL copybook or DDL describing a relational table. |
Dispatcher/Distributor |
Specialized function of the Replicator Engine that supports parallel producer connections. |
Engine |
Refers to the SQData Apply and Replicator Engine components. |
Event |
Any condition that can be identified by a change in the value of data that has been Captured |
Exit |
In the Engine context, a program that performs functions not supported by the typical Integration/ETL tool but that can be called by the tool. |
Field |
An individual data element in a datastore. Used interchangeably with column in this manual. |
File |
Refers to a sequential (flat) file on any operating system platform. |
Message Broker |
Communication technology used to pass data and information about data (metadata) between disparate applications. Common examples include Apache kafka and IBM MQ. |
Platform |
Refers to an operation system instance. |
Producer |
Term used by Apache Kafka to describe client applications that publish to (write) Kafka topics. |
Propagation |
Refers to capturing changed data and applying it to a target datastore(s). |
Queue |
Refers to the storage of messages by a message broker like Kafka. |
Record |
A group of information within a file. Used interchangeably with row and message. |
Row |
A record within a relational database table. Used interchangeably with record. |
Script |
A collection of instructions that describe the target datastore, various replication options and source/target specific metadata processing options. |
Source |
A datastore from which change data has been captured or has been unloaded. |
Table |
Used interchangeably with relational datastore. A table represents a physical structure that contains data within a relational database management system. |
Target |
A datastore to which information is being written. |
