Manage the integration batch poller

The Integration Batch Poller polls the integration batches submitted to the platform, and starts the integration jobs on the execution engine. The polling action is performed on a schedule configured in the batch poller.

Stop and start the integration batch poller

To stop and start the integration batch poller:

  1. In the Management view, expand the Job Executions node and double-click the Integration Batch Poller node. The Integration Batch Poller editor opens.

  2. Use the stop Stop this component and start Start this component buttons in the editor’s toolbar to stop and start the integration batch poller.

Stopping the batch poller does not kill running jobs, and does not prevent new batches to be submitted. When this component is stopped, the submitted batches are simply not taken into account and no jobs is queued on the execution engine until the batch poller is restarted.

Configure the integration batch poller

The integration batch poller configuration determines the frequency at which submitted batches are picked up for processing.

To configure the integration batch poller:

  1. In the Management view, expand the Job Executions node and double-click the Integration Batch Poller node.

  2. In the Integration Batch Poller editor, choose in the Configuration section the polling frequency:

    • Weekly at a given day and time.

    • Daily at a given time.

    • Hourly at a given time.

    • Every n second.

    • With a Cron expression.

  3. Press Control+S (or Command+S on macOS) to save the configuration.

It is not necessary to restart the integration batch poller to take into account the configuration changes.

In the Advanced section, set optionally the following logging parameters:

  • Job Log Level: Select the logging level that you want for the jobs:

    • No Logging disables all logging. Jobs and tasks are no longer traced in the job log. Jobs restart is not possible. This level is not recommended.

    • No Tasks only logs job information, and not the task details. This mode supports job restart.

    • Exclude Skipped Tasks (default) logs job information and task details, except for the tasks that are skipped.

    • Include All Tasks logs job information and all task details.

  • Execution Monitor Log Level: Logging level [1…3] for the execution console for all the queues.

  • Enable Conditional Execution: A task may be executed or skipped depending on a condition set on the task. For example, a task may be skipped depending on parameters passed to the job. Disabling this option prevents conditional executions and forces the engine to process all the tasks.

Deployment repositories are created with a Job Log Level value set to No Task. Other repositories are created with no configured value, and use the Exclude Skipped Tasks default value.