The repositories configuration is used to configure the repositories on which the analysis is performed. It uses the structure below.


The friendly name of the repository, this is used source value in Xillio Insights. Example: if you need to analyse two instances of an repository, the repository names might look like synergyTest and synergyProduction.


The plugin name that is used to connect to the repository. Note that this is case sensitive. You can find a list of supported repository plugins


Defaults to etlFramework/plugins/. This can be changed if you want use project specific connector plugins (you should place them in the /project).


Optional field that you can use to point to an custom mapping robot using its path relative to the project. A custom mapping robot should reside in the /project folder and look like:

use Concurrency;

argument data = Concurrency.testInput({}, []);

var object = Concurrency.pop(data.input);

while(object != null){
    if(object.xillioType == "log"){
        Concurrency.push(object, data.output);

        var metadata = {};

        // extend robot to fill the metadata object

        object.udm.metadata = metadata;

        Concurrency.push(object, data.output);

    object = Concurrency.pop(data.input);


The options of the config object are specific per plugin. Use the list of supported repositories. for their configuration options.

    "repositoryName" : {
        "location" : "project/plugins/"
        "type" : "pluginName",
        "config": {
            // config values for Extract function of the plugin