jms apache artemis source JMS - Apache Artemis Source

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Stable"

Receive data from an Apache Artemis message broker by using JMS.

Configuration Options

The following table summarizes the configuration options available for the jms-apache-artemis-source Kamelet:

Property Name Description Type Default Example

brokerURL

Broker URL

Required The JMS URL.

string

tcp://k3s-node-master.usersys.redhat.com:31616

destinationName

Destination Name

Required The JMS destination name.

string

destinationType

Destination Type

The JMS destination type (queue or topic).

string

queue

Dependencies

At runtime, the jms-apache-artemis-source Kamelet relies upon the presence of the following dependencies:

  • camel:jms

  • camel:kamelet

  • mvn:org.apache.activemq:artemis-jakarta-client-all:2.32.0

Camel JBang usage

Prerequisites

  • You’ve installed JBang.

  • You have executed the following command:

jbang app install camel@apache/camel

Supposing you have a file named route.yaml with this content:

- route:
    from:
      uri: "kamelet:timer-source"
      parameters:
        period: 10000
        message: 'test'
      steps:
        - to:
            uri: "kamelet:log-sink"

You can now run it directly through the following command

camel run route.yaml

Camel K Environment Usage

This section describes how you can use the jms-apache-artemis-source.

Knative source

You can use the jms-apache-artemis-source Kamelet as a Knative source by binding it to a Knative object.

jms-apache-artemis-source-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: jms-apache-artemis-source-pipe
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: jms-apache-artemis-source
    properties:
      brokerURL: tcp://k3s-node-master.usersys.redhat.com:31616
      destinationName: The Destination Name
  sink:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the jms-apache-artemis-source-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the source by using the following command:

    kubectl apply -f jms-apache-artemis-source-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind channel:mychannel -p "source.brokerURL=tcp://k3s-node-master.usersys.redhat.com:31616" -p "source.destinationName=The Destination Name" jms-apache-artemis-source

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kafka source

You can use the jms-apache-artemis-source Kamelet as a Kafka source by binding it to a Kafka topic.

jms-apache-artemis-source-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: jms-apache-artemis-source-pipe
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: jms-apache-artemis-source
    properties:
      brokerURL: tcp://k3s-node-master.usersys.redhat.com:31616
      destinationName: The Destination Name
  sink:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic

Prerequisites

  • You’ve installed Strimzi.

  • You’ve created a topic named my-topic in the current namespace.

  • You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the jms-apache-artemis-source-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the source by using the following command:

    kubectl apply -f jms-apache-artemis-source-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic -p "source.brokerURL=tcp://k3s-node-master.usersys.redhat.com:31616" -p "source.destinationName=The Destination Name" jms-apache-artemis-source

This command creates the Kamelet Pipe in the current namespace on the cluster.