Change Data Capture node
Use the Change Data Capture node to capture all the changed data from your database into IBM® App Connect Enterprise.
Information about the Change Data Capture node is available in the following sections:
Purpose
You can use the Change Data Capture node for extracting or subscribing to changes that occur on a particular database server without incurring an extra cost in each transaction.
Using this node in a message flow
The Change Data Capture node is contained in the Database drawer of the palette, and is represented in the IBM App Connect Enterprise Toolkit by the following icon:
For more information about configuring the Change Data Capture node, see Configuring the Change Data Capture node.
Terminals and properties
The Change Data Capture node terminals are described in the following table.
Terminal | Description |
---|---|
Failure | The output terminal to which a message is routed if an error occurs before a message is propagated to the Out terminal. |
Out | If no errors occur within the input node, a message that is received from an external resource is always sent to the Out terminal first. |
Catch | The output terminal to which the message is routed if an exception is thrown downstream and caught by this node. Exceptions are caught only if this terminal is attached. |
The following tables describe the node properties that you can set on a specified tab. The column headed M indicates whether the property is mandatory (marked in the IBM App Connect Enterprise Toolkit with an asterisk if you must enter a value when no default is defined). The column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the BAR file to deploy it).
Property | M | C | Default Value | Description |
---|---|---|---|---|
Node Name | Yes | No | Change Data Capture | The name of the node. |
Short Description | No | No | None | A brief description of the node. |
Long Description | No | No | None | Text that describes the purpose of the node in the message flow. |
Property | M | C | Default | Description | mqsiapplybaroverride command property |
---|---|---|---|---|---|
Policy | Yes | Yes | None | The URL of the policy property. | policyURL |
List of Database Tables | Yes | Yes | None | List of database tables. | databaseTables |
Property | M | C | Default | Description | mqsiapplybaroverride command property |
---|---|---|---|---|---|
Additional instances pool | No | Yes | Use Pool Associated with Message Flow | The pool from which the additional instances are obtained.
|
componentLevel |
Additional instances | No | Yes | 0 | The number of additional instances that the node can start if the Additional instances pool property is set to Use Pool Associated with Node. | additionalInstances |
For a full description of the Instances properties, see Configurable properties in a BAR file.
Property | M | C | Default | Description |
---|---|---|---|---|
Events | No | No | None | Events that you define for the node are displayed on this tab. By default, no
monitoring events are defined on any node in a message flow. Use Add,
Edit, and Delete to create, change, or delete
monitoring events for the node; see Configuring monitoring event sources by using monitoring properties for details. You can enable and disable events that are shown here by selecting or clearing the Enabled check box. |