The Central Configuration is where all global settings for a Domino installation are listed.
-
Go to the Admin portal.
-
Click Advanced > Central Config.
-
On the Configuration Management page, you can:
-
Click an existing record to edit its attributes.
-
Click Add Record to create a new setting. If no record is created in the application, the system uses the default value.
You must restart the Domino services for changes to take effect. To do this, click here to restart services.
-
These options relate to the Audit Log.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Enables Domino to store audit events and shows the Audit Log button. See Download the Audit Log. Domino recommends that you do not change this value unless you must disable auditing. | |
| ||
| Page size for the number of records fetched from MongoDB. | |
| ||
| The maximum memory limit used by PDF generation. If the memory usage is greater than 25 MB, temporal files are used. | |
These options relate to the Keycloak authentication service.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Enables Domino organization membership to synchronize with SAML identity provider attributes so that membership can be managed by the identity provider. | |
| ||
| Enables Domino’s user roles to synchronize with SAML identity provider attributes so that user role management can be managed by the identity provider. See Admin roles assignments through users role SAML attributes. | |
| ||
| If See Roles for more information. | |
| ||
| Enables Domino organization membership to synchronize with SAML identity provider attributes so that membership can be managed by the identity provider. | |
These options relate to the compute grid.
They are available in namespace common and must be recorded with no name.
| Key | Default | Description |
|---|---|---|
| ||
| Controls how often the garbage collector runs to delete old or excess persistent volumes. | |
| ||
None | Setting a value in minutes here will cause persistent volumes older than that to be automatically deleted by the garbage collector. | |
| ||
| Maximum number of idle persistent volumes to keep. Idle volumes in excess of this number will be deleted by the garbage collector. | |
| ||
| Maximum number of salvaged volumes to keep. Salvaged volumes in excess of this number will be deleted by the garbage collector. | |
| ||
| Setting a value in days here will cause salvaged volumes older than that to be automatically deleted by the garbage collector. | |
| ||
| Kubernetes storage class that will be used to dynamically provision persistent volumes. This is set initially to the value of | |
| ||
| Size in GB of compute grid persistent volumes. This is the total amount of disk space available to users in runs and workspaces. | |
| ||
| The number of seconds an execution pod in a deploying state will wait before timing out. | |
| ||
| The number of seconds an execution pod that cannot be assigned due to user quota limitations will wait for resources to become available before timing out. | |
| ||
| The number of seconds an execution pod in a preparing state will wait before timing out. | |
| ||
| This is the maximum number of executions each user will be allowed to run concurrently. If a user attempts to start additional executions in excess of this those executions will be queued until some of the user’s other executions finish. | |
These options customize MongoDB connections.
| Key | Default | Description |
|---|---|---|
| ||
| The maximum number of threads allowed to wait for a MongoDB connection. The | |
These options relate to datasets scratch spaces
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| This option sets the first datasets scratch space risk threshold in days. Scratch spaces with changes that have not been recorded as a snapshot for this duration are marked as medium risk. | |
| ||
| This option controls the second datasets scratch space risk threshold in days. Scratch spaces with changes that have not been recorded as a snapshot for this duration are marked as high risk. | |
These options relate to email notifications from Domino.
They are available in namespace common and must be recorded with no name.
| Key | Default | Description |
|---|---|---|
| ||
None | Hostname of SMTP relay to use for sending emails from Domino. | |
| ||
None | Username to use for authenticating to the SMTP host. | |
| ||
| Port to use for connecting to SMTP host. | |
| ||
| Whether the SMTP host uses SSL. | |
These options relate to Domino Environments.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| If set to | |
| ||
| Docker image URI for the initial default environment. | |
| ||
Domino Analytics Distribution Py3.6 R3.6 | Name of the initial default environment. | |
These options relate to the file contents download API endpoint.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Set to | |
These options relate to long-running workspace sessions and long-running jobs.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Defines how long a workspace must run in seconds before the workspace is classified as 'long-running' and begins to generate notifications or becomes subject to automatic shutdown. | |
| ||
| Set to | |
| ||
| Set to | |
| ||
| Maximum time (in seconds) that a user can set as the period between receiving long-running notification emails. Note | |
These options relate to long-running workspace sessions.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Set to | |
| ||
| Set to | |
| ||
| Longest time in seconds a long-running workspace will be allowed to continue before automatic shutdown. Users cannot set their automatic shutdown timer to be longer than this. | |
These options relate to Model APIs.
They are available in namespace common and must be recorded with no name.
| Key | Default | Description |
|---|---|---|
| ||
| Default number of instances per Model used for Model API scaling. | |
| ||
| Maximum number of instances per Model used for Model API scaling. | |
| ||
| Key used in Kubernetes label node selector for Model API pods. | |
| ||
| Value used in Kubernetes label node selector for Model API pods. | |
These options relate to the on-demand Spark clusters.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| Frequency in seconds to run status checks on on-demand Spark clusters. | |
| ||
| File system path on which Spark worker storage is mounted. | |
| ||
None | Option to supply alternative default configuration directory for on-demand Spark clusters. | |
| ||
| Minimum amount of memory in MiB to use for Spark worker overhead. | |
| ||
| Spark worker overhead scaling factor. | |
The following configuration settings are used for caching.
| Key | Default | Description |
|---|---|---|
| ||
| Use this key to modify the period (in months) of historical data that the Control Center uses. You might have to change this value to less than Caution | |
| ||
| Specifies how often the cache is refreshed in minutes. This cache is used in the Control Center and improves performance. However, if the cache is refreshed every 30 minutes some recent data will not be included in the reports. | |
This option is available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
String of comma-separated project paths. For example,
| ||
These options relate to project visibility settings.
They are available in namespace common and must be recorded with no name.
Key | Default | Description |
| ||
| If set to | |
| ||
| Controls the default visibility setting for new projects. Options are | |
| Key | Default | Description |
|---|---|---|
| ||
| The maximum number of input files to compare. | |
| ||
| The maximum number of input file comparisons that will be found. If this value is reached, the comparison will stop. | |
| ||
| The maximum number of result files to compare. | |
| ||
| The maximum number of result file comparisons that will be found. If this value is reached, the comparison will stop. | |
These options relate to the User Activity Reports.
| Key | Default | Description |
|---|---|---|
| ||
| Sets the default recipient for the User Activity Report. To access this report, go to Admin > Advanced > User Activity Report. | |
| ||
| When | |
| ||
| Specifies the number of days to report for recent activity in the User Activity Reports. For example, the default value includes activity within the past 30 days in the Recent Activity section. | |
| ||
| Defines the frequency for automatically scheduled User Activity Reports. The default cron string value is set to daily at 02:00. | |
| ||
Empty | Identifies a comma-separated list of email addresses that receive automatic scheduled User Activity Reports. This is not shown in the Central Configuration unless it is set explicitly. Example values are: email1@domain.com, email2@domain.com. | |
Use these options to customize the Domino application with your organization’s brand. See White Labeling.
| Key | Default | Description |
|---|---|---|
| ||
N/A | Set a URL that directs your users to a web-based form or email address (mailto:support@domain.com). | |
| ||
N/A | Set the custom HTML to show immediately above the page footer. | |
| ||
N/A | Set the URL for the image that you want shown in the footer.
The image displays on the same line as the Domino logo.
If | |