- 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 (PDF).
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.
The applicability of a configuration item is indicated like this:
C-based DataSource applications
Java-based DataSource applications
In this example, the blue tick (check mark) means that the item can be used to configure C-based DataSource applications (built using the C DataSource API), whereas the grey cross means the item can't be used to configure Java-based DataSource applications (built using the Caplin Integration Suite).
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-data-service service-name MyDataService add-source-group ... add-source-group end-data-service
Links to the DataSource configuration reference pages
- Field definition format
- Run-time environment
- DataSource peers
- Data services
- Name mapping
- Java (JVM)
- Secure Sockets Layer (SSL)
- DataSource monitoring
- Latency chains