Jitterbit MQ Acknowledge Activity¶
A Jitterbit MQ Acknowledge activity, using its Jitterbit MQ connection, acknowledges messages (using an
ackId) in a Jitterbit message queue and is intended to be used as a target to consume data in an operation.
Create a Jitterbit MQ Acknowledge Activity¶
An instance of a Jitterbit MQ Acknowledge activity is created from a Jitterbit MQ connection using its Acknowledge activity type.
To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an Activity Instance in Component Reuse.
An existing Jitterbit MQ Acknowledge activity can be edited from these locations:
- The design canvas (see Component Actions Menu in Design Canvas).
- The project pane's Components tab (see Component Actions Menu in Project Pane Components Tab).
Configure a Jitterbit MQ Acknowledge Activity¶
Follow these steps to configure a Jitterbit MQ Acknowledge activity:
Step 1: Enter a Name
Provide a name for the activity.
Step 2: Review the Data Schemas
Any request or response schemas are displayed.
Step 1: Enter a Name¶
In this step, provide a name for the activity. Each user interface element of this step is described below.
Name: Enter a name to identify the activity. The name must be unique for each Jitterbit MQ Acknowledge activity and must not contain forward slashes
Ack Multiple Messages: Select to acknowledge multiple messages. This option is overridden by data provided in the
multiplefield in the activity's request schema.
Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.
Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.
Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.
Step 2: Review the Data Schemas¶
Any request or response schemas are displayed. Each user interface element of this step is described below.
Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.
The request and response data schemas consist of these nodes and fields:
Request Schema Node/Field Description
String containing the acknowledgement ID (obtained from a Get or Get Bulk activity); this field is used only for the acknowledgement of a single message
Integer of the delivery tag (configured as the
deliveryTagin a Send or Send Bulk activity); for example, if you are acknowledging multiple messages and this field is set to
3, all messages with delivery tags set to
trueif multiple messages are to be acknowledged, set to
falseif only a single message is to be acknowledged
String containing any additional properties Response Schema Node/Field Description
Boolean representing the success (
true) or failure (
false) of the acknowledgement
Node containing any errors
HTTP response status code returned
String containing any error messages
String containing any additional properties
Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Jitterbit MQ endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.
Back: Click to temporarily store the configuration for this step and return to the previous step.
Finished: Click to save the configuration for all steps and close the activity configuration.
After configuring a Jitterbit MQ Acknowledge activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.
Jitterbit MQ Acknowledge activities can be used as a target with these operation patterns:
To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.