Skip to content

Parameters Groups

Parameters Groups

Parameter Groups In ADIB, parameters define how jobs and steps operate. They configure the source and destination of data, the way data is processed, and when and where tasks are executed. 1. Job Parameters A job is a collection of steps executed together. Job parameters control scheduling, execution, and dependencies.

Parameter Description
Name Unique name for the job.
Description Optional text describing the job.
Active Whether the job is enabled or disabled.
Instances The environment where the job will be executed.
Position / Order Defines the job’s execution sequence relative to other jobs.
Follow-up Job Optional next job to trigger automatically after completion.
Execution Time When the job should run (using cron format). Example: 0 3 - - - 1-5 runs at 3:00 AM Monday to Friday.

2. Step Parameters A step is a single integration task within a job. Step parameters define data sources, destinations, and processing rules.

Parameter Description
Step Name & Description Name and optional description of the step.
Active Enable or disable the step.
Source Module (srcModule) Defines where data comes from (e.g., MySQL, Excel, XML).
Destination Module (destModule) Defines where data is sent (e.g., Excel, Contentserv PIM).
Web Service Module (wsModule) Optional; used if the step involves a web service.
Pre-process / Post-process Optional actions before or after the step (e.g., sending emails, retrieving files).
Step Mode (stepModus) How data is transferred: fullTransfer (all data), deltaWholeLine (only changed data), deltaDroppedLine (deleted data).
Dry Run Tests connections and available fields without transferring data.
Flex Mapping List Optional; used for complex data transformations.
Step Position Mode Defines whether all fields or only selected fields are transferred.
Connect Step ID Links this step to a follow-up step.
Web Service Template (ws_templateId) Template used when working with web service modules.
Elastic / Portal Template Template used for ADIB portal steps.

Note: For module-specific parameters (e.g., database connection details for MySQL, file paths for Excel, or template IDs for web services), please refer to the parameters section of the module documentation. These parameters must be configured for the source and destination modules to function correctly.