Environment Variables

Configuration Types

Depending on the layer that defines the configuration variables, they have the following priorities:

RuntimeEnvironmentDeploymentModule

Highest precedence:

No rebuild or restart of the application is required when a configuration is changed.
You can use the Configuration API to apply changes in the Runtime configuration.

Second precedence:

No rebuild is required when a configuration is changed. However, you should restart the application to apply the environment changes.
Usually, the Environment configurations are provided during the application deployment, as part of application descriptor (e.g. Define environment variable for container in Kubernetes, or in Cloud Foundry App Manifest).

Third precedence:

Rebuild and redeployment are required.
"Default" deployment (ROOT.war) configuration variables are taken from dirigible.properties properties file. You can find a sample here.

Lowest precedence:

Rebuild and redeployment are required.
"Default" module (e.g. dirigible-database-custom.jar, dirigible-database-h2.jar) configuration variables are taken from dirigible-xxx.properties properties files. You can find samples here and here.

Note

The precedence order means that if the there is an Environment variable with name DIRIGIBLE_TEST and Runtime variable with the same name, the Runtime variable will have higher priority and will be applied.

You can find all applied configuration values under the Configurations View.

Configuration Parameters

HDI Environment Variables

Parameter	Description	Default*
XSK_HDI_SUPPORTED	Whether the HDI API is supported by the database (e.g. HANA)	`true`
XSK_HDI_ONLY	Database models to be processed only via the HDI API	`false`
XSK_SYNCHRONIZER_XSJOB_ENABLED	Whether the XS Jobs synchronizer is enabled	`false`

Additional Information

To find all Eclipse Dirigible related environment variables, see Environment Variables.