Eclipse Kura component
Kura component is available starting from Camel 2.15.
This documentation page covers the integration options of Camel with the Eclipse Kura M2M gateway. The common reason to deploy Camel routes into the Eclipse Kura is to provide enterprise integration patterns and Camel components to the messaging M2M gateway. For example you might want to install Kura on Raspberry PI, then read temperature from the sensor attached to that Raspberry PI using Kura services and finally forward the current temperature value to your data center service using Camel EIP and components.
Bundles deployed to the Eclipse Kura are usually developed as bundle activators. So the easiest way to deploy Apache Camel routes into the Kura is to create an OSGi bundle containing the class extending
Keep in mind that
KuraRouter implements the
org.osgi.framework.BundleActivator interface, so you need to register its
stop lifecycle methods while creating Kura bundle component class.
Kura router starts its own OSGi-aware
CamelContext. It means that for every class extending
KuraRouter, there will be a dedicated
CamelContext instance. Ideally we recommend to deploy one
KuraRouter per OSGi bundle.
Bundle containing your Kura router class should import the following packages in the OSGi manifest:
Keep in mind that you don't have to import every Camel component bundle you plan to use in your routes, as Camel components are resolved as the services on the runtime level.
Before you deploy your router bundle, be sure that you have deployed (and started) the following Camel core bundles (using Kura GoGo shell)...
...and all the components you plan to use in your routes:
Then finally deploy your router bundle:
Kura router base class provides many useful utilities. This section explores each of them.
Kura uses SLF4J facade for logging purposes. Protected member
log returns SLF4J logger instance associated with the given Kura router.
bundleContext returns bundle context associated with the given Kura router.
camelContext is the
CamelContext associated with the given Kura router.
producerTemplate is the
ProducerTemplate instance associated with the given Camel context.
consumerTemplate is the
ConsumerTemplate instance associated with the given Camel context.
OSGi service resolver
OSGi service resolver (
service(Class<T> serviceType)) can be used to easily retrieve service by type from the OSGi bundle context.
If service is not found, a
null value is returned. If you want your application to fail if the service is not available, use
requiredService(Class) method instead. The
IllegalStateException if a service cannot be found.
KuraRouter activator callbacks
Kura router comes with the lifecycle callbacks that can be used to customize the way the Camel router works. For example to configure the
CamelContext instance associated with the router just before the former is started, override
beforeStart method of the
Loading XML routes from ConfigurationAdmin
Sometimes it is desired to read the XML definition of the routes from the server configuration. This a common scenario for IoT gateways where over-the-air redeployment cost may be significant. To address this requirement each
KuraRouter looks for the
kura.camel.BUNDLE-SYMBOLIC-NAME.route property from the
kura.camel PID using the OSGi ConfigurationAdmin. This approach allows you to define Camel XML routes file per deployed
KuraRouter. In order to update a route, just edit an appropriate configuration property and restart a bundle associated with it. The content of the
kura.camel.BUNDLE-SYMBOLIC-NAME.route property is expected to be Camel XML route file, for example:
Deploying Kura router as a declarative OSGi service
If you would like to deploy your Kura router as a declarative OSGi service, you can use
deactivate methods provided by