Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "BaSyx / Documentation / Components / DataBridge / Features / Protocol Integration / ActiveMQ"

(Created page with "= Active MQ = The ActiveMQ broker can be integrated with DataBridge. When the message on the configured topic is published the route would process the data. == Configuration...")
 
Line 21: Line 21:
 
== Naming Convention ==
 
== Naming Convention ==
 
The name of the ActiveMQ consumer configuration file should be '''activemqconsumer.json'''.
 
The name of the ActiveMQ consumer configuration file should be '''activemqconsumer.json'''.
 +
 +
== Working Example ==
 +
The integration example with ActiveMQ as a consumer, JsonAta as a transformer, and AAS as a data sink is on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/basyx.components.databridge.examples/basyx.components.databridge.examples.activemq-jsonata-aas DataBridge Example].

Revision as of 07:27, 31 January 2023

Active MQ

The ActiveMQ broker can be integrated with DataBridge. When the message on the configured topic is published the route would process the data.

Configuration

To configure ActiveMQ consumer in DataBridge you need to provide the unique id, and the ActiveMQ server details like host, port, and the queue i.e. the topic.

Sample Configuration

[
	{
		"uniqueId": "property1",
		"serverUrl": "127.0.0.1",
		"serverPort": 61616,
		"queue": "first-topic"
	}
]

Similarly, you can configure multiple ActiveMQ consumers inside the configuration file.

Naming Convention

The name of the ActiveMQ consumer configuration file should be activemqconsumer.json.

Working Example

The integration example with ActiveMQ as a consumer, JsonAta as a transformer, and AAS as a data sink is on DataBridge Example.

Back to the top