Use the staging level of the One Identity Manager database to specify whether a test database, development database or a live database is being dealt with. A number of configuration settings are controlled by the staging level. These are set when you modify the staging level.
Setting | Database Staging Level | ||
---|---|---|---|
Development Environment | Test Environment | Live Environment | |
Color of the One Identity Manager tools status bar. |
none |
Green |
Yellow |
Maximum DBQueue Processor runtime |
20 minutes |
40 minutes |
120 minutes |
Maximum number of slots for DBQueue Processor |
3 |
5 |
Maximum number of slots according to the hardware configuration |
To modify a database staging level
The DBQueue Processor configuration settings are configured for normal operations and must not be modified normally. The number of configuration settings is reduced in the case of test and development environments because there may be more databases on one server.
If you have to change the settings for test or development environments on performance grounds, you must modify the following configuration parameter settings in the Designer.
Configuration parameter | Meaning |
---|---|
QBM\DBQueue\CountSlotsMax |
This configuration parameter specifies the number of maximum slots available. Enter the value 0 to use the maximum number of slots according to the hardware configuration. |
QBM\DBQueue\KeepAlive |
This configuration parameter regulates the maximum runtime of the central dispatcher. Tasks on slots currently in use are still processed when the timeout expires. Then the slot database schedules are stopped and the central dispatches exits. The lowest permitted value for runtime is 5 minutes; the highest value is 720 minutes. |
In certain circumstances, it is necessary to store encrypted information in the One Identity Manager database.
Value | Description |
---|---|
RSA |
RSA encryption with AES for large data (default). |
FIPSCompliantRSA |
FIPS certified RSA with AES for large data. This method is used if encryption must match the FIPS 1040-2 standard. The local security policy "Use FIPS compliant algorithms for encryption, hashing, and signing" must be enabled. |
|
NOTE: If you have not set the configuration parameter "Common\EncryptionScheme", RSA is used. |
|
NOTE: It is recommended that you create a backup before encrypting the database information in a database. Then you can restore the previous state if necessary. |
|
NOTE: It is recommended that you create a backup before encrypting the database information in a database. Then you can restore the previous state if necessary. |
To create a new database key and encrypt the One Identity Manager database
Open Launchpad and select Encrypt database. This starts the program "Crypto Configuration".
The key file (*.key) is created. The file browser is closed. Path and file name are displayed under <Private key>.
This establishes which data is encrypted.
The data encryption is started. Conversion progress is displayed.
|
NOTE: To change a database key, you need the key file with the old database key. The key is change and saved in a new key file. |
|
NOTE: It is recommended that you create a backup before encrypting the database information in a database. Then you can restore the previous state if necessary. |
To change a database key and encrypt the One Identity Manager database
The file browser is closed. Path and file name are shown.
The key file (*.key) is created. The file browser is closed. Path and file name are displayed under <Private key>.
This establishes which data is encrypted.
The data encryption is started. Conversion progress is displayed.
© 2022 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy