Please give details of the problem

Skip to content

FileReader Adapter

The FileReader adapter is used to access and retrieve files from a local system in RunMyProcess DigitalSuite.


The following prerequisites must be fulfilled to install and run the FileReader adapter:

  • You must install the adapter on a local system in your environment. This can either be the system where you have installed the DigitalSuite EnterpriseConnect Agent, or a different one which is able to connect to the Agent's host.

  • You can install the adapter several times in your environment, for example, to retrieve files on different systems. The identifier of the adapter (protocol setting in the handler.config configuration file) must be unique for each of the installations.

  • The files to be retrieved in RunMyProcess DigitalSuite must be local files or directly accessible from the system where the adapter is installed.

Installing the Adapter

To install the adapter:

  1. Download the following ZIP file: unified-adapter-[version].zip

    [version] is the current version number

    The ZIP file contains executables, licences, configuration files, and reference files for several adapters.

  2. Extract the ZIP file to a local folder. The following path is recommended:


    [parent-folder] is a folder of your choice. If the EnterpriseConnect Agent is installed on the same machine, use its installation folder as the [parent-folder], for example, C:\ProgramFiles (x86)\dsec-agent.

  3. Copy the configuration files for the FileReader adapter, fileReader.config and handler.config, from the configFiles\fileReader.reference subfolder to the configFiles folder, for example:

    copy configFiles\fileReader.reference\*.config configFiles

    Overwrite existing files in the configFiles folder.

  4. If desired, delete obsolete files. Only the following folders and files are required in the fileReader folder to use the adapter:

    ├── configFiles
       ├── handler.config
       └── fileReader.config
    ├── lib
       └── unified-adapter-[version].jar
    └── log.properties

    In addition, we recommend you keep the following:

    • runAdapter.bat batch file for starting the adapter on Microsoft Windows
    • fileReader.reference subfolder in the configFiles folder for reference purposes

Configuring the Adapter

Configuration settings for the FileReader adapter are required in the following configuration files:

Edit the files with a plain text editor.


The handler.config file contains general configuration settings for connecting the adapter to the EnterpriseConnect Agent:

#Generic Protocol Configuration
protocol = fileReader
protocolClass = org.runmyprocess.sec2.FileReader
agentHost =
pingFrequency = 1000
adapterConnectionInterval = 1000
offlineLogsMaxSize = 100
maxNumberOfLogsInBatch = 100
clusterEnabled = false
clusterAgentsHttpAddressList = localhost:8071,localhost:8072,localhost:8073

The settings have the following meaning:

  • protocol: The identifier of the adapter. If you install the adapter several times in your environment, the identifier must be unique for each of the installations, for example, fileReader1 and fileReader2.
  • protocolClass: The adapter's Java class.
  • agentHost: The IP address and port of the EnterpriseConnect Agent.
  • pingFrequency: The frequency in milliseconds in which the adapter pings the EnterpriseConnect Agent.
  • adapterConnectionInterval: The frequency in milliseconds in which the adapter tries to connect to the EnterpriseConnect Agent.
  • offlineLogsMaxSize: The maximum number of log entries that the adapter collects locally and sends to the EnterpriseConnect Agent when it re-connects to it after it was disconnected.
  • maxNumberOfLogsInBatch: The maximum number of log entries the adapter sends to the EnterpriseConnect Agent at a time. A value of 0 means that the number of log entries sent at a time is unlimited.
  • clusterEnabled: true if the EnterpriseConnect Agent is configured and running as a cluster, false otherwise.
  • clusterAgentsHttpAddressList: The IP addresses and ports of the EnterpriseConnect Agent cluster, if clusterEnabled is set to true.


The fileReader.config file contains specific settings for the adapter:

#fileReader Configuration   

The setting has the following meaning:

  • basePath: The absolute path starting from which the files to be accessed by means of the adapter are stored. This path will be prepended to any file paths and names received from RunMyProcess DigitalSuite. For example: basePath=/projects/myproject/

Note: Make sure to use proper escape characters for navigating through folders on Microsoft Windows, for example: basePath=C:\\Users\\RMP\\Desktop\\

Starting the Adapter

The adapter needs to be running to be able to access local files.

Before you start the adapter, make sure that the DigitalSuite EnterpriseConnect Agent is running.

To start the adapter:

  1. Change to the fileReader installation folder.

  2. Execute the following command, depending on the operating system:

    • On Microsoft Windows: Execute the runAdapter.bat batch file.

    • On Linux: Execute the following command directly, or create and execute a corresponding shell script to do so:

      java -XX:+UseG1GC -XX:+ExitOnOutOfMemoryError -Djava.util.logging.config.file=./log.properties -cp lib/*: org.runmyprocess.sec2.AdapterHandler

Using the Adapter

If everything is configured and running correctly, you can place requests from RunMyProcess DigitalSuite to retrieve files from the local environment.

Request: POST on http://[agent-host]:[port]/, where [agent-host] and [port] are the IP address and port of the EnterpriseConnect Agent.

Content Type: application/json

Accept: application/json

Content (example):


You can find a sample request like the one above in the fileReader.reference\InputJSONExample.txt file in the fileReader installation folder.

Return Object:

The expected return is a JSON object that looks as follows:


file contains the return information, file.file is the file content in base64-encoding.