Lineage edge processing
To perform lineage processing for sources not reachable from the Ataccama ONE cloud, edge processing must be set up near the data source location. During edge processing, the standalone scanner will act as a remote agent; therefore, it must be deployed at the edge.
A standalone lineage scanner must be installed at each edge. Therefore, before setting up edge processing, read the Standalone Lineage Scanner, which describes the installation process for the standalone scanner.
Registering the agent
The agent (the standalone scanner) must be registered and paired with the Ataccama ONE cloud service to establish a communication channel between the edge and the cloud service. To do that, execute the following command from the edge:
./bin/lineage-scanners edge register my-edge https://lss-<ataccama_one_app_url>/edges-api/registrations
A successful command line response should be as follows:
Edge registration successfully completed.
Edge instance name: my-edge
Edge instance id: 2622fc8d-02f0-41fa-a098-8788a7f1ca9c
Creating a scan plan on the edge
Adding [<edge instance name>] to the scan plan name in the Ataccama ONE UI will cause the scan to be executed on the corresponding edge from which the agent was registered.

Using AKV with edge processing
When referring to Azure Key Vault secrets in a scan plan, the AKV connection is established from the edge; therefore, the AKV must be configured on the edge using the command line interface. See configuring the Azure Key Vault in the standalone scanner.
There is a limitation of the SW: when AKV is used with edge processing, the scan plans are not validated correctly when saving them with "Validate & Save." Please ignore the error message and use the "Save" button instead. |
Troubleshooting
Error when registering the agent
In a case of the following error message, there is no working network connection between the edge and Ataccama ONE instance. Check the connectivity between between the edge and Ataccama ONE instance.
org.springframework.web.reactive.function.client.WebClientResponseException$Conflict: 409 Conflict from POST http://lss:8080/secrets-api/secrets
at org.springframework.web.reactive.function.client.WebClientResponseException.create(WebClientResponseException.java:327)
---
Was this page useful?