To use databases in your business or User Dialog processes, start with defining database configurations for each database you want to use. After you have configured the databases (data sources) you can use them in your process steps. The process steps reference only the database configuration ids. Therefore, you can use different database configuration settings for each environment, i.e., development, test, and production servers.

Database Configuration Editor

The database configuration editor lets you configure the databases you use in your project.

Database Configuration Editor

Database Configuration Editor

  • All Database Configurations A list of all database configurations defined in this project. A red or green icon indicates the result of the connection test automatically executed upon saving a database configuration.

  • New Add a new database configuration

  • Remove Remove the selected database configuration

  • Test Connection Test database connection. A dialog shows the result status. In case of failure, the reason is displayed

  • SQL Opens a SQL editor to set up SQL Statements. The SQL Editor displays the query result in a result table

  • Database Select the type and driver of the database you use. We ship some often used and well-tested drivers with the Axon Ivy Designer.

    The field Max Connections lets you specify the maximum number of concurrent connections to this database.

    Choose an Icon that represents the database. The icon will also be used as decorator icon on Database process elements that reference this database.

  • Connection Properties Specify the properties for the database connection.

  • Additional Connection Properties If your database needs additional settings, you can use this section to define these properties.

Dynamic Properties

You may need to adjust property values for multiple runtime environments. E.g., use different database hosts for testing and production, consequently with other credentials and connection URIs.

If you anticipate this need, then you can simplify these configuration adjustments for operations by using Dynamic Configuration expressions in both properties and other configuration values. E.g., the property databaseName=${ivy.var.cloudDb} is evaluated at runtime and has the value of the variable called cloudDb. Thus, your database name is now configurable using variable cloudDb. Operations need to set this variable correctly; they do not need to dive into the configuration of this external database.