Skip to Content

Jitterbit MQ connector for Jitterbit Integration Studio

Summary

The Jitterbit MQ connector establishes access to the Jitterbit message queue service.

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

The Jitterbit MQ connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a Jitterbit MQ 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 connection and its activities are referred to as a Jitterbit MQ endpoint:

Jitterbit MQ 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.

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

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 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 the number of messages exceeds the user-defined message limit for an individual message queue, this runtime error will be returned:

"statuscode":500,"Error":"Error sending message."

To resolve, you may need to acknowledge messages in the queue, or you can adjust the message limit. The user-defined message limit is set on the Management Console Message queues page in the Message queues tab. Adjust the value in the Message Limit field, available under a queue's Advanced Options.

If you experience other issues with the connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  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 enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.jbmq" level="DEBUG"/>

  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.