Custom Configurations for the In-Memory DB (OLAP)

Turns on encrypting of the database files. Newly saved files are encrypted if this is set using the AES-256-CBC algorithm. On/off switch.Note:

If "crypt" is enabled,

• it is not possible to set the log-level of OLAP Server to "trace" or "debug". Both log levels could make the log file contain information about database contents, and since log files are always readable, this would conflict with the purpose of the "crypt" option.
  
• it is not possible to enable the "audit" option in palo.ini. The data storage for audit information currently cannot be encrypted, and so that storage would again contain readable data information which would conflict with the purpose of the "crypt" option.

For decryption, just remove crypt from palo.ini and on next "save" the database files will be decrypted, i.e. if a value is written to a cube, it will be decrypted (with all its files). It will not be automatically decrypted. Don't remove crypt-key otherwise it won't be possible to load encrypted files. Remove the crypt-key after you're sure that everything was decrypted.

Procedure to decrypt all databases:

• remove crypt from palo.ini
  
• restart OLAP service
  
• use Jedox example (ETL-Tools) "Database Copy"
  
• copy all databases
• everything will be back to decrypted status

Note: when the OLAP API function /dimension/create is called with parameter mode=1, then not only is a dimension created, but the OLAP server will also execute all database scripts from the Subsets directory, if it exists in the directory indicated by defaults-directory palo.ini key.

-legacy
-binary

Binary: dimensions are saved to database_DIM_*.csv and database_DIM_*.bin (if available), similar to cube save/load.

Note: dimensions that have been saved as binary files are not portable between Linux and Windows.

1. automatic
2. drilldown
3. drilldown-base
4. integrator
5. custom

1. Drills through if ETL is available, or else drills down without taking rule-calculated values into account.
2. Drills down to the stored or rule-calculated values at the cube base level.
3. Drills down at the cube base level, without taking rule-calculated values into account.
4. Drills through to reveal relational data from ETL.
5. Uses the same logic as older Jedox versions and performs a drillthrough according to the OnDrillThroughExt function, which is part of the SVS script. Note that we do not recommend this mode as it may require maintenance by the customer when upgrading the Jedox environment.

Examples:
journal-flush-interval 0
journal-flush-interval disabled

For details on log levels and parameters, see .

When multiple password patterns are defined, the last one has priority.

<info>

<bulk error>

<bytes>

Generates an error if splashing requires more space than the first number.

Generates a warning entry if splashing requires more space than the second number.

Generates an info entry if splashing requires more space than the third number.

Generates an error if splashing operations in a bulk request require in total more space than the fourth number.

“Bulk” requests are those where multiple values (cells) are changed in a single request. PALO.SETDATA_BULK() function uses this, but also ETL cube loads. In previous versions, the check was executed for each single value change in the bulk request. This new value will additionally check the overall memory requirement for the whole bulk.

Without a change of the default value (empty or 0) the overall memory requirement for the whole bulk will not be checked.

The fifth number is an estimation of the memory used for one cell in bytes.The used default value is 16 (entry: empty or 16).

This value influences how the memory consumption of values is calculated, i.e. how much memory OLAP assumes for individual base cell values. The previously used value was hardcoded to 16 bytes; this value may be too low in reality. It can now be changed via this value. A higher value (e.g. 32) will increase the assumed memory for splashing operations and the value of number four will be exceeded earlier.

Example: splash-limit 2000 1000 200 8000 32

ERROR_splash_THRESHOLD_EXCEEDED = 5027

If the string data limit is set to a high number (more than 100K), the rebuild should be scheduled with string-storage-rebuild-schedule. If no time is set, an error message will be logged during startup (but server will start).

For details, see OLAP String Storage and its Usage in Jedox .

Example: string-storage-rebuild-schedule 03:15

system-restore

New fresh System DB is created when System database.csv file is missing.

template-directory

t

<directory>

Directory of online documentation:
template-directory Binary/Api.

trace

T

<logname>

Enables trace logging. Once enabled, a trace log file will be created in the olap/data directory for each opened port per startup (note: you can specify just the filename for the data folder - thus it will be saved in the olap/data directory - or a full path to another directory, such as /full/path/traceFolder/<logname>).

undo-file-size

u

<number of
bytes per lock>

In a locked cube area it is possible to undo changes. Each lock can use <number of bytes per lock> bytes in files for storing changes:
undo-file-size 100000000

undo-memory-size

m

<number of bytes per lock>

In a locked cube area it is possible to undo changes. Each lock can use <number of bytes per lock> bytes in memory for storing changes:
undo-memory-size 10000000

use-cube-worker

Y

Uses cube worker.
Can react on cell value changes.
On/off switch.

use-dimension-worker

W

Uses dimension worker. Can react on creation, deletion, and renaming of an element in a specified dimension.
On/off switch.

If no value has been set, then error is the default value.

When activated, arrays with group names are not retrieved from AD, so SVS authentication script receives empty array with group names.

worker-pool-init-size 5

worker-pool-max-size 32

The workerlogin parameter has one additional argument. If you supply workerlogin on the command line and in the configuration file, then the value supplied in the configuration will be taken. If the http option is supplied for port A on the command line and for port B in the configuration file, then both ports A and B are used.

*Authorization and authentication modes will be deprecated in Jedox 2024.2.