jms amqp 10 sink JMS - AMQP 1.0 Kamelet Sink

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Preview"

A Kamelet that can produce events to any AMQP 1.0 compliant message broker using the Apache Qpid JMS client

Configuration Options

The following table summarizes the configuration options available for the jms-amqp-10-sink Kamelet:

Property Name Description Type Default Example

destinationName *

Destination Name

The JMS destination name

string

remoteURI *

Broker URL

The JMS URL

string

"amqp://my-host:31616"

destinationType

Destination Type

The JMS destination type (i.e.: queue or topic)

string

"queue"
Fields marked with (*) are mandatory.

Usage

This section summarizes how the jms-amqp-10-sink can be used in various contexts.

Knative Sink

The jms-amqp-10-sink Kamelet can be used as Knative sink by binding it to a Knative object.

jms-amqp-10-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jms-amqp-10-sink-binding
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: jms-amqp-10-sink
    properties:
      destinationName: "The Destination Name"
      remoteURI: "amqp://my-host:31616"

Make sure you have Camel K installed into the Kubernetes cluster you’re connected to.

Save the jms-amqp-10-sink-binding.yaml file into your hard drive, then configure it according to your needs.

You can run the sink using the following command:

kubectl apply -f jms-amqp-10-sink-binding.yaml

Dependencies

The Kamelet needs the following dependencies:

  • camel:jms

  • camel:kamelet

  • mvn:org.apache.qpid:qpid-jms-client:1.0.0

Binding to Knative using the Kamel CLI:

The procedure described above can be simplified into a single execution of the kamel bind command:

kamel bind channel:mychannel jms-amqp-10-sink -p "sink.destinationName=The Destination Name" -p "sink.remoteURI=amqp://my-host:31616"

This will create the KameletBinding under the hood and apply it to the current namespace in the cluster.

Kafka Sink

The jms-amqp-10-sink Kamelet can be used as Kafka sink by binding it to a Kafka topic.

jms-amqp-10-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jms-amqp-10-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-amqp-10-sink
    properties:
      destinationName: "The Destination Name"
      remoteURI: "amqp://my-host:31616"

Ensure that you’ve installed Strimzi and created a topic named my-topic in the current namespace. Make also sure you have Camel K installed into the Kubernetes cluster you’re connected to.

Save the jms-amqp-10-sink-binding.yaml file into your hard drive, then configure it according to your needs.

You can run the sink using the following command:

kubectl apply -f jms-amqp-10-sink-binding.yaml

Binding to Kafka using the Kamel CLI:

The procedure described above can be simplified into a single execution of the kamel bind command:

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic jms-amqp-10-sink -p "sink.destinationName=The Destination Name" -p "sink.remoteURI=amqp://my-host:31616"

This will create the KameletBinding under the hood and apply it to the current namespace in the cluster.

Kamelet source file

Have a look at the following link:

https://github.com/apache/camel-kamelets/blob/main/jms-amqp-10-sink.kamelet.yaml

Back to top