The Jitterbit Harmony JMS Connector establishes access to JMS (Java Message Service) providers.
The JMS connector provides an interface for creating a JMS connection, the foundation used for generating instances of JMS activities. These activities, once configured, interact with JMS providers through the connection.
The JMS connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a JMS 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 JMS connection and its activities are referred to as a JMS endpoint:
Acknowledge: Sends a bulk acknowledgment of JMS messages and is intended to be used as a target in an operation.
Get: Retrieves all JMS messages available in a specific queue and is intended to be used as a source in an operation.
Consume (Beta): Consumes messages from a JMS queue and is intended to be used as a source in an operation.
Send: Sends messages to a JMS queue or topic and is intended to be used as a target in an operation.
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 JMS 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.
The JMS connector supports the Java Message Service 1.1 specification.
A Jitterbit Harmony Private Agent is required when using IBM MQ as the JMS provider. IBM MQ 9.2 is supported. Other versions of IBM MQ may also work but have not been tested by Jitterbit. For more information on selecting a JMS provider, see JMS connection.
If you experience issues with the JMS connector, these troubleshooting steps are recommended:
Ensure the JMS 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.
Check the operation logs for any information written during execution of the operation.
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.sdkjms" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.