Skillset Required

Understand the settings held in the EFTLink configuration files that controls EFTLink, and core behavior. System implementers must know how to add, modify and validate configuration settings using an appropriate text editor.

Configuration settings may be stored in either Java properties files or JSON files. The syntax rules depend on the file format in use:

Java Properties Files

When configuration is stored in a Java properties file:

  • Properties names are case sensitive.
  • Properties cannot contain spaces.
  • Each property must be defined on a separate line using the format property = value.
  • Spaces around the equals sign (=) are permitted
  • Boolean values are not case-sensitive (True and true are equivalent).
  • Lines prefixed with # are comments.

JSON Files

When configuration is stored in a JSON file:

  • Property names and string values must be enclosed in double quotation marks (").
  • Properties are defined as key/value pairs separated by a colon (:).
  • Opening and closing braces ({}) and brackets ([]) must be correctly balanced.
  • JSON is case-sensitive.
  • Standard JSON does not support comments. Where explanatory text is required, comment-style entries may be added using a property such as " _comment": "<comment>" if supported by the EFTLink configuration schema.