Skip to Content

Jitterbit MQ (Beta) Send Activity

Introduction

A Jitterbit MQ (Beta) Send activity, using its Jitterbit MQ (Beta) connection, sends messages to a Jitterbit message queue and is intended to be used as a target to consume data in an operation.

Note

This connector is currently released as a beta version and is available only to a limited set of users. To participate in the beta program or provide feedback on bugs and enhancements, contact your Customer Success Manager (CSM).

Creating a Jitterbit MQ (Beta) Send Activity

An instance of a Jitterbit MQ (Beta) Send activity is created from a Jitterbit MQ (Beta) connection using its Send 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 (Beta) Send activity can be edited from these locations:

Configuring a Jitterbit MQ (Beta) Send Activity

Follow these steps to configure a Jitterbit MQ (Beta) Send activity:

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.

Jitterbit MQ (Beta) Send Activity Configuration Step 1

Tip

Fields with a variable icon 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 (Beta) Send activity and must not contain forward slashes / or colons :.

  • Queue: Provide the name of the queue to send messages to. The queue must be in the environment specified in the Jitterbit MQ (Beta) connection.

  • 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.

Jitterbit MQ (Beta) Send Activity Configuration Step 2

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    Note

    Data supplied in a transformation takes precedence over the activity configuration.

    The request and response data schemas consist of these nodes and fields:

    Request Schema Node/Field Description
    messageBody The message body
    queue The queue containing the message
    exchange Not functional
    routingKey Not functional
    mandatory Set to true to return the message if it cannot be placed in a queue, set to false to discard the message if it cannot be placed in a queue
    immediate Set to true to deliver the message immediately, set to false to consume the message at a later time
    properties Node containing the properties of the message
    appId The identifier of the application that produced the message
    contentEncoding Content encoding for the message
    contentType The message content type, such a application/json
    correlationId The ID of the correlated message (which request the message is replying to)
    deliveryMode Integer indicating whether the retrieved message is persisted to disk (2) or non-persistent (1)
    expiration The expiration time after which the message will be deleted (the TTL period in milliseconds as determined in the message queue settings)
    messageId 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)
    priority Integer value ranging from 0 through 9 indicating the priority of the message
    type String containing the message type, for example, the type of event or command this message represents.
    timestamp The time of the request
    envelope Node containing the envelope data
    deliveryTag Integer of the delivery tag to attach to the message (used in the Acknowledge activity)
    exchange Not functional
    isRedeliver Is redeliver
  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the Jitterbit MQ (Beta) 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.

  • 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.

Next Steps

After configuring a Jitterbit MQ (Beta) Send 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.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity Actions Menu in Connector Basics.

Jitterbit MQ (Beta) Send activities can be used as a target with these operation patterns:

A typical use case is to use a Jitterbit MQ (Beta) Send activity in the Two-transformation Pattern. In this example, the first transformation (Send Request) creates a request structure that is passed to the Jitterbit MQ (Beta) Send activity. The second transformation (Send Response) receives the response structure, which is then written to a variable by a Variable Write activity (Write Send Response) and a message is then logged by the Write to Operation Log script:

Jitterbit MQ (Beta) Send operation

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.