Jobs page

This section describes how users can view, run, and cancel jobs from the Environment → Jobs page.

The Environment → Jobs page displays all the jobs present in the given environment. It also displays information about the given environment under the Environment Properties section.

The following job types are supported in a masking environment:

1. Profiling

2. Masking

The following job types are supported in a tokenize/reidentify environment:

1. Profiling

2. Tokenization

3. Re-Identification

Sortable and filterable columns are Job ID, Name, Rule Set, Type, Status and Completed Time.

Submitting a job

To submit or resubmit a job, Click the (…) button to the right of the corresponding job row under the Actions column and click Run. Editing/Deleting a Job is not allowed while it is running.

Upon submitting the job, the masking engine will check if there are enough resources allocated to simultaneously running jobs to determine whether to run or queue the submitted job. There are two resources that the submitted job will be verified against.

1. Maximum memory for all running jobs.

   • This limit defaults to a dynamic calculation of 75% of the entire system's available memory minus 6GB, which is reserved for the masking web application. This calculation can be manually overridden by setting the general application setting MaximumMemoryForJobs. To revert a manually overridden limit back to the dynamically calculated limit, set the MaximumMemoryForJobs to 0.

2. Maximum number of simultaneously running jobs.

   • This limit defaults to 7 simultaneously running jobs. However, this default value can be overridden by setting the general application setting NumSimulJobsAllowed to a different value. The engine also provides a dynamic limit for this resource, which takes the number of available cores on the system minus 1, reserved for the masking engine. This dynamic limit can be used by setting NumSimulJobsAllowed to 0.

If the submitted job causes all of the currently running jobs to exceed either of those limits, the job will be queued and run at a later time when enough of the other jobs stop running to free up resources. To view the the position of the job in the queue, navigate to the Monitor Screen.

Submitting a Multi tenant Jobs

When the Multi tenant option is selected while creating a job, the User can select connector at the time of running a job. This option allows existing rulesets to be reused to mask identical schemas via different connectors.

1. In-Place Job → The User can select the Target connector at the job execution time
   

   

2. On-The-Fly Job → User can select Source and Target connectors at the job execution time
   

   

Stopping a Job

To stop a job, Click the (…) button to the right of the corresponding job row under the Actions column and click Cancel.

On clicking Cancel Action, it will prompt for confirmation. Click on Confirm to cancel the job.

On clicking Confirm, the job will be cancelled and the status will be changed to CANCELLED.

Stopping a RUNNING job can result in corrupted or semi-masked data. Stopping a QUEUED job will have no impact on the data source since the execution of the job has not yet begun. If email notifications are enabled, stopping a QUEUED job will send an email to the user who created the job indicating that it has been cancelled by the user who stopped the job.

Export Environment

The Environment → Jobs page also provides a way to Export the current environment.

Clicking on Export Environment will open the below dialog.

An optional passphrase for encrypting the export file can be specified. Click Export to export the environment. All the information for the current environment (connectors, rule sets, jobs, and so on) is exported to a file.

Clicking on Export will create an Aysnc task and information will appear related to the created task at the bottom of the page.

Users can also track export status from Async Task Status.