SHARE YOUR IDEAS

Description:

Scheduling and triggering the execution of an externally implemented data extraction should be defined in APM much like with the built-in connectors

Solution:

Provide scheduling and last export information persistence for API connection definitions like for SAP/JDBC/Data Lake extractions.

Provide an interface definition that the extraction system (e.g. wM.io) must provide (ideally a REST service definition) containing at least the identifier for the last extraction interval (e.g. a timestamp)

Provide the possibility with the scheduler to define the endpoint and access security definitions for the implementation of the above mentioned service

Call the service on scheduler event.

Ideally the external service is only responsible for uploading data into source tables. The re-calcualtion could be triggered by APM as part of the automation as the recalculation may as well involve data from standard extractor definitions and should only be started if all data is uploaded.

Additionally this would massively reduce the complexity in the external integration tooling