Stored Procedure Accelerator Guide for Oracle

9.8.2
- 9.9.3
- 9.9.2
- 9.9.1
- 9.9
- 9.8.4
- 9.8.3
- 9.8.1
- 9.8.0

Back Next

Configuring the StoredProc Rules

Configure the StoredProc rules in the

Rule Editor

Select the MatchProcNamesFolder rule and click

Action

Edit

The

Edit Rule

window opens.

The Text field of the matcher contains a template that you can use to enter the stored procedure names. Replace "proc name 1," "proc name 2," and "proc name 3" with stored procedure or user-defined table function names.

For example, you might enter the following text in the Text field:

.*Proc_Dept_Emp.*|.*Func_Job_Location.*

The following image shows the MatchProcsNamesFolder rule matcher parameters:

The MatchPRocNamesFolder rule uses theText matcher and has .*Proc_Dept_Emp.*|.*Func_Job_Location.* entered in the Text field.

Click

The

Rule Editor

closes.

Click

File

Update Rules

to save the security rule.

Select the DefMaskRSSym rule and click

Action

Edit

The

Edit Rule

window opens.

Create the following symbols:

ExplicitRuleSet: In the
Symbol Name
field, enter ExplicitRuleSet. In the
Symbol Value
field, enter the name of the rule set that contains the masking rules. For the template rule sets, enter StoredProcMasksTmpl. If you want to use the HR example rule set, enter HRStoredProcMasksRS. In the Keep Per Session field, enter No.
ORACLE_DDM_TEMPDB: In the
Symbol Name
field, enter ORACLE_DDM_TEMPDB. In the
Symbol Value
field, enter the name of the Oracle database schema where Dynamic Data Masking will create the temporary objects. In the Keep Per Session field, enter No.

The following image shows the DefMaskRSSym rule action properties:

The DefMaskRSSym uses the Define Symbol rule action. The Symbol Name is ExplicitRuleSet and the Value is StoredProcMasksTmpl.

Optionally, if you have a function that you want to use to determine whether to mask the stored procedure, create the following additional symbols:

MATCH_FUNCTION: In the
Symbol Name
field, enter MATCH_FUNCTION. In the
Symbol Value
field, enter the fully qualified name of the PL/SQL decision making function. The function must return 0 or 1. If the function returns 1, Dynamic Data Masking masks the stored procedure. If the function returns 0, Dynamic Data Masking does not mask the stored procedure.
MATCH_FUNCTION_PARAMS: In the
Symbol Name
field, enter MATCH_FUNCTION_PARAMS. In the
Symbol Value
field, enter the number of arguments in the original stored procedure that you want to pass to the decision making function. The count starts from the first argument.

The following image shows the DefMaskRSSym rule action with the additional symbols:

The MATCH_FUNCTION symbold definition is DDMADMIN_DECISION_FUNCTION. The MATCH_FUNCTION_PARAMS symbol value is 2.

Click

The

Rule Editor

closes.

Click

File

Update Rules

to save the security rule.

Select the MaskProcs rule and click

Action

Edit

The

Edit Rule

window opens.

In the rule action Class Path field, enter the file path of the stored procedure accelerator .jar files, separated by a semicolon (;).

You can find the .jar files in the following directory:

<Dynamic Data Masking installation>\Accelerators\StoredProcedureMasking\lib

For example, you might enter:

C:\Program Files\Informatica\DDM\Accelerators\StoredProcedureMasking\lib\StoredProcedureMasking.jar;C:\Program Files\Informatica\DDM\Accelerators\StoredProcedureMasking\lib\MultipleStatementMasking.jar

The Class Name must be ProcMaskerOracle.

Click

The

Rule Editor

closes.

Click

File

Update Rules

to save the security rules.

Click

File

Exit