Link Search Menu Expand Document

Set-up Agent

Blindata Agent must be able to communicate with all external systems for which you want to automate the activities of metadata collection and data quality monitoring as well as with the main Blindata instance. Therefore, it will be necessary to set-up the machine where the Agent is installed with the appropriate network configurations.

Configurations

The installation of the Blindata Agent must be perfected with the following configurations:

  1. Datasource URL: the connection string to the database
  2. Datasource username:the username of the user that can interacat with the database for the creation of schemas and tables for creation, modification and deletion of data. Make sure that the user has the right permissions
  3. Datasource password: the password of the user with which the agent will interact with the database
  4. Remote base URL: Used in the CORS configuration, it indicates the URL from which requests are accepted. If not specified, the remote base URL is used as default. It is the url accessed from the browser interface, for example https://blindata.mydomain.com.
  5. Encryption secret: String of 32 characters that will be used by the encryption algorithm of the credentials of the connections stores by the agent

The Blindata Agent agent connection is http, see related pages below to enable https connection

Start Agent

The agent is started with the following command:

java -Dloader.path=path/to/blindata-agent/lib/ -jar blindata-agent-"VERSION".jar
--spring.datasource.url=jdbc:postgresql://"host":"port"/postgres
--spring.datasource.username=postgresql
--spring.datasource.password=password
--blindata.agent.remote.base-url=https://blindata.mydomain.com
--blindata.agent.remote.allowed-origin=https://allowed-origin.mydomain.com
--blindata.agent.encryption.secret=#encryption key

The -Dloader.path option must be specified only if the agent must use custom drivers to connect to external systems. If there is no need to use custom drivers, the option can be omitted.

Alternatively you can modify the file application.properties located in the same folder as the jar file with the previous commands.

Related pages: