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

Connecting the Dynamic Data Masking Server to ZooKeeper on Server Startup

Connecting the Dynamic Data Masking Server to ZooKeeper on Server Startup

Create a script file that connects the Dynamic Data Masking Server to ZooKeeper when the Dynamic Data Masking Server starts.
  1. Create a parent node in ZooKeeper.
    Example:
    server zookeeper create -path /DDM
    The parent node contains the Dynamic Data Masking clusters in ZooKeeper. The parent node is a permanent node that continues to exist even after ZooKeeper is restarted.
  2. Create a regular parent node for each database cluster if none exists.
    server zookeeper create -path /DDM
  3. To automatically connect the Dynamic Data Masking Server to Zookeeper and create ephemeral nodes, create a script file with the name
    serverStarting.bat
    or
    serverStarting.sh
    .
    Otherwise, you can manually run the ZooKeeper commands after you start the server.
  4. Provide the following information in the
    serverStarting
    script file:
    1. The
      connect
      command and parameters to connect the Dynamic Data Masking Server and ZooKeeper.
    2. The
      create
      command and parameters to create an ephemeral node for each database server.
    3. Initialize the ephemeral nodes with specific URLs. The URL must include the host and port of the Dynamic Data Masking Server.
      The database driver uses the URL to connect to the database cluster through Dynamic Data Masking.
    Linux Example:
    #!/bin/sh cd `dirname $0` . ./server zookeeper connect -url 'zookeeper_ensemble' . ./server zookeeper create -type EPHEMERAL -path /<DDM cluster>/<name of ephemeral node> -data hive.server2.instance.uri=<ddmhost1>:10001;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=<hive service principal for ddmhost1>
    Microsoft Windows Example:
    @echo off REM ********************************************* REM Start DDM Server REM ********************************************* CALL server start REM ********************************************* REM Connect DDM Server to Zookeeper REM ********************************************* CALL server zookeeper connect -url '<zookeeper_ensemble>' REM ********************************************* REM Create a new ephemeral node for the DDM Server REM ********************************************* CALL server zookeeper create -type EPHEMERAL -path /<DDM cluster>/<name of ephemeral node> -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=<hive service principal for ddmhost1>"
  5. Save the
    serverStarting
    script file in the Dynamic Data Masking installation directory.
    When the Dynamic Data Masking Server starts, the server runs the
    serverStarting
    script file.
  6. Repeat steps 3-5 for other Dynamic Data Masking servers in the cluster.

0 COMMENTS

We’d like to hear from you!