Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Security
  5. Connection Management
  6. JDBC Client Configuration
  7. ODBC Client Configuration
  8. Configuration for MicroStrategy
  9. Access Control
  10. Logs
  11. High Availability
  12. Server Control
  13. Performance Tuning
  14. Troubleshooting
  15. Appendix A: Database Keywords

Administrator Guide

Administrator Guide

Configuring Dynamic Data Masking for Apache ZooKeeper

Configuring Dynamic Data Masking for Apache ZooKeeper

To group the Dynamic Data Masking servers in a cluster in ZooKeeper, create a parent node. The parent node is a persistent node and will continue to exist after you restart ZooKeeper.
  1. Use the Dynamic Data Masking Server control commands to create the parent node in ZooKeeper.
    1. Start the Dynamic Data Masking Server.
    2. Connect to ZooKeeper with the following command:
      server zookeeper connect -url '<zookeeper_ensemble>'
      Example:
      server zookeeper connect -url 'server1.informatica.com:2181, server2.informatica.com:2181, server3.informatica.com:2181'
    3. Create a parent node in ZooKeeper with the following command:
      server zookeeper create -path /<name of parent node>
      Example:
      server zookeeper create -path /DDM
      The following image shows a database cluster with two database nodes and a Dynamic Data Masking cluster with two server nodes:
  2. Create an ephemeral node for each Dynamic Data Masking Server in the cluster. Initialize the ephemeral node with the URL copied from the database node of
    hiveserver2
    . Replace the host and port values of the database URL with the corresponding host and port values of the Dynamic Data Masking Server.
    If the environment is enabled for Kerberos, replace the Hive service principal with Dynamic Data Masking service principal defined in the
    /cfg/ddm.security
    file.
    server zookeeper create -path /<DDM cluster path> -type EPHEMERAL -data <driver_url_toddm_cluster>
    Example:
    server zookeeper create -type EPHEMERAL -path /DDM/ddm1 -data "hive.server2.instance.uri=<ddmhost1>:<DDM hive service port>;hive.server2.authentication=KERBEROS;hive.server2.transport.mode=binary;hive.server2.thrift.sasl.qop=auth;hive.server2.thrift.bind.host=<ddmhost1>;hive.server2.thrift.port=<DDM hive service port>;hive.server2.use.SSL=false;hive.server2.authentication.kerberos.principal=<Dynamic Data Masking service principal for ddmhost1>"
    server zookeeper create -type EPHEMERAL -path /DDM/ddm2 -data "hive.server2.instance.uri=<ddmhost2>:<DDM hive service port>;hive.server2.authentication=KERBEROS;hive.server2.transport.mode=binary;hive.server2.thrift.sasl.qop=auth;hive.server2.thrift.bind.host=<ddmhost2>;hive.server2.thrift.port=<DDM hive service port>;hive.server2.use.SSL=false;hive.server2.authentication.kerberos.principal=<Dynamic Data Masking service principal for ddmhost2>"
    A persistent node can have child nodes. An ephemeral node cannot have child nodes.

0 COMMENTS

We’d like to hear from you!