Every Job Orchestrator includes a set of Application Settings that control the operational behavior of compliance nodes.
An application setting is a name-value pair organized into categories. These settings influence how operations are executed and managed by the Job Orchestrator.
Application settings are system-level configuration parameters and are not intended to be modified frequently. Changing these values can significantly affect the behavior and performance of the system.
Before modifying any application setting, carefully review the description and intended purpose of the setting.
Application settings grid
Application settings are organized into several categories, including:
-
General settings
-
Mask settings
-
Job settings
-
Algorithm settings
-
Database settings
-
Profile settings
-
ASDD settings
The settings are displayed in a grid view that allows filtering, sorting, and editing.
Modifying application settings
Follow these steps to modify an application setting:
-
Navigate to the Application Settings tab on the Job Orchestrator details page.
-
The Application Settings grid displays all available settings grouped by category.
-
Use the column headers to sort or filter settings.
-
To locate a specific setting, enter the Setting Name in the search field located in the table header.
-
Click the pencil icon in the rightmost column of the desired setting.
-
Update the value:
-
Boolean settings display a dropdown with true and false options.
-
Other settings provide a text input field.
-
-
Click outside the field to open the confirmation dialog.
-
Choose Save to apply the change or Discard to cancel it.
Application settings reference
The following table describes the available application settings and their functions.
General group settings
|
Setting Group |
Setting Name |
Type |
Description |
Default Value |
|---|---|---|---|---|
|
general |
EnableMonitorRowCount |
Boolean |
Controls whether a job displays the total number of rows that are being masked. Setting this to false reduces the startup time of all jobs. |
true |
|
|
NumSimulOperationsAllowedPerNode |
Integer [0, ∞) |
This setting limits the number of operations allowed to run simultaneously on a node. Setting this number to zero will lead to a dynamically calculated limit based on the number of available CPU cores. |
7 |
|
|
DataRetentionInterval |
Integer [-1, ∞) |
The length of time that specific historical data is retained. |
60 |
|
|
DataRetentionMaxDirectorySize |
Integer [-1, 100] |
The percentage of disk space allowed for all logfiles located in specific directories. |
10 |
|
MaximumMemoryForJobsPerNode |
Integer [0, ∞) |
When set to 0, the maximum memory for jobs is calculated automatically. Adjusting this default is only recommended for Containerization Masking if a limit in pod resources is not defined. |
0 |
NumSimulOperationsAllowedPerNode setting should be set based on node configuration. It is risky to run many jobs at once in an environment where you have scheduled more jobs than the system has memory for. When the system runs out of memory all jobs will fail.
Application Settings for property behavior
|
Setting Name |
Description |
|---|---|
|
MaximumMemoryForJobsPerNode |
If 75% of the app container's max memory limit - 6 GB. |
| NumSimulOperationsAllowedPerNode |
|
NumSimulOperationsAllowedPerNode setting should be configured based on the capacity of the compliance node. Running too many operations simultaneously on a node without sufficient system resources can lead to failures. For example, if the node runs out of memory, all operations currently executing on that node may fail. Administrators should ensure that the configured limit aligns with the available CPU and memory resources of the node.Algorithm group settings
|
Setting Group |
Setting Name |
Type |
Description |
|
|---|---|---|---|---|
|
algorithm |
DefaultNonConformantDataHandling |
String {DONT_MASK, FAIL, NULLIFY} |
Default algorithm behavior for Handling of Non-conformant Data patterns. |
DONT_MASK |
Database group settings
|
Setting Group |
Setting Name |
Type |
Description |
Default Value |
|---|---|---|---|---|
|
database |
DB2zDateFormat |
String |
Default Date String format to use for DB2 zOS if the database is not using one of the pre-defined IBM DB2 zOS Date String formats. Default is ISO Date String format. |
yyyy-MM-dd |
Mask group settings
|
Setting Group |
Setting Name |
Type |
Description |
Default Value |
|---|---|---|---|---|
|
mask |
DatabaseCommitSize |
Integer [1, ∞) |
Controls how many rows are updated (Batch Update) to the database before the transaction is committed. |
10000 |
|
|
DefaultStreams |
Integer [1, ∞) |
Default number of streams for a masking job. |
1 |
|
|
DefaultUpdateThreads |
Integer [1, ∞) |
Default number of database update threads for a masking job. |
1 |
|
|
DefaultMaxMemory |
Integer [1024, ∞) |
Default maximum memory for masking jobs (in megabytes). |
1024 |
|
|
DefaultMinMemory |
Integer [1024, ∞) |
Default minimum memory for masking jobs (in megabytes). |
1024 |
|
|
CharStreamingBufferLimitRate |
Integer [1, 50] |
Used for calculating maximum allowed buffer size for Character streaming parsers to buffer data. Only used in JSON file and Document store type masking. |
25 |
|
MdsQueryDataTableBatchSize |
Integer [1, 5000] |
Controls the table query batch size for database masking job and report generation. Increasing the batch size results in faster processing time of the masking job but will use more heap memory. |
100 |
|
|
DefaultHybridBinaryConversion |
String {HEX, UTF8} |
To handle how unmasked binary data should be written to the target file in case of a Database to Delimited File job. HEX is preferred for safe binary-to-hex conversion. UTF-8, a legacy option, may cause corruption and is not recommended. |
HEX |
|
|
DefaultHybridBinaryHexPrefix |
String |
A prefix that should be added to the HEX string while converting unmasked binary data in the case of a Database to a Delimited Filejob. |
\x |
ASDD group settings
|
Setting Group |
Setting Name |
Type |
Description |
Default Value |
|---|---|---|---|---|
|
ASDD |
DefaultMaximumColumnSize |
Integer [1, 65536] |
The maximum length of the column value to profile. Any value beyond that is truncated to this length for ASDD profiling and the remaining part is ignored. |
1024 |
|
DefaultTableSampleRows |
Integer [1, ∞) |
The number of database rows for the ASDD profiler to sample for each table. |
1000 |
|
|
|
DefaultAssignmentThreshold |
Integer [1, 100] |
The confidence threshold that must be met or exceeded for the ASDD profiler to make a data class and algorithm assignment. Assignment threshold can otherwise be set on a discovery expression level; see Create a discovery policy. |
1 |
|
|
DefaultJobExecutionStreams |
Integer [1, ∞) |
The number of streams to use by default for new ASDD profiler jobs |
1 |
|
|
DefaultNullFilterThreshold |
Integer [0, 100] |
The percentage of column values that must be null or empty to trigger an additional query to retrieve more column values. |
75 |
|
DefaultTableSampleLimitSeconds |
Integer [0, ∞) |
A subsequent not-null query is triggered if enough data is not fetched for a column during the initial sample query. This setting sets the query timeout for such queries, which can run forever for large tables. |
180 |
|
|
DefaultIncompleteMultiColumnBehaviour |
String {IGNORE, FAIL} |
How to handle Data Class assignment behavior for Multi-column algorithms. IGNORE will allow the Data Class assignment to Multi-column algorithms. |
FAIL |
|
|
DefaultJobLogLevel |
String {TRACE, DEBUG, INFO, WARN, ERROR} |
Log level for ASDD job logs i.e. individual table or file specific logs. Warning: The more detailed setting may log sensitive information when errors occur. Although this information can be very valuable when debugging a problem, it should be used with care. |
INFO |
|
|
|
DefaultMultipleProfilerExpressionAlgorithm |
String |
Default Multiple PHI masking algorithm which will be used when the Multiple Profiler Expression will be true for profile job. This value is used by the ASDD profiler. |
NullValueLookup |
Job group settings
|
Setting Group |
Setting Name |
Type |
Description |
Default Value |
|---|---|---|---|---|
|
job |
JobLoggingLevel |
String {Basic, Detailed} |
Controls the amount of information being logged from a job's output. Warning: the Detailed setting may log sensitive information when errors occur. Although this information can be very valuable when debugging a problem, it should be used with care. |
Basic |