Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Dynamic Data Masking 9.9.3
  • All Products

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

Back Next

Configuring Dynamic Data Masking Server High Availability for Db2

Configuring Dynamic Data Masking Server High Availability for Db2

Configure Dynamic Data Masking Server high availability to send requests through a secondary Dynamic Data Masking Server if the primary Dynamic Data Masking Server is unavailable.
Verify the following prerequisites before you configure Dynamic Data Masking Server high availability for Db2:
  • You must have a Db2 database.
  • You must have two Dynamic Data Masking Servers installed.
  • You must have the IBM JDBC driver.
  1. In the Management Console for the primary Dynamic Data Masking Server, create a connection to the Db2 database. The database client must use the IBM JDBC driver to connect to the listener port that you define for the connection.
    If the Dynamic Data Masking Server installations are on the same machine, you must configure different listener port numbers for the primary and secondary servers.
  2. Add the Dynamic Data Masking service for DB2.
  3. Open the connection rule set for the Dynamic Data Masking service and create a rule folder that identifies requests to the database. Configure the following properties for the rule folder:
    Matcher
    Select the Incoming DDM Listener Port matcher. The Incoming DDM Listener Port matcher identifies requests based on the incoming listener port.
    Incoming Port
    Enter the listener port number for the primary Dynamic Data Masking Server.
    Rule Action
    Select the Folder rule action. The Folder rule action creates a rule folder.
    Processing Action
    Select the Stop if Matched processing action to process only the connection rules in the rule folder.
  4. In the rule folder, create a connection rule that sets the priority levels of the Dynamic Data Masking Servers. Configure the following properties for the connection rule:
    Matcher
    Select the All Incoming Connections matcher. The All Incoming Connections matcher applies the rule action to all SQL requests.
    Rule Action
    Select the Load Control rule action. The Load Control rule action identifies the Dynamic Data Masking Servers and port numbers, and sets the server priority level. Configure the following Load Control properties:
    • Host
      . Enter the names of the Dynamic Data Masking Servers. Click the plus sign (+) to add additional servers.
    • Port
      . Enter the port number for each of the Dynamic Data Masking Servers.
    • Priority
      . Enter a priority number for each of the Dynamic Data Masking Servers. The value of the Priority property corresponds to the frequency that the client sends the request through the Dynamic Data Masking Server.
    For more information about the Load Control action and how to set priority levels, see the
    Dynamic Data Masking User Guide
    .
    Processing Action
    Select the Continue processing action. The Continue processing action sends the request to the next rule in the tree.
    The following image shows an example of the connection rule:
    The rule uses the All Incoming Connections matcher, the Load Control rule action, and the Stop if Applied processing action.
  5. In the connection rule folder, create another connection rule that sends the request to the database. Configure the following properties for the connection rule:
    Matcher
    Select the All Incoming Connections Matcher.
    Rule Action
    Select the Switch to Database action. The Switch to Database action sends the request to the database that you specify.
    Database
    Enter the name of the database node in the Management Console tree.
    Processing Action
    Select the Continue processing action.
  6. Save the connection rule set for the primary Dynamic Data Masking Server.
  7. In the Management Console for the secondary Dynamic Data Masking Server, create a connection to the Db2 database. The database client must use the IBM JDBC driver to connect to the listener port that you define for the connection.
    If the Dynamic Data Masking Server installations are on the same machine, you must configure different listener port numbers for the primary and secondary servers.
  8. Add the Dynamic Data Masking service for DB2.
  9. Open the connection rule set for the Dynamic Data Masking service and create connection rules that are identical to the connection rules that you created for the primary Dynamic Data Masking Server except that the Load Control action priority levels are switched.
  10. Configure the following properties for the rule folder:
    Matcher
    Select the Incoming DDM Listener Port matcher.
    Incoming Port
    Enter the listener port number for the secondary Dynamic Data Masking Server.
    Rule Action
    Select the Folder rule action.
    Processing Action
    Select the Stop if Matched processing action to process only the connection rules in the rule folder.
  11. Configure the following properties for the first rule in the rule folder:
    Matcher
    Select the All Incoming Connections matcher.
    Rule Action
    Select the Load Control rule action. Configure the following Load Control properties:
    • Host
      . Enter the names of the Dynamic Data Masking Servers. Click the plus sign (+) to add additional servers.
    • Port
      . Enter the port number for each of the Dynamic Data Masking Servers.
    • Priority
      . Enter a priority number for each of the Dynamic Data Masking Servers. Enter one (1) for the secondary Dynamic Data Masking Server and zero (0) for the primary Dynamic Data Masking Server.
    Processing Action
    Select the Continue processing action.
    The following image shows an example of the connection rule:
    The rule uses the All Incoming Connections matcher, the Load Control rule action, and the Stop if Applied processing action.
  12. Configure the following properties for the second rule in the rule folder:
    Matcher
    Select the All Incoming Connections Matcher.
    Rule Action
    Select the Switch to Database action.
    Database
    Enter the name of the database node in the Management Console tree.
    Processing Action
    Select the Continue processing action.
  13. Save the connection rule set for the secondary Dynamic Data Masking Server.
You can connect to the Db2 database through either of the Dynamic Data Masking Servers. If one of the Dynamic Data Masking Servers is unavailable, the request goes through the other Dynamic Data Masking Server.
To verify which Dynamic Data Masking Server receives requests, you can run Dynamic Data Masking in debug mode and check the log files to see which server provides debug information. You can also define database nodes for different databases on each server and check which database Dynamic Data Masking sends the request to.
0 COMMENTS
We’d like to hear from you!