A DataConnect application that runs on-premise but can be scheduled from the Integration Manager powered by Actian DataCloud and can be used to perform an integration between on-premise and cloud-based resources. Agents may be used for different purposes, such as Job Processor, Engine Facade, File Flinger, Message Publisher, or Stream Publisher to DataCloud.

Specifies which package should be executed and provides any needed system variables (see macros) and files to run the package. The configuration may also specify a schedule on which to run, or be run on demand. The configuration may inherit assets (Macros, Files, Package, and Entry Point) from a template, or it may override those assets.

Username/password used for login

The place where the execution of a Package begins. Every Package must define one or more entry points. The entry point must be a process.

Every time a configuration executes, that instance of the execution is a job. Each job is associated with runtime metrics and results, often found in the log.

DataConnect engine log related to a job.

Most packages are designed to require configuration values. These configuration values can be supplied as key-value pairs called Macros, specified at the global level, the Template level, or the configuration level. If the same Macro key is provided multiple places, the Configuration Macro overrides the Template Macro, which would override the Global Macro. Macros can be added individually or through a Macro file in either XML or JSON format.

The maps and processes created with DataConnect that will be executed once the configuration is run. This will be a DataConnect djar file.

Specifies what package should be executed and provides any needed system variables (see Macros) and files to run the package. The template cannot be executed or scheduled, but provides the basis for one or more Configurations that may inherit assets (Macros, Files, Package, and Entry Point) from the template.