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

JDBC Logging

JDBC Logging

If you use the DDM for JDBC service, you can configure logging on the client machine to debug the JDBC wrapper.
The Dynamic Data Masking installation contains a template configuration file for JDBC logging. You can find the template in the following location:
<Dynamic Data Masking installation>\Wrappers\jdbc\template.jdbcLogConfig.properties
The template.jdbcLogConfig.properties file contains the following properties:
ddm.logfile.name
Specifies the file name of the log. Modifiable.
Default value: %h/DDM_GENJDBC.log
ddm.logging.level
Specifies the log level. Modifiable.
You can specify the following log levels:
  • ERROR. Provides the complete details of all errors and exceptions that affect the Dynamic Data Masking processes.
  • WARN. Provides information about exceptions that do not affect the Dynamic Data Masking processes, but do affect Dynamic Data Masking functionality.
  • INFO. Provides information about the normal behavior of the Dynamic Data Masking Server, such as when a service starts or stops and when a user logs in.
  • DEBUG. Provides information for debugging issues, such as client connection details to the database and the Dynamic Data Masking Server, connection rule results, and original and modified requests to the database.
Default value: INFO
ddm.logfile.limit
Specifies the maximum size of the log file before the logger creates a new file. For example, you might enter 500KB or 200MB. A value of zero (0) indicates that there is no file size limit. Modifiable.
Default value: 0
ddm.logfile.count
The number of backup files the appender creates before it overwrites the oldest file. Modifiable.
Default value: 1
ddm.logfile.append
Specifies whether you want to overwrite the log file when you start the application. A value of false indicates that you want to overwrite the log file with a new file. A value of true indicates that you want to add new log information to the existing log file.
ddm.logfile.encoding
The log file character encoding system. Modifiable.
Default value: UTF-8
ddm.log.format
Specifies the logging format. Not modifiable.
Default value: %1$tm/%1$td %1$tH:%1$tM:%1$tS,%1$tL [%2$s] %4$s - %5$s %6$s %n
The following properties are used in the configuration of the log file name and are replaced at runtime:
  • %t. The system temporary directory. For example,
    %t/DDM_GENJDBC.log
    causes the logs on Solaris to be written to
    /var/tmp/DDM_GENJDBC.log
    and the logs on Windows 7 to be written to
    C:\Users\<username>\AppData\Local\Temp
    .
  • %h. The value of the user.home system property.
  • %g. The generation number to distinguish rotated logs. If the file count is greater than one, the generation number is added to the end of the file name.
  • %u. A unique number used to resolve conflicts. If FileHandler tries to open the file when the file is in use by another process, it increments the unique number and tries again until it finds a file name that is not in use.
  • %%. Translates to a percent sign (%).
When you modify the JdbcLogConfig.properties file, you must restart the application for the new properties to take effect.
The following text is an example of a JDBC configuration file:
######################## description of special components for log file name starts ######################## # %t The system temporary directory "%t/DDM_GENJDBC.log" would typically cause log files to be written on Solaris to /var/tmp/DDM_GENJDBC.log whereas on Windows 7 they would be typically written to C:\Users\<username>\AppData\Local\Temp # %h The value of the "user.home" system property # %g The generation number to distinguish rotated logs. If the file count is greater than one, then the generation number will be added to the end of the generated filename. # %u A unique number to resolve conflicts. FileHandler tries to open the filename and finds the file is currently in use by another process it will increment the unique number field and try again. This will be repeated until FileHandler finds a file name that is not currently in use. # "%% %%" translates to a single percent sign "%" ######################## description of special components for log file name ends ######################## # log file name and location ddm.logfile.name=%h/DDM_GENJDBC.log # level for ddm log file ddm.logging.level=INFO # max size of log file (in bytes). 0 means unlimited ddm.logfile.limit=0 # max number of log files ( minimum is 1) ddm.logfile.count=1 # whether log file gets appended after restart of JVM. (false means old logs gets deleted) ddm.logfile.append=true #encoding of log file ddm.logfile.encoding=UTF-8 # log format ddm.log.format=%1$tm/%1$td %1$tH:%1$tM:%1$tS,%1$tL [%2$s] %4$s - %5$s %6$s %n

0 COMMENTS

We’d like to hear from you!