The controller daemon (sqdaemon) is started by sqdservice when the AMI instance starts. The sqdservice will restart it if it cannot communicate with it for any reason.
All apply engines must be defined to the controller daemon by adding a unique <ENGINE_NAME> stanza into $SQDATA_DAEMON_DIR/cfg/sqdagents.cfg and managed using the commands to the controller daemon.
For example, an sqdagents.cfg stanza for a replication pipeline from DB2 z/OS to Oracle:
[DB2ZTOORACLE]
type=engine
program=sqdata
args=/var/precisely/di/sqdata/apply/DB2ZTOORACLE/scripts/db2ztooracle.prc
--log-level=8
working_directory=/var/precisely/di/sqdata/apply/DB2ZTOORACLE
stdout_file=/var/precisely/di/sqdata_logs/apply/DB2ZTOORACLE/stdout.txt
stderr_file=/var/precisely/di/sqdata_logs/apply/DB2ZTOORACLE/stderr.txt
auto_start=0
comment=Apply Engine for Oracle from DB2z
The sample commands to manage this apply engine include:
- sqdmon start///DB2ZTOORACLE --service=2626
- sqdmonstop///DB2ZTOORACLE --service=2626