Message Queue Service¶
Jitterbit Harmony Message Queue is a cloud-based, multi-tenant messaging queue service, where you can create and manage queues and messages through the Management Console Message Queues page and the Jitterbit MQ (Beta) connector.
A message is any data that is transferred between two systems or applications. When a message (sent through the Jitterbit MQ (Beta) connector) is received by an application (the Message Queue Service), the application can place it in a queue, which contains messages arranged in the order in which they need to be acted upon or processed.
The Message Queue service supports asynchronous processing, enabling you to manage your system workloads and resources with these components:
Message Queues management page
Use the Management Console Message Queues page to perform these actions:
Create, manage, and monitor message queues in the Message Queues tab.
Create and manage authentication tokens in the Authentication Tokens tab. Authentication tokens grant the Jitterbit MQ (Beta) connector access to message queues.
Enable or disable messaging for Harmony environments and set the message queue automatic refresh interval in the Settings tab.
Jitterbit MQ (Beta) connector
Use the Jitterbit MQ (Beta) connector to perform these actions:
Acknowledge messages in a message queue using the Acknowledge activity.
Retrieve all messages in a specific message queue using the Get activity.
Negatively acknowledge messages using the NACK activity.
Send messages to a message queue using the Send activity.
This diagram displays how a Jitterbit Message Queue message moves through the system architecture:
Data is retrieved from a source endpoint, such as by using a Cloud Studio connector. The retrieved data can then be transformed into a message to be consumed by the Jitterbit MQ (Beta) connector.
Using the Jitterbit MQ (Beta) Send or Send Bulk activity, the data is sent to the Jitterbit Message Queue service (which sends the messages to the specified message queue).
Messages can then be retrieved from a message queue using a Jitterbit MQ (Beta) Get or Get Bulk activity.
Data retrieved from a message can then be used as input to be consumed by a target endpoint, such as by using a Cloud Studio connector.
Once the data is consumed, the message can be either acknowledged (using the Acknowledge activity) or negatively acknowledged (using the NACK activity). If the message is not acknowledged or negatively acknowledged before the timeout of 30 minutes, the message will be available to be retrieved from the queue again by either a Get or Get Bulk activity.
If using a Private Agent that is behind a firewall within your network, you must allowlist the Message Queue Service.
The Message Queue Service is hosted in Jitterbit's cloud datastore and is accessed through the Jitterbit MQ (Beta) connector. Message processing can be scheduled to occur at designated times through operation schedules.
The Message Queue service has usage limits to ensure optimal performance and fair usage. These are the usage limits depending on the purchased tier, either Basic or Premium:
|Number of environments enabled for the Message Queue service||2 environments||No limit|
|Number of queues per environment||2 queues per environment||100 queues per environment|
|Number of messages per queue||25 messages||10,000 messages|
|Message length||100 MB||500 MB|
|Messages per month (across all queue types)||50,000 messages||Limited by number of message packs purchased|
These usage limits are contractual. It is encouraged that you monitor your message usage and consider upgrades or additional pack purchases to align with usage patterns.
For information on tier pricing, contact your Customer Success Manager (CSM).