DataSource configuration reference: Introduction

The following pages define the configuration items that you can use to configure a DataSource application (such as Liberator, Transformer or an Integration Adapter).

For an overview of how configuration works see Features and concepts of DataSource configuration.

To find out about the format of configuration items, see the DataSource Configuration Syntax Reference.

There’s a page (or sometimes more) for each area of configuration (peer connections, data services, logging, and so on), listing all the configuration items that are available for that area. Most configuration items can be used in both C-based and Java-based DataSource applications, including Liberator and Transformer.

Configuration file locations

If you are developing a DataSource application:

  • The application’s default configuration goes in: blade/DataSource/etc/datasource.conf

  • The application’s default overriding configuration goes in: blade/overrides/datasource-name/etc/datasource.conf

If you are deploying a kit to a Deployment Framework, override the application’s default DataSource settings in one of the Deployment Framework locations below:

  • Liberator: global_config/overrides/servers/Liberator/etc/…​

  • Transformer: global_config/overrides/servers/Transformer/etc/…​

  • Other DataSources: global_config/overrides/datasource/datasource.conf

For how to do this, see the How Can I…​ pages listed below under See also.

Mandatory items and default values

If a configuration item or an option within an item has a default value, the item/option is optional and if you don’t specify it, its default value will apply.

If the default is shown as [none], the item/option is mandatory (unless otherwise indicated) - you must specify it in your configuration. For example, the service-name and add-source-group options of the add-data-service item have no default, so if you define a data service, it must at least have a name and a single add-source-group:

   service-name MyDataService