Editing Configurations
This feature enables editing of Job Configurations and all files that are associated with it. The configuration details, files, and configuration macros can be edited by opening the .jobconfig file.
To enable editing, you must import the job configuration file into DataConnect Project Explorer (see Importing Configurations into a Workspace). The editor allows editing of only some fields. After editing, you can redeploy the configurations or packages (djars) back to Integration Manager (see Redeploying to Integration Manager).
The following information is displayed in the Job Configuration editor:
Job Configuration Details:
Field | Editable | Description |
|---|---|---|
Name | No | The configuration name. |
Id | No | The configuration Id. |
Base Template | No | Template the configuration is associated with. If the configuration does not have an association with a Template, this field will display “Not Set”. |
Active | Yes | Indicates whether the configuration is currently Active or Inactive. You can run the configuration only if it is set to Active (this option is in selected state). |
Run Location | No | This property specifies which engine to use when executing the associated configuration. Default indicates that one of the cloud-based engines provided by Actian will be used. |
Package Name | Yes | Displays the djar package or packages that were uploaded into the configuration. If multiple packages are available, they will appear in the drop-down and you can select a different package to view its details. |
Entry Point | Yes | 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 | Yes | When this option is selected, the package process steps will be overridden by the artifacts added under Files. The artifact must have the same name as in the package. |
Job Timeout (Min) | Yes | Jobs run from this 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 | No | This property displays the schedule associated with the configuration. Possible values are: • On Demand – Unscheduled; the configuration must be run manually. • Interval – Scheduled to run every x hours and x minutes. • Daily – Scheduled to run every x days at a specified time. • Weekly – Scheduled to run every week at a specified time on a specific day. • Monthly – Scheduled to run every month on a specific day every x months at a specified time. • Custom – Scheduled to run as per the specified schedule frequency. • Custom CRON Expression – Scheduled by a Quartz CRON expression, which you specify. A quick Cron expression tutorial provided by Quartz is here. |
Log Level | Yes | 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 if Break after first error is set • 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 | No | Displays the username of the owner (creator) of the configuration. |
You can perform the following actions:
Actions | Description |
|---|---|
 | Click this icon to open the Deployment Wizard. You can repackage and deploy or redeploy to Integration Manager using the guided workflow of this wizard. Any changes you made to the djar files, macros, or the configuration will be uploaded to Integration Manager. See Redeploying to Integration Manager. |
Configuration Files: Displayed here is a list of artifact files that are associated with the job configuration. You can perform the following actions:
Actions | Description |
|---|---|
 | Click this icon to open the windows browse dialog. Browse and select an artifact file to add it. |
 | Select one or more files and click this icon to delete the selected files. |
 | Allows you to import djar file into DataConnect for editing and debugging. |
Configuration Macros: Displayed here is a list of job configuration macros that were imported into your workspace’s active macro definition file. A new macroset is created for the job configuration that you selected to import. For more information on macros, see Managing Macro Sets and Macros.
The following information is displayed:
Fields | Editable | Description |
|---|---|---|
Name | Yes | The macro name. Click the template name to edit it. A text box is displayed. Type a new name and then press enter. |
Value | Yes | The macro value. Click the macro value to change it. A text box is displayed. Type a new value and then press enter. |
Description | Yes | The macro description. Click the macro description to edit it. A text box is displayed. Type a new description and then press enter. |
Secure | No | Indicates if the macro is encrypted. |
You can perform the following actions:
Actions | Description |
|---|---|
 | Click this icon to add a macro. The default Name is “Macro n” where “n” is a number. You can change the default Name. Click the blank space under Value and Description fields and a text box appears. Type the required values and press enter. |
 | Select a macro and click this icon to delete it. |
 | Allows you to merge your local macro changes like edits or additions of new macros into the current DataConnect macro definition file (under Options > Manage Macros). |
Last modified date: 07/26/2024