Jitterbit MQ (Beta) Connection¶

Introduction¶

A Jitterbit MQ (Beta) connection, created using the Jitterbit MQ (Beta) connector, establishes access to the Jitterbit Message Queue Service. Once a connection is configured, you can create instances of Jitterbit MQ (Beta) activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Note

This connector supports the Enable Re-authentication on Change organization policy. If enabled, a change to the Organization ID, Environment ID, or Jitterbit Region in this connection requires users to re-enter the Auth Token for the connection.

This connector is currently released as a beta version. To provide feedback on bugs and enhancements, contact your Customer Success Manager (CSM).

Create or Edit a Jitterbit MQ (Beta) Connection¶

A new Jitterbit MQ (Beta) connection is created using the Jitterbit MQ (Beta) connector from one of these locations:

The design component palette's Connections tab (see Design Component Palette).
The Global Connections page (see Create a Global Connection in Global Connections).

An existing Jitterbit MQ (Beta) connection can be edited from these locations:

The design component palette's Connections tab (see Design Component Palette).
The project pane's Components tab (see Component Actions Menu in Project Pane Components Tab).
The Global Connections page (see Edit a Global Connection in Global Connections).

Configure a Jitterbit MQ (Beta) Connection¶

Each user interface element of the Jitterbit MQ (Beta) connection configuration screen is described below.

Jitterbit MQ (Beta) connection configuration

Tip

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.

Connection Name: Enter a name to use to identify the connection. The name must be unique for each Jitterbit MQ (Beta) connection and must not contain forward slashes / or colons :. This name is also used to identify the Jitterbit MQ (Beta) endpoint, which refers to both a specific connection and its activities.
Organization ID: Enter the Harmony organization ID for the organization containing the message queue.
Environment ID: Enter the Harmony environment ID for the environment containing the message queue. The environment ID is found by hovering over the environment name on the Environments page.
Auth Token: Enter an authentication token associated with the environment. The authentication token is generated in the Message Queues page within the Authentication Tokens tab.
Jitterbit Region: Select the Jitterbit region the organization belongs to, either APAC, EMEA, or NA.
Optional Settings: Click to expand additional optional settings:
- Connection Request Timeout in Seconds: Enter the time (in seconds) that the connection is to remain established with the Message Queue Service after servicing a request. The default is 10 seconds and the maximum value allowed is 180 seconds. Changing this value is not recommended.
- Response Timeout in Seconds: Enter the time (in seconds) to wait for a response from the Message Queue Service. The default is 10 seconds and the maximum value allowed is 300 seconds.
- Connection Timeout in Seconds: Enter the time (in seconds) to wait until a new connection is fully established. The default is 10 seconds and the maximum value allowed is 300 seconds.
Test: Click to verify the connection using the provided configuration.
Save Changes: Click to save and close the connection configuration.
Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.
Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component Dependencies, Deletion, and Removal). A message asks you to confirm that you want to delete the connection.

Next Steps¶

After a Jitterbit MQ (Beta) connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions Menus in Connector Basics.

These activity types are available:

Get Bulk: Retrieves a batch of messages available in a specific Jitterbit message queue and is intended to be used as a source in an operation.
Acknowledge: Acknowledges messages in a Jitterbit message queue and is intended to be used as a target in an operation.
Send Bulk: Sends a batch of messages to a Jitterbit message queue and is intended to be used as a target in an operation.
Get: Retrieves a single message available in a specific Jitterbit message queue and is intended to be used as a source in an operation.
NACK: Negatively acknowledges messages (using the ackId) and is intended to be used as a target in an operation.
Get Queue Details: Retrieves queue details for a specific Jitterbit message queue and is intended to be used as a source in an operation.
Send: Sends a single message to a Jitterbit message queue and is intended to be used as a target in an operation.