|
Create Application Directory Structure |
Scroll |
Connect CDC SQData's Apply and Replicator Engines share a number of operational components including both NaCl Keys and the Connect CDC SQData daemon. The Linux directory structure described below should be used for Apply Engines.
While the Connect CDC SQData Variable Directory <SQDATA_VAR_DIR> location works fine for Capture Agents and the Controller daemon, Apply Engine Script development also requires a structure accommodating similar items from dissimilar platforms such as DDL from Db2 and Oracle. For that reason the following directory nodes are recommended at the next level for script development and parts management:
./<directory_name> |
Description |
|---|---|
ENGINE |
Main Engine scripts |
CDCPROC |
CDC Engine Called Procedures referenced by #INCLUDE |
LOADPROC |
Load (UnLoad) Engine Called Procedures referenced by #INCLUDE |
DSDEF |
Datastore Definition referenced by #INCLUDE |
<TYPE>DDL |
RDBMS specific DDL, eg DB2DDL, ORADDL, MSSQLDDL, etc |
IMSSEG |
IMS Segment Copybooks |
IMSDBD |
IMS DBD |
<TYPE>COB |
System specific COBOL copybooks, eg: VSAMCOB, SEQCOB (sequential files) |
XMLDTD |
XML Document Type Definitions that will be used in a DESCRIPTION command |
<TYPE>CSR |
RDBMS specific Cursors, eg DB2CSR, ORACSR,etc |
<TYPE>LOAD |
RDBMS specific Load Control, eg DB2LOAD, ORALOAD ,etc |
Notes:
1.While it may be more convenient to user lower case directory names, if your environment includes the z/OS Platform, consideration should be given to reusability as some z/OS references must be in Upper Case.
2.Engine scripts are typically Platform specific in that they cannot be used on another type of Platform, eg z/OS and UNIX without at least minor modification.
3.Called Procedures can frequently be used with little or no changes on another platform, even when they contain platform specific Functions, unless they require direct access to a datastore on another platform, an atypical requirement.
4.Throughout the remainder of this document, part locations will usually refer only to the last node of standard z/OS Partitioned Datasets and UNIX or Windows directory hierarchy.
Unzip the Basic_Linux_Parts_Structure.zip file to create the full Linux directory structure along with sample parts and shell scripts.
Alternatively, commands similar to the following may be used to create the recommended directory structures.
$ mkdir -p <SQDATA_VAR_DIR>/DB2DDL --mode=775
$ mkdir -p <SQDATA_VAR_DIR>/ORADDL --mode=775
$ mkdir -p <SQDATA_VAR_DIR>/IMSDBD --mode=775
$ mkdir -p <SQDATA_VAR_DIR>/IMSSEG --mode=775
$ mkdir -p <SQDATA_VAR_DIR>/ENGINE --mode=775
$ mkdir -p <SQDATA_VAR_DIR>/CDCPROC --mode=775
The nature of Replicator Engine Configuration scripts do not require a complicated structure. Precisely recommends that you consider how your Source database and Applications are structured since it may be desirable to maintain Replicator Engine Configurations in a similar structure:
./<directory_name> |
Description |
|---|---|
ENGINE |
Replicator Engine Configuration Scripts |
