Spring Boot integrations poll Collibra Platform workflows rather than listen for incoming workflow requests. We are proposing how this mechanism can work and the requirements needed on both the Collibra Platform and the Spring Boot integration.
In summary, this is how the whole process works:
A generic User Task Creation Workflow is set up on the Collibra Platform. Whenever a Collibra Workflow needs to communicate with an integration, it should use this workflow to create a user task for the integration to pick up.
Create an Initialization Method inside the integration, which defines a callback function which is triggered when a User Task is found.
Collibra Workflow Utils methods within the Integration Library will use Collibra Core API calls to pick up the relevant user tasks created by the User Task Creation Workflow, call the callback function defined in the Initialization Method to start the integration process, and complete User Tasks when the integration process finishes.
To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.
Spring boot Integration demo for showing the Collibra Workflow Process.
- Eclipse IDE
- Spring Boot Framework
- Collibra Data Intelligence Cloud
- Collibra Data Intelligence On-Prem
- Java Runtime Environment 1.8
- Spring Boot Framework
- Spring Boot Integration Library
License and Usage Requirements
Browse discussions with customers who also use this app.
Collibra-hosted discussions will connect you to other customers who use this app.
The following terms shall apply to the extent you receive the source code to this offering.
Notwithstanding the terms of the Binary Code License Agreement under which this integration template is licensed, Collibra grants you, the Licensee, the right to access the source code to the integrated template in order to copy and modify said source code for Licensee’s internal use purposes and solely for the purpose of developing connections and/or integrations with Collibra products and services.
Solely with respect to this integration template, the term “Software,” as defined under the Binary Code License Agreement, shall include the source code version thereof. Except with respect to the foregoing, all remaining terms of the Binary Code License Agreement shall apply to the license of integration template hereunder.