Usually, a message is run in a recurring batch process. This topic gives some background information on how the batch process is managed. The applied batch process depends on the the performance settings of the message:

• Sequential
• Parallel

Note: The information in this topic only applies if the 'Split message run' feature is enabled in the Connectivity studio parameters.

Sequential

If the batch processing type is Sequential, batch tasks are processed in the defined sequence (files) or in the creation sequence (paging).

When the message is run, a batch job is created with these tasks:

Batch task	Description
Initialize the data for the message [message name]	Runs the pre-actions of the connector.
Run the message [message name]	Runs the message. Only one 'Run the message' batch task is created. All files are added to this batch task and run sequentially.
Finalize of message [message name]	Runs the post-actions of the connector.

Note: These batch task are shown only when the batch job status is 'Executing'. If the batch job is ended, only the 'Run the message [message name]' batch task is shown.

Parallel

If the batch processing type is Parallel, batch tasks are split over several threads (batch tasks) to run in parallel. Parallel processing improves the performance of message processing.

The number of batch tasks that is created for a batch job is defined by the Threads number (Message page header, Performance section).
If the Threads number is set to:

• 0, for each file to be processed a separate batch task is added to the batch job. Disadvantage: The more files must be processed, the more batch tasks are created. This can 'flood' the batch system with batch tasks being run at the same time.
• Any other number, the files to be processed are spread over the defined number of batch tasks. Example: Threads number is 5, number of files is 50. Five batch tasks are created. these batch tasks are run in parallel. Each batch task processes 10 files sequentially.

When the message is run, a batch job is created with these tasks:

Batch task	Description
Initialize the data for the message [message name]	Runs the pre-actions of the connector.
Prepare and create separate runs for [message name]	Creates 'Run the message' batch task, considering the Threads number as defined on the message header.
Run the message [message name]	Runs the message. Several 'Run the message' batch task can be created. Files that are added to one batch task, are run sequentially.
Finalize of message [message name]	Runs the post-actions of the connector.

Note: These batch task are shown only if the batch job status is 'Executing'. When the batch job is ended, only the 'Run the message [message name]' batch task is shown.

See also

• Improve integration performance