ConfigurationGuide - GeneralElectric/TrueConnect-Link GitHub Wiki
The behavior of TrueConnect-Link is driven by its' configuration, this tells it what files to look for,where and how often to look. It also defines what metadata is to added with the upload to TrueConnect and how to connect to it.
A configuration file is associated with a clientId and its connection to a TrueConnect instance. So if you have multiple ClientIDs or you connect to multiple TrueConnect Instances, then you will need multiple configuration files.
The full json schema describing the configuration format is available here
The configuration format does allow a single client to search multiple location for multiple tenants. This is done by defining multiple "Targets" in the configuration.
The top level of the configuration tells TrueConnect-Link how to connect to TureConnect and includes:
- runasservice: this is normally overridden by runnecint TrueConnect-Link with either the Auto or Start command
- clientid: used as the identity for authentication into TrueConnect
- secret: used as the password for authentication into TrueConnect
- tokenurl: The URI of the UAA service, that provides authentication token
- endpoint: The URI of the TrueConnect service to store the files on
- targets: A list of things to search for
Targets describe the location and pattern of files you wan to upload to true connect, whilst you could point the location to the root of your file systems and use a complex regular expression in the match parameter to look for various file patterns and folders but its simpler if you split them up, in fact the format mandates that you define a new target for each data type and data format or tenant you want to upload.