Field | Description |
---|---|
Name | The configuration name. |
Id | The configuration Id. |
Base Template | Template the configuration is associated with. If the configuration does not have an association with a Template, this field will display “Not Set”. |
Active | 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 | 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 | 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 | 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 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 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 | 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 | 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 | Displays the username of the owner (creator) of the configuration. |
Actions | Description |
---|---|
Click this icon to open the Package Import Wizard. You can import the temporary configuration into DataConnect for editing and debugging using the guided workflow of this wizard. See Importing Configurations into a Workspace. |
Fields | Description |
---|---|
File | The artifact file name. |
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. |