The Data Masker Create/Edit Rule Controller Form

This form is used to create and edit a Data Masker Rule Controller. Rule Controllers contain the login information which other masking rules will use to connect to a remote database. The title text and button label on the form will change as is appropriate to the create or edit mode. In the example screen shot above, the form is editing an existing Rule Controller.

A masking set must have a Rule Controller and may have several Rule Controllers. Rule Controllers are designed to offer connectivity to a single Oracle schema. If a masking set requires connections to multiple schemas (which can be in different databases), then it will be necessary to create a new Rule Controller for each schema. A masking set can have an unlimited number of Rule Controllers and they can connect to the same Oracle schema if required.

The Rule Controller form has two tabs on the left hand side. The Target DB Login tab contains connection details for the Rule Controllers dependent rules. The Options tab contains additional configuration options and also tools which can refresh various components such as the schema structure.

What the items in the Target DB Login tab do

The login panel on the left hand side of the form is used to configure the Oracle login for the Rule Controller. Rule Controllers can be configured to connect via the standard Oracle SQL*Net using TNSNames or directly to the database via TCP/IP. If the TNSNames method is used, the PC must have Oracle SQL*Net version 9 (or higher) installed. In general if it is possible to connect to the target schema with a TNSName via an Oracle Utility such as SQL*Plus then the Data Masker software should not have any difficulties connecting.

Login Name and Password

This is the login name of the schema to which the Rule Controllers dependent rules will connect and when they execute.

Connect via TNSNames and Connect via TCP/IP

These two options determine the method the rules will use when connecting to the target schema. The TNSNames mode requires a valid Oracle TNSName identical to that which would be used in an SQL*Plus session. The TCP/IP mode requires the host name, port and SID of the database.

Optional Proxy Configuration

Usually the Login Name field references the schema that contains the tables to be masked - however the Login Name can be a proxy schema which only has select and update access to the real target schema. If the Login Name is a proxy schema, the name of the schema that actually owns the tables should be entered in this panel. The only real benefit to using a proxy schema is that it can contain the server side audit table that the Data Masker software uses to record the masking rule actions. This enables the audit table to be held separately from the target schema.

What the items in the Options tab do

Target Database Version

The Data Masker software will adjust its masking algorithms so as to be as efficient as possible. For some rules, higher Oracle database versions offer the opportunity for speed improvements.

Audit Table Configuration

A small table named DMO_AUDITTAB, used for auditing purposes, is required to be located in the target schema (or in the proxy login - see above). The Data Masker software will use this audit table to record the actions of each rule. The audit table is also used to determine which rules need to be executed in the event of a re-start. More information on the server side audit table can be found in the Audit Table help file.

Refresh Tables and Indexes

The Rule Controller maintains the schema structure information for the connection schema as well as the login information. This button will activate a wizard (a series of walk through panels) which will refresh the schema structure held by the Rule Controller.

Create DBLink Table

This button launches the Create DBLink Table form which enables a remote table accessed via a database link to be created in the masking set.

Refresh Foreign Keys

This button connects to the target schema and refreshes the foreign key information held by the Rule Controller.

Refresh Triggers

This button connects to the target schema and refreshes the trigger information held by the Rule Controller.

Refresh Row Counts

The Data Masker software does not need to know the number of rows in the target schema tables. However, it is very useful to have such information when developing masking rules. This button offers the ability refresh the row count values held by the Rule Controller with the current target schema table row counts. It is possible to use the estimated row counts provided by the Oracle statistics if desired.