Directory hierarchy - connect_cdc_sqdata

The Connect CDC (SQData) installation for UNIX recommends using one of two locations for the base product, in /opt under a folder named for the product or into a system account <owner_name> user's home directory:

/opt/sqdata or /home/<owner_name>/sqdata

In addition to the installation directory, the following series of commands will create the necessary directory structure along with the required file permissions for the Secure Communications components:

MKDIR '/home/sqdata/' MODE(7,7,5)
 
MKDIR '/home/sqdata/daemon/' MODE(7,7,5)
 
MKDIR '/home/sqdata/daemon/cfg' MODE(7,7,5)
 
MKDIR '/home/sqdata/daemon/logs' MODE(7,7,5)

Finally, Apply and Replicator components typically requires a different structure to accommodate the organization of development into areas of responsibility, including the associated "application" and "environments" like Testing or Production. This section will refer to the locations most commonly used on Linux:

MKDIR '/var/opt/sqdata/<application>/<environment>'

For customers that choose to install the base product in the home directory of a special user account:

MKDIR '/home/<sqdata_user>/<application>/<environment>

The nature of Replicator Engine Configuration scripts do not require a complicated structure. SQData only 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
rpts	Optional Report archive directory on Linux, managed by local shell scripts
logs	Optional Log archive directory on Linux, managed by local shell scripts

Note: Engine reports will all have the same name. While infrequently used they and corresponding logs can be timestamped and archived using shell scripts at startup.

Directory hierarchy - connect_cdc_sqdata - Latest

Connect CDC (SQData) Replicator Engine