The Controller Daemon, SQDaemon plays a key role in the authentication process by being the first point of contact for any agent requesting communication with any other agent in both single and multi-platform environments. For more details regarding the Controller Daemon's role in security, see Secure Communications. Controller Daemons are accessed via a TCP/IP interface to an assigned Port on the platform where they are running. Their symbolic name is often synonymous with a specific Host (platform or Environment on which they are running.
The primary difference between an Engine Controller Daemon and a Daemon on Capture platforms is that the Authorized Key File of the Engine Controller Daemon need only contain the Public keys of SQDmon utility users on both the local and remote platforms.
Setup and configuration of the Engine Controller Daemon, SQDaemon, includes:
| # | Task | Utility |
| Configure Engine Daemon | ||
| 1 | Reserve TCP/IP port for Engine Daemon | N/A |
| 2 | Generate Engine public / private keys | SQDutil |
| 3 | Add the public key generated in step #2 to the Authorized Key List files on the Source system and target system | N/A |
| 4 | Create the Access Control List Configuration | N/A |
| 5 | Create the Agent Configuration File | N/A |
| 6 | Prepare the Controller Daemon JCL, shell or batch script | N/A |
| Engine Environment Preparation Complete | ||
Example
acl=<SQDATA_VAR_DIR>/daemon/cfg/acl.cfg
authorized_keys=<SQDATA_VAR_DIR>/daemon/nacl_auth_keys
identity=<SQDATA_VAR_DIR>/id_nacl
message_file=../logs/daemon.log
service=2626
[VSAM2ORA]
type=engine
program=SQDATA
args=VSAM2ORA.prc
working_directory=<SQDATA_VAR_DIR>
message=<SQDATA_VAR_DIR>
stderr_file=<SQDATA_VAR_DIR>/VSAM2ORA.rpt
stdout_file=<SQDATA_VAR_DIR>/VSAM2ORA.rpt
auto_start=yes