Jitterbit MQ Get Activity¶
A Jitterbit MQ Get activity, using its Jitterbit MQ connection, retrieves a single message available in a specific Jitterbit message queue and is intended to be used as a source to provide data in an operation.
Create a Jitterbit MQ Get Activity¶
An instance of a Jitterbit MQ Get activity is created from a Jitterbit MQ connection using its Get 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 Get 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 Get Activity¶
Follow these steps to configure a Jitterbit MQ Get activity:
Step 1: Enter a Name and Specify the Queue
Provide a name for the activity and specify the queue.
Step 2: Review the Data Schemas
Any request or response schemas are displayed.
Step 1: Enter a Name and Specify the Queue¶
In this step, provide a name for the activity and specify the queue. Each user interface element of this step is described below.
Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket
[ into the field or by clicking the variable icon to display a list of the existing variables to choose from.
Name: Enter a name to identify the activity. The name must be unique for each Jitterbit MQ Get activity and must not contain forward slashes
Queue: Provide the name of the queue containing the messages to be retrieved. The queue must be in the environment specified in the Jitterbit MQ connection.
Auto Acknowledge: Select to enable automatic acknowledgement of retrieved messages. This option generates a response for each acknowledged message and may cause longer processing times. If Auto Acknowledge is left unselected, explicit acknowledgements (using the Acknowledge activity) are limited to 50 per environment and 500 per organization.
If Auto Acknowledge is left unselected, messages retrieved using the Get activity must be acknowledged (by the Acknowledge activity) or negatively acknowledged (by the NACK activity) before a timeout of 30 minutes. Once the 30-minute timeout has expired, messages will continue to be retrieved by a Get or Get Bulk activity.
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 response data schema consists of these nodes and fields:
Response Schema Node/Field Description
The number of messages retrieved, either
The message body
The queue containing the message
The acknowledgement ID to be used in the Acknowledge activity
Node containing the properties of the message
Node containing the envelope data
Integer of the delivery tag to attach to the message (used in the Acknowledge activity)
The identifier of the application that produced the message
Content encoding for the message
The message content type, such a
The ID of the correlated message (which request the message is replying to)
Integer indicating whether the retrieved message is persisted to disk (
2) or non-persistent (
The expiration time after which the message will be deleted (the TTL period in milliseconds as determined in the message queue settings)
The message ID (if applications need to identify messages, it is recommended that they use this attribute instead of putting it into the message payload)
Integer value ranging from
9indicating the priority of the message (
9being the lowest priority)
String containing the message type, for example, the type of event or command this message represents.
The time of the request
Node containing any message headers
Node containing each message header
The name of the message header
The value of the message header
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 Get 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 Get activities can be used as a source with these operation patterns:
- Transformation Pattern
- Two-target Archive Pattern (as the first source only)
- Two-target HTTP Archive Pattern (as the first source only)
To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.