Red Hat Camel K is deprecated
Red Hat Camel K is deprecated and the End of Life date for this product is June 30, 2025. For help migrating to the current go-to solution, Red Hat build of Apache Camel, see the Migration Guide.Chapter 39. JMS - IBM MQ Kamelet Sink
A Kamelet that can produce events to an IBM MQ message queue using JMS.
39.1. Configuration Options
The following table summarizes the configuration options available for the jms-ibm-mq-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| channel * | IBM MQ Channel | Name of the IBM MQ Channel | string | ||
| destinationName * | Destination Name | The destination name | string | ||
| password * | Password | Password to authenticate to IBM MQ server | string | ||
| queueManager * | IBM MQ Queue Manager | Name of the IBM MQ Queue Manager | string | ||
| serverName * | IBM MQ Server name | IBM MQ Server name or address | string | ||
| serverPort * | IBM MQ Server Port | IBM MQ Server port | integer |
| |
| username * | Username | Username to authenticate to IBM MQ server | string | ||
| clientId | IBM MQ Client ID | Name of the IBM MQ Client ID | string | ||
| destinationType | Destination Type | The JMS destination type (queue or topic) | string |
|
Fields marked with an asterisk (*) are mandatory.
39.2. Dependencies
At runtime, the jms-ibm-mq-sink Kamelet relies upon the presence of the following dependencies:
- camel:jms
- camel:kamelet
- mvn:com.ibm.mq:com.ibm.mq.allclient:9.2.5.0
39.3. Usage
This section describes how you can use the jms-ibm-mq-sink.
39.3.1. Knative Sink
You can use the jms-ibm-mq-sink Kamelet as a Knative sink by binding it to a Knative object.
jms-ibm-mq-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: jms-ibm-mq-sink-binding
spec:
source:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
properties:
serverName: "10.103.41.245"
serverPort: "1414"
destinationType: "queue"
destinationName: "DEV.QUEUE.1"
queueManager: QM1
channel: DEV.APP.SVRCONN
username: app
password: passw0rd
39.3.1.1. Prerequisite
Make sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.
39.3.1.2. Procedure for using the cluster CLI
-
Save the
jms-ibm-mq-sink-binding.yamlfile to your local drive, and then edit it as needed for your configuration. Run the sink by using the following command:
oc apply -f jms-ibm-mq-sink-binding.yaml
39.3.1.3. Procedure for using the Kamel CLI
Configure and run the sink by using the following command:
kamel bind --name jms-ibm-mq-sink-binding timer-source?message="Hello IBM MQ!" 'jms-ibm-mq-sink?serverName=10.103.41.245&serverPort=1414&destinationType=queue&destinationName=DEV.QUEUE.1&queueManager=QM1&channel=DEV.APP.SVRCONN&username=app&password=passw0rd'
This command creates the KameletBinding in the current namespace on the cluster.
39.3.2. Kafka Sink
You can use the jms-ibm-mq-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jms-ibm-mq-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: jms-ibm-mq-sink-binding
spec:
source:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: jms-ibm-mq-sink
properties:
serverName: "10.103.41.245"
serverPort: "1414"
destinationType: "queue"
destinationName: "DEV.QUEUE.1"
queueManager: QM1
channel: DEV.APP.SVRCONN
username: app
password: passw0rd
39.3.2.1. Prerequisites
Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace. Make also sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.
39.3.2.2. Procedure for using the cluster CLI
-
Save the
jms-ibm-mq-sink-binding.yamlfile to your local drive, and then edit it as needed for your configuration. Run the sink by using the following command:
oc apply -f jms-ibm-mq-sink-binding.yaml
39.3.2.3. Procedure for using the Kamel CLI
Configure and run the sink by using the following command:
kamel bind --name jms-ibm-mq-sink-binding timer-source?message="Hello IBM MQ!" 'jms-ibm-mq-sink?serverName=10.103.41.245&serverPort=1414&destinationType=queue&destinationName=DEV.QUEUE.1&queueManager=QM1&channel=DEV.APP.SVRCONN&username=app&password=passw0rd'
This command creates the KameletBinding in the current namespace on the cluster.
39.4. Kamelet source file
https://github.com/openshift-integration/kamelet-catalog/jms-ibm-mq-sink.kamelet.yaml
