This topic describes how to use Integration Manager for DataConnect to manage and edit integrations, and the configurations that execute them. The integrations and configurations can reside on-premise or in the cloud. Users can also debug, repackage and redeploy integrations. This ability to manage, edit and redeploy from within Integration Manager greatly simplifies maintaining or extending existing integrations and configurations.

There are two Integration Manager products, Integration Manager for DataConnect (for use on-premise), and Integration Manager for Actian Data Platform (for use in the cloud). Integrations can be created and deployed using either Integration Manager product. For information about using Integration Manager for Actian Data Platform, see Actian Data Platform (formerly Avalanche) help.

For information about deploying a package from the command line of the engine, see Using Runtime Engine.

Users create connections to the servers where their integrations reside. For example, users might have a connection to the Platform Integration Manager server, another connection to their local Integration Manager, and another to a virtual machine. Users can then select a connection to browse, execute and inspect integrations in the Integration Manager for DataConnect Read-only Viewer.

The Read-only Viewer presents the integration details needed to determine which integration users want to edit. Integrations can also be executed in the Read-only Viewer. Once a particular integration is identified, users can import it into the on-premise product workspace for editing. Integrations cannot be edited in the Read-only Viewer (they must be imported first).

Importing the integration enables the Integration Manager for DataConnect Editor, which allows users to edit and debug integration artifacts (and job configurations). Integrations cannot be executed in the Editor. When finished editing, users can repackage and redeploy the integration - back to the platform product, for example. If users subsequently edit the redeployed integration in the platform product, the edits are not updated in the Integration Manager for DataConnect (the integration must be reimported into the DataConnect product).

Using Integration Manager for DataConnect involves working with various types of files, such as job configurations, integrations, packages and temporary (tmp_*.config) files. A package is a compressed, portable (.djar) file which contains all the artifacts in a project (for example, maps and processes, including all referenced, supporting artifacts). An integration is a configuration that references a .djar file (which might or might not have a schedule for execution). A job configuration specifies when and how to execute the artifacts. Temporary (tmp_*.config) files are used in the Read-only Viewer which enable users to inspect and execute integrations in order to identify the integration they want to edit.

This topic describes a typical high-level Integration Manager for DataConnect workflow.