Skip to Content

Jitterbit MQ (Beta) Connector

Summary

The Jitterbit Harmony Jitterbit MQ (Beta) Connector establishes access to the Jitterbit Message Queue Service.

Note

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

The Jitterbit MQ (Beta) connector provides an interface for creating a Jitterbit MQ (Beta) connection, the foundation used for generating instances of Jitterbit MQ (Beta) activities. These activities, once configured, interact with Jitterbit Message Queue Service through the connection.

The Jitterbit MQ (Beta) connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview

This connector is used to first configure a Jitterbit MQ (Beta) connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Jitterbit MQ (Beta) connection and its activities are referred to as a Jitterbit MQ (Beta) endpoint:

Jitterbit MQ (Beta) activity types

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

  • Send: Sends a single message to a Jitterbit message queue and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and Supported API Versions

The Jitterbit MQ (Beta) connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

Note

If using a Private Agent that is behind a firewall within your network, you must allowlist the Message Queue Service.

Troubleshooting

If you experience issues with the Jitterbit MQ (Beta) connector, these troubleshooting steps are recommended:

  1. Ensure the Jitterbit MQ (Beta) connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can check the agent logs for more information.