Automated masking and exit is controlled by providing the appropriate command line options when the application starts. The options required to automate the masking process are:

<Masking Set Filename>

The name of the masking set to load. This must be a full path including the drive and directory information. The Data Masker software will not use default directories in command line mode. If the masking set filename contains spaces, remember to enclose it in double quotes when placing it on the command line otherwise the Windows operating system will present it to the Data Masker software as multiple command line options.

-R

The signal to Run the masking set and perform the masking operations.

-X

The signal to eXit after the masking set has completed. In order to determine if the masking set completed successfully or failed with an error it is necessary to examine the application exit code (see the discussion below).

-S <param>

The login Substitution parameter. The masking set can be configured with dummy login information in the Rule Controllers and have that information substituted by the command line. This functionality enables the target of a masking set to be determined at runtime. The format of the login substitution parameter is always

<DummySchema>@<DummyTNSName>=<RealSchema>/<RealPassword>@<RealTNSName>

The Login Substitution Parameter section below contains more information and examples.

If the Masking Set filename is specified and the -R option is omitted then the Data Masker application will simply load the Masking Set and return to manual operating mode.

Exit Codes

When run from a command line, the Data Masker software will return an exit code via the standard DOS mechanism. If the last run of the masking rules was a success then this exit code will always be zero. Any non-zero exit code implies that an error occurred while opening the masking set or while running the masking rules. If a non-zero exit code is returned the log file should always be examined to determine the error that occurred. Some of the more common exit codes are:

101

The masking set was not found. See the log file for more information.

201

The masking set run was cancelled by user request.

301

Errors occurred during the run of the masking set. See the log file for more information.

1000-1999

Errors occurred during the pre-run checks of the masking set. See the log file for more information.

The exit code value is returned using the Windows standard mechanisms and can be determined via any of the available Windows methods. The most common way to view the return code is by using the DOS echo %errorlevel% command. The script output below shows such an operation. The 301 exit code means the masking set execution failed with an error.

C:\Program Files\Data Masker for Oracle>start /wait Datamasker.exe C:\Net2000\DMO_TestSets\DMTest.MaskSet -R -X
C:\Program Files\Data Masker for Oracle>echo %errorlevel%
301
C:\Program Files\Data Masker>

There is an important consideration which must be noted when launching Windows applications from a command line. The Command application will, by default, launch a Windows application as a separate process. Once started, the Command application will not monitor the running Windows application process. In effect, this behaviour means that immediately after launching the Windows application, the Command application will return to the DOS prompt and continue with the next command statement. It is not possible to retrieve the exit code in such circumstances and the next operation in the Command application will begin to process long before the masking set has completed.

If it is necessary for the Command line application to wait until the masking set has executed (and the Data Masker software has shutdown) before it executes the next operation, then the Data Masker software must be launched with the DOS start /wait command. The example below illustrates these concepts:

C:\Program Files\Data Masker for Oracle>REM the errorlevel will be set and the next command will only
C:\Program Files\Data Masker for Oracle>REM    be performed once the masking set is complete
C:\Program Files\Data Masker for Oracle>start /wait Datamasker.exe C:\Net2000\DMO_TestSets\DMTest.MaskSet -R -X
C:\Program Files\Data Masker for Oracle>echo %errorlevel%
C:\Program Files\Data Masker for Oracle> ... perform next command

C:\Program Files\Data Masker for Oracle>REM the errorlevel will always be zero and the next command will be
C:\Program Files\Data Masker for Oracle>REM    performed immediately without waiting for the Data Masker software
C:\Program Files\Data Masker for Oracle>REM    to complete
C:\Program Files\Data Masker for Oracle>Datamasker.exe C:\Net2000\DMO_TestSets\DMTest.MaskSet -R -X
C:\Program Files\Data Masker for Oracle>echo %errorlevel%
C:\Program Files\Data Masker for Oracle> ... perform next command

The Login Substitution Parameter

The Login Substitution Parameter always follows the -S command line option and is used to replace dummy values configured in the Rule Controller with values specified on the command line. The format of the login substitution parameter is always

<DummySchema>@<DummyTNSName>=<RealSchema>/<RealPassword>@<RealTNSName>

For example, a Rule Controller might be configured with a schema of FOO and a TNSName of BAR. In that case, a command line with the option -S FOO@BAR=scott/tiger@testdb1 would check each Rule Controller in the masking set and substitute the real connection information of scott/tiger@testdb1 in place of FOO@BAR. The dummy values of FOO@BAR serve as place holders for the real information and allow the appropriate Rule Controller to be updated at run time. A masking set can have multiple Rule Controllers. In that circumstance, multiple substitution parameters can be configured as shown below:

-S FOO@BAR=scott/tiger@testdb1 -S ABC@TESTDB=dmtest/dmtestpass@Test10G

Examples

Load a Masking Set file only

start /wait DataMasker.exe "C:\Program Files\Data Masker Oracle\Masking Sets\scott.maskset"

Load, Run and Exit

start /wait DataMasker.exe "C:\Program Files\Data Masker Oracle\Masking Sets\scott.maskset" -R -X

Load, Run and Exit and Substitute login details

start /wait DataMasker.exe "C:\Program Files\Data Masker Oracle\Masking Sets\scott.maskset" -R -X -S FOO@BAR=scott/tiger@testdb1