PubNub
Since Camel 2.19
Both producer and consumer are supported
Camel PubNub component can be used to communicate with the PubNub data stream network for connected devices. This component uses pubnub java library.
Use cases include:
-
Chat rooms: Sending and receiving messages
-
Locations and Connected cars: dispatching taxi cabs
-
Smart sensors: Receiving data from a sensor for data visualizations
-
Health: Monitoring heart rate from a patient’s wearable device
-
Multiplayer games
-
Interactive media: audience-participating voting system
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-pubnub</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The PubNub component supports 13 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
The component configurations. |
PubNubConfiguration |
||
UUID to be used as a device identifier, a default UUID is generated if not passed. |
String |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
|
Also subscribe to related presence information. |
false |
boolean |
|
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
|
The operation to perform. PUBLISH: Default. Send a message to all subscribers of a channel. FIRE: allows the client to send a message to BLOCKS Event Handlers. These messages will go directly to any Event Handlers registered on the channel. HERENOW: Obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count. WHERENOW: Obtain information about the current list of channels to which a uuid is subscribed to. GETSTATE: Used to get key/value pairs specific to a subscriber uuid. State information is supplied as a JSON object of key/value pairs SETSTATE: Used to set key/value pairs specific to a subscriber uuid GETHISTORY: Fetches historical messages of a channel. Enum values:
|
String |
||
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
|
If Access Manager is utilized, client will use this authKey in all restricted requests. |
String |
||
If cipher is passed, all communications to/from PubNub will be encrypted. |
String |
||
The publish key obtained from your PubNub account. Required when publishing messages. |
String |
||
The secret key used for message signing. |
String |
||
Use SSL for secure transmission. |
true |
boolean |
|
The subscribe key obtained from your PubNub account. Required when subscribing to channels or listening for presence events. |
String |
Endpoint Options
The PubNub endpoint is configured using URI syntax:
pubnub:channel
with the following path and query parameters:
Query Parameters (14 parameters)
Name | Description | Default | Type |
---|---|---|---|
UUID to be used as a device identifier, a default UUID is generated if not passed. |
String |
||
Also subscribe to related presence information. |
false |
boolean |
|
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
|
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
ExceptionHandler |
||
Sets the exchange pattern when the consumer creates an exchange. Enum values:
|
ExchangePattern |
||
The operation to perform. PUBLISH: Default. Send a message to all subscribers of a channel. FIRE: allows the client to send a message to BLOCKS Event Handlers. These messages will go directly to any Event Handlers registered on the channel. HERENOW: Obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count. WHERENOW: Obtain information about the current list of channels to which a uuid is subscribed to. GETSTATE: Used to get key/value pairs specific to a subscriber uuid. State information is supplied as a JSON object of key/value pairs SETSTATE: Used to set key/value pairs specific to a subscriber uuid GETHISTORY: Fetches historical messages of a channel. Enum values:
|
String |
||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
|
Autowired Reference to a Pubnub client in the registry. |
PubNub |
||
If Access Manager is utilized, client will use this authKey in all restricted requests. |
String |
||
If cipher is passed, all communications to/from PubNub will be encrypted. |
String |
||
The publish key obtained from your PubNub account. Required when publishing messages. |
String |
||
The secret key used for message signing. |
String |
||
Use SSL for secure transmission. |
true |
boolean |
|
The subscribe key obtained from your PubNub account. Required when subscribing to channels or listening for presence events. |
String |
Message Headers
The PubNub component supports 4 message header(s), which is/are listed below:
Message body
The message body can contain any JSON serializable data, including: Objects, Arrays, Ints and Strings. Message data should not contain special Java V4 classes or functions as these will not serialize. String content can include any single-byte or multi-byte UTF-8
Object serialization when sending is done automatically. Just pass the full object as the message payload. PubNub will takes care of object serialization.
When receiving the message body utilize objects provided by the PubNub API.
Examples
Publishing events
Default operation when producing. The following snippet publish the event generated by PojoBean to the channel iot.
from("timer:mytimer")
// generate some data as POJO.
.bean(PojoBean.class)
.to("pubnub:iot?publishKey=mypublishKey");
Fire events aka BLOCKS Event Handlers
See https://www.pubnub.com/blocks-catalog/ for all kind of serverless functions that can be invoked. Example of geolocation lookup
from("timer:geotimer")
.process(exchange -> exchange.getIn().setBody(new Foo("bar", "TEXT")))
.to("pubnub:eon-maps-geolocation-input?operation=fire&publishKey=mypubkey&subscribeKey=mysubkey");
from("pubnub:eon-map-geolocation-output?subscribeKey=mysubkey)
// geolocation output will be logged here
.log("${body}");
Subscribing to events
The following snippet listens for events on the iot channel. If you can add the option withPresence, you will also receive channel Join, Leave asf events.
from("pubnub:iot?subscribeKey=mySubscribeKey")
.log("${body}")
.to("mock:result");
Performing operations
herenow : Obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count of the channel
from("direct:control")
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=herenow")
.to("mock:result");
wherenow : Obtain information about the current list of channels to which a uuid is subscribed
from("direct:control")
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=wherenow&uuid=spyonme")
.to("mock:result");
setstate : Used to set key/value pairs specific to a subscriber uuid.
from("direct:control")
.bean(StateGenerator.class)
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=setstate&uuid=myuuid");
gethistory : Fetches historical messages of a channel.
from("direct:control")
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=gethistory");
There is a couple of examples in test directory that shows some of the PubNub features. They require a PubNub account, from where you can obtain a publish- and subscribe key.
The example PubNubSensorExample already contains a subscribe key provided by PubNub, so this is ready to run without a account. The example illustrates the PubNub component subscribing to a infinite stream of sensor data.
Spring Boot Auto-Configuration
When using pubnub with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-pubnub-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 14 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
If Access Manager is utilized, client will use this authKey in all restricted requests. |
String |
||
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
|
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
|
If cipher is passed, all communications to/from PubNub will be encrypted. |
String |
||
The component configurations. The option is a org.apache.camel.component.pubnub.PubNubConfiguration type. |
PubNubConfiguration |
||
Whether to enable auto configuration of the pubnub component. This is enabled by default. |
Boolean |
||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
|
The operation to perform. PUBLISH: Default. Send a message to all subscribers of a channel. FIRE: allows the client to send a message to BLOCKS Event Handlers. These messages will go directly to any Event Handlers registered on the channel. HERENOW: Obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count. WHERENOW: Obtain information about the current list of channels to which a uuid is subscribed to. GETSTATE: Used to get key/value pairs specific to a subscriber uuid. State information is supplied as a JSON object of key/value pairs SETSTATE: Used to set key/value pairs specific to a subscriber uuid GETHISTORY: Fetches historical messages of a channel. |
String |
||
The publish key obtained from your PubNub account. Required when publishing messages. |
String |
||
The secret key used for message signing. |
String |
||
Use SSL for secure transmission. |
true |
Boolean |
|
The subscribe key obtained from your PubNub account. Required when subscribing to channels or listening for presence events. |
String |
||
UUID to be used as a device identifier, a default UUID is generated if not passed. |
String |
||
Also subscribe to related presence information. |
false |
Boolean |