Adding a new Engine on a new target platform begins with the installation of the SQData product. See the Installation Section for the applicable platform Installation instructions. Once the product is installed, the steps to configure the new Engine parallel those required to configure the existing Engine . In our example the new Engine is named VSAM2ORA. The Engine script will specify only simple mapping of fields in a VSAM File layout to columns in a the target relational table.
While not as easy as simple replication due to potentially different names for corresponding columns and fields the most important aspect of the script will be the DATASTORE specification for the source CDC records.
DATASTORE cdc://<host><:port>/<publisher_agent_alias>/<engine_agent_alias>
Keyword | Description |
---|---|
<host> |
Location of the Controller Daemon. |
<:port> |
Optional, required only if non-standard port is specified by the service parameter in the Controller Daemon configuration. |
<publisher_agent_alias> |
Must match the alias provided in the "sqdconf add" command "--datastore" parameter when the Publisher agent was configured. The engine will connect to the Controller Daemon on that host and request to be connected to that Publisher agent (SQDZLOGC process). |
<engine_agent_alias> |
Must match the alias provided in the "sqdconf add" command "--datastore" parameter when the Publisher agent is configured to support the new target Engine. |
DATASTORE cdc://<host><:port>/VSAMPUB/VSAM2ORA
OF VSAMCDC
AS CDCIN
DESCRIBED BY <description_name>
;