Encrypt change data payload - connect_cdc_sqdata - 4.1

Connect CDC (SQData) Secure communications components

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
4.1
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Secure communications components
Topic type
How Do I
Installation
Copyright
2024
First publish date
2000
ft:lastEdition
2024-02-07
ft:lastPublication
2024-02-07T13:29:14.268926

Traditionally CDC data was often sent via TCP/IP as "clear text" since the network between the systems running the Capture / Publisher and Engines were nearly always internal networks. Often those systems were also in the same physical room with dedicated high bandwidth connectivity. Distributed processing on remote systems makes encryption of the CDC payload data even on internal networks desirable if not mandatory. Four options are available to provide that encryption:

  • VPN
  • SSH Tunnel
  • NaCl Payload encryption
  • TLS Encryption (Requires implementation of IBM's Application Transparent Transport Layer Security (AT-TLS) and supports z/OS sources and Linux based Apply and Replicator engines only, at this time)

Notes:

  1. Precisely highly recommends the use of VPN or SSH Tunnel connections between systems both to simplify their administration and because the CPU intensive encryption task can be performed by dedicated network hardware.
  2. Customers utilizing NaCL encryption for z/OS based Captures/Publishers are encouraged to utilize zIIP processors to reduce the CPU cost associated with software encryption.