This section contains details about running extractions automatically and manually in Xtract Universal Designer. Examples on how to call extractions:
Running an Extraction #
Extractions are triggered by an HTTP request and executed on the Xtract Universal server.
Depending on the destination, the execution of an extraction can be triggered either interactively or unattended.
Extractions are typically triggered interactively when a user requires new or updated data from SAP, and no additional data storage system (like a data warehouse) is present.
In these scenarios, execution of an extraction is typically triggered by one of Xtract Universal’s plugins:
Or directly by the target environment:
When an additional data storage system (database, cloud storage, flat files) is present, extractions are typically triggered as part of an ELT-process (Extract, Load, Transform), which is run unattended at regular intervals by a scheduler or other orchestration software. In these scenarios, execution of an extractions is typically triggered by running the XU command line tool from the orchestration software.
For advanced scenarios or environments that do not support command line programs, the HTTP Webservices can be used for triggering and monitoring executions.
Note: Xtract Universal does not have its own scheduler. You can use third party schedulers.
Run parallel Extractions #
The amount of possible parallel extractions depends on the hardware resources of the Windows server.
Every triggered extraction is executed in a separate process of the operating system.
Reliability and throughput of the network connection, available RAM and disk throughput (for logging and caching) are all crucial factors for the parallelization.
Other factors are the performance of the SAP source system the destination.
Note: Xtract Universal scales corresponding to the available hardware resources of the runtime environment.