Viewing Integration Manager Configurations
Use the Integration Manager for DataConnect Configuration Read-only Editor to browse, execute and inspect configurations within Integration Manager.
This Read-only Editor is only meant to provide details about integrations so that users can determine the integrations they wish to edit. A temporary configuration file is used to display details for each integration. Names for the temporary files have the prefix tmp_ and the file extension .config.
When a job configuration which resides in the platform product is executed from the Read-only Editor, it executes on the Integration Manager for Actian Data Platform or the Integration Manager server. The Read-only Editor shows the execution status as it is running on the platform server. When the execution completes, users can view the log file. The Log status for the execution is shown in the Read-only Editor Configuration Jobs area.
Once the integration of interest is identified, users import it into their workspace which enables editing. For more information, see Importing Integration Manager Integrations into a Workspace.
Prerequisites
• One or more package (.djar) files. For information about creating a package (.djar) file for a project, see Creating a Package.
• An Integration Manager connection to either a server hosting an Integration Manager installation, or to the Actian Data Platform. For more information, see Defining an Integration Manager Connection.
Note: The Integration Manager instance must be running.
• Integration Manager connections are configured in Preferences. For more information, see Setting Integration Manager Preferences.
The following image illustrates the Integration Manager Configuration Read-only Viewer: 
To view a job configuration using the Integration Manager Configuration Read-only Editor:
1. Navigate to the Integration Manager Explorer tab (to the right of the Repository Explorer tab).
2. Select the instance you wish to view from the Connections dropdown.
A list of Job Configurations for the instance are displayed.
Note: For information about creating a package (.djar) file for a project, see Creating a Package.
3. Double-click a package (.djar) to select it.
Details for the job configuration, as well as files and macros associated with the selected package are displayed in a new tab. The label for the new tab is the package (.djar) name prepended with tmp_, and has the file extension .config. For example, a package named sales2024.djar will have the tab name tmp_ sales2024.config.
Use the tmp_ file to inspect package details. The tmp_ prefix indicates that the job configuration resides in the Actian Data Platform, or other Integration Manager installation. The Job Configuration details reflect their current state in the connected Integration Manager or in the platform. The tmp_ files are deleted when the tab is closed.
To edit the integration, import the integration into your workspace. For more information, see Importing Integration Manager Integrations into a Workspace.
The following information is displayed in the Integration Manager Configuration viewer.
Job Configuration Details Lists details about the job configuration.
Field | Description |
|---|---|
Name | The name of the job configuration. |
Id | The unique ID for the job configuration. |
Base Template | Template the job configuration is associated with. If the job configuration does not have an association with a template, this field will be empty. |
Active | Active Indicates whether the job configuration is currently Active or Inactive. You can run the job configuration on the Integration Manager Platform only if it is set to Active (this option is in selected state). |
Run Location | Displays the .djar package that will be run by the job configuration. If multiple packages are available, they will appear in the drop-down (and a different package or configuration can be selected to execute after re-deployment). |
Package Name | Displays the .djar package or packages that were uploaded into the job configuration. If multiple packages are available, they will appear in the drop-down and you can select a different package to view its details. Note: For information about creating a package (.djar) file for a project, see Creating a Package. |
Entry Point | Specifies the entry point where the executed job will begin. The entry point must be a master Run Time Config (.rtc) file in your project. The (.rtc) file can be a master process.rtc or map.rtc file. |
Artifact Override | When this option is selected, the package process steps or map will be overridden by the artifacts added under Files. The artifact must have the same name as in the package. |
Job Timeout (Min) | Jobs run from this job configuration will time out if they do not finish within the time that is set in minutes. If the timeout is set to 0, the timeout will be ignored. |
Scheduling | Possible values are: • On Demand – Unscheduled; the job configuration must be run manually. • Scheduled – The job configuration is scheduled to execute. |
Log Level | Specifies the types of messages that will be included in the job’s log file. Possible settings include: • Inherit From Template • SEVERE – Logs errors that can cause the process execution to terminate. • WARNING – Logs messages about data truncation in a field, field name changes, loss of precision, or other issues • INFO – Logs messages such as “Execution initialization...,” “Execution successful,” whether the process execution was terminated, and so on. • DEBUG – All messages generated as a result of a TraceOn action and some other messages are logged at this level. In this case, the record number, first five fields of each record, and all the events are recorded. |
Owner | Displays the username of the owner (creator) of the job configuration. |
You can perform the following actions:
Actions | Description |
|---|---|
 | Click to open the Package Import Wizard. You can import the temporary job configuration (and all supporting artifacts within the .djar) into DataConnect for editing and debugging using the guided workflow of this wizard. See Importing Integration Manager Integrations into a Workspace. |
 | Click to execute the job configuration. |
 | Click to view execution details in the Integration Manager Log tab in the JobConfig panel. |
Configuration Files: Lists files associated with the select job configuration.
Fields | Description |
|---|---|
File | The artifact file name. |
Configuration Macros: Lists macros associated with the selected job configuration.
Fields | Description |
|---|---|
Name | The macro name. Click the template name to edit it. A text box is displayed. Type a new name and then press enter. |
Value | The macro value. Click the macro value to change it. A text box is displayed. Type a new value and then press enter. |
Description | The macro description. Click the macro description to edit it. A text box is displayed. Type a new description and then press enter. |
Secure | Indicates if the macro is encrypted. |
Configuration Jobs (Last 10): Lists execution results for the last ten executed job configurations, sorted by start date and time in descending order. Each time you Run the job configuration, a new entry appears at the top.
Note: Only jobs executed from DataConnect are listed.
Fields | Description |
|---|---|
Start (EDT) | The date and time the job configuration started running. |
Status | The execution results. Possible values are: Running - The job configuration is executing. Finished - The job configuration executed successfully. Failed - The job configuration was not successful. |
Duration | The amount of time, in minutes and seconds, for the job configuration to execute. |
Log | Contains a link to the job configuration log file. Click the Log icon to see execution details in the Integration Manager Log tab in the JobConfig panel. |
Job ID | A unique ID for the executed job configuration. |
Server | The name of the server where the job configuration was executed. |
Last modified date: 10/22/2024