Engine controller daemon - connect_cdc_sqdata - Latest

Connect CDC (SQData) Secure Communications Components
Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
Latest
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Secure Communications Components
Copyright
2024
First publish date
2000
Last edition
2024-07-30
Last publish date
2024-07-30T19:55:16.493453

The Engine Controller Daemon requires five files to manage the Authentication process

  • NaCl Public and Private Key files
  • Authorized key List file - NACL.AUTH.KEYS
  • Access Control List file - acl.cfg
  • Agent Configuration file - sqdagents.cfg
Note: The Public and Private key files are created by the sqdutil utility while the nacl.auth.keys, acl.cfg and sqdagents.cfg files are typically created using a text editor on Linux.

Public and private keys

The utility SQDUTIL will be executed from the command line under the User_Name (User_ID) to be used by the Engine to generate the public / private key pair:

sqdutil keygen

By default the private key is generated in ~/.nacl/id_nacl and the public key in ~/.nacl/id_nacl.pub. The Apply Engine's public key must then be added to the Authorized Key List file used by the Capture Controller Daemon running on the Source Platform.

Authorized key list

The NACL.AUTH.KEYS file will contain a concatenated list of the Public Keys of all the Agents interacting with the Engine Controller Daemon. In this example that will only include the Apply Engine running on Linux. On Linux this is usually done by a systems administrator using a text editor.

Access control list and agent configuration files

These two files are usually created using a text editor on Linux.

Access Control List - The acl.cfg will contain something similar to the following, with the user_name (user_id) under which the Engine will execute either assigned to a group_name or specified in the acls section.
default_acl=query

[groups]
group_name=user_name

[acls]
group_name=admin
A sample sqdagents.cfg file for a single engine running on Linux might look like the following:
acl=acl.cfg
authorized_keys=/home/sqdata/nacl.auth.keys
identity=/home/sqdata/.nacl/id_nacl
message_file=../logs/acl.log
service=2626

[DB2TOKAF]
type=engine
program=sqdata
args=--log-level=2 DB2TOKAF.prc
working_directory=c:/home/sqdata/ENGINE
auto_start=yes