Tuesday, November 25, 2014

JBoss Fuse - Connecting to Twitter and the Aggregator pattern

If you think connecting to Facebook is easy with Camel, try connecting to Twitter! It's every easier!
Before connecting to Twitter, make sure you have register a twitter developer account, and go to https://apps.twitter.com/. Create a new Twitter App.

There are a few mandatory parameter for authentication if you want to play with Twitter, they are :
  • consumerKey - The consumer key
  • consumerSecret - The consumer secret 
  • accessToken - The access token
  • accessTokenSecret - The access token secret

Also Twitter has Consumer  as it handle mostly polling functionality, such as search from content, streaming tweets from twitter etc.

  • timeline/home - read or polls tweet from user home
  • search - search specific keywords,
  • streaming/filter - get streaming of data from twitter.

Whereas Producer handles tweeting and calling of twitter API, they might also include searching and timeline polling too.

  • directmessage - gets the message 
  • search - search for keywords
  • timeline/user - polling from users
For more detail please visit the product documentation

Note, currently Twitter API is in version V1.1, using the JBoss Fuse 6.1 should work without a problem. since it's base on Twitter4j V3.x

To play with Camel-Twitter connector.
First, we are going to create a twitter app(make sure you have already register an developer account for Twitter), and then go to https://apps.twitter.com/ 

Provide details of the app, then you will come to the application console, click on (modify app permissions) so we can read and publish into our account.

Click on Generate My Access Token and Token secret to get the authentication keys under Your Access Token.

Save both customer and access token and token secret somewhere handy, because we are going to need them later. Make sure you have installed JBDS and the integration plugin.
Go to JBDS, create a new blueprint Fuse project, enter Group ID and artifact ID.

Open pom.xml and add camel-facebook dependency.

Drag the endpoints from palette to canvas,
Endpoint with uri :


and log: ${body.source}

Add the properties file containing twitter authentication settings, the 4 must have parameter mentioned above, and fill them in by mapping the tokens you get from creating the Twitter App.
  • consumerKey - The consumer key
  • consumerSecret - The consumer secret 
  • accessToken - The access token
  • accessTokenSecret - The access token secret
Map the properties file into Camel Context by using "propertyPlaceholder"

<propertyPlaceholder location="classpath:twitter.properties" id="twitter"/>

So you can start test the first part of the Twitter Camel Example. Related videos can be found here:

Now, going back to our demo. In part 2, we are going to poll tweets every 10 secs from your personal timeline, and analysis the source device of the tweets, and make a summary of how many time each device was use and tweets the result back to Twitter!

From part one, we have already polling tweets from twitter, now to further process the content, add a content switch to the route, that will add 4 different header content to the header bane "devicetype" and call another route for further process.

                ${body.source} == "Web Client"
                ${body.source} == "iPhone"
                ${body.source} == "Android"

Notice we are using "seda" to pass the route, seda. The seda: component provides asynchronous SEDA behavior, so that messages are exchanged on a BlockingQueue and consumers are invoked in a separate thread from the producer. We do that because the twitter connector creates one route exchange per returned object, instead of returning a list of tweets, and in our example, the order of process does not matter.

With all the different tweets coming in separately, we now want to summarize the total device, that's when the EIP Aggregator becomes very handy. The Aggregator from the EIP patterns allows you to combine a number of messages together into a single message. In this component, we can implement our own aggregation strategy, and choose different ways when to stop the aggregation, like aggregate every 10 seconds, aggregate every 5 messages, or after certain sizes or even end in some predicted condition.  (For more details, please read the product document). In our demo, we are aggregating every 10 seconds.

So create a java bean that holds the device data (Web, iPhone, Android and Others)
package org.blogdemo.twitterdemo;

public class SourceCounter {
 private int web = 0;
 private int android = 0;
 private int iphone = 0;
 private int others = 0;

 public void addType(String type){
   web ++;
 public void addWeb() {
 public void addAndroid() {
 public void addIphone() {
 public void addOthers() {
 public int getWeb() {
  return web;
 public void setWeb(int web) {
  this.web = web;
 public int getAndroid() {
  return android;

 public void setAndroid(int android) {
  this.android = android;
 public int getIphone() {
  return iphone;
 public void setIphone(int iphone) {
  this.iphone = iphone;

 public int getOthers() {
  return others;

 public void setOthers(int others) {
  this.others = others;

 public String toString() {
  return "web:["+web+"] iphone:["+iphone+"] android:["+android+"] others:["+others+"]";

And create our own aggregation strategy by adding number to the java bean, base on the "devicetype" header.

package org.blogdemo.twitterdemo;

import org.apache.camel.Exchange;
import org.apache.camel.processor.aggregate.AggregationStrategy;

public class SourceAggrateStrategy implements AggregationStrategy {

 public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
  SourceCounter counter = null;
  if (oldExchange == null) {
   counter = new SourceCounter();
         counter = oldExchange.getIn().getBody(SourceCounter.class);
  String newType = newExchange.getIn().getHeader("deviceType").toString(); 
  return newExchange;

Add the strategy into Camel context in the blueprint.xml,

<bean id="sourceAggrateStrategy" class="org.blogdemo.twitterdemo.SourceAggrateStrategy" />

Setup the aggregator,

And then at the end, we are exporting the result back to Twitter, using the twitter connector again.

                Summarizing the device tweeting every 10 secs from my twitter using Camel, ${body}

Here is the part two video, it takes you through step by step of building the demo.

You can also find the code and the one click ready in my Github account too!

Following the instruction in Github, installing the application onto JBoss Fuse, you can also see the run time detail too!


Wednesday, November 19, 2014

JBoss Fuse - Connecting to Facebook

Got your camel working? now it's time to have some fun, how about update your Facebook status using Camel? From Camel 2.12 onwards, Facebook endpoint was added, which makes it a lot easier to implement.

So how does it works? Basically, Facebook provides a unofficial Java API called "facebook4j", so Camel uses this API to implement the integration with Facebook. 

Basically, Facebook requires OAuth for all client application authentication, please go to the Facebook developer site and register.  

And create a new application, because Facebook require you to set authority to different function for each application. For instance, with application A, you grant the publish and poll right with all your photos, and application B you grant the location information to it. So click on the "Apps" tab on top of the page. 

Choose website, 

Give a name to your application, and choose the type of your application,

Skip or go through the quick start.  After that, you will arrive in your demo dashboard, it has the information required to authenticate your camel accessing Facebook, make sure you store the App ID and App Secret (click on "show" to display), because we are going to use it later.

Let's take the easy way, and use the Graph API explorer tool to generate your token. A token is the key tells Facebook how long your session last and the approval permissions. We are going to use the temporary short-term token. Further reading about the token can be found here.

Choose the application you have created, and click on the Get Access Token,

The permissions pops up, make sure you click on the permission that you what to use. For our case, please click on "publish_actions" in "Extended Permission", and make sure you store the access token somewhere.

And now we are ready to create our first Camel-Facebook application. There are 3 must have parameters, 
  • oAuthAppId - The APP ID from application Dashboard 
  • oAuthAppSecret - The APP Secret from application Dashboard 
  • oAuthAccessToken - The user access token we got from the tool

There are also other none mandatory options, make sure you check the document if needed. 

Like the other camel components, Facebook also have Producer and Consumer too. 

Use Facebook producer when you want to send or perform actions on to Facebook, like posting a status, uploading a photo, leave comments, get account information and adding Tags, etc.. The detail functionality are also available on the document too. 

On the other hand consumer endpoints are responsible for the reading part of the action, we will also play with that in the demo too. 

This is a simple demo, to avoid any privacy issues with your friends, this time we are going to get your birthday from Facebook, calculate how many days left till your next birthday, and then publish it to your Facebook status. 

Make sure you have installed JBDS and the integration plugin.  
Go to JBDS, create a new blueprint Fuse project, enter Group ID and artifact ID. 

Open pom.xml and add camel-facebook dependency. 

Drag the endpoints from palette to canvas, 
Endpoint with uri : 

and log: ${body}

Add the properties file containing facebook authentication settings, the 3 must have parameter mentioned above,  
  • oAuthAppId - The APP ID from application Dashboard 
  • oAuthAppSecret - The APP Secret from application Dashboard 
  • oAuthAccessToken - The user access token we got from the tool

The result returning from Facebook are objects from Facebook4j, simply create a java bean that does the actual business calculation. 

package org.blogdemo.fbdemo;

import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;

import facebook4j.User;

public class BirthdayCounter {

 public int count(User user){
  if(user == null || user.getBirthday() == null){
   return -1;
  String birthday = user.getBirthday();
     SimpleDateFormat sdf = new SimpleDateFormat("MM/dd/yyyy"); 
     SimpleDateFormat yf = new SimpleDateFormat("yyyy");
     Date date = new Date();
     int endYear = Integer.parseInt(yf.format(date));
     String birthdayTempString = birthday.substring(0, birthday.length()-4)+endYear;
     Date birthdayThisYear = null;
     Date birthdayNextYear = null;
     try {
      birthdayThisYear = sdf.parse(birthdayTempString);
  } catch (ParseException e) {
     //Determine we should calculate from this year or next year
      return 0;
     }else if(birthdayThisYear.before(date)){
      birthdayTempString = birthday.substring(0, birthday.length()-4) + (endYear+1);
      try {
    birthdayNextYear = sdf.parse(birthdayTempString);
   } catch (ParseException e) {
      birthdayTempString = birthday.substring(0, birthday.length()-4) + (endYear-1);
      birthdayNextYear = birthdayThisYear;
     int dayDiff = daysBetween(date,birthdayNextYear);
  return dayDiff;
 private int daysBetween(Date d1, Date d2){
  return (int)( (d2.getTime() - d1.getTime()) / (1000 * 60 * 60 * 24));

And create another bean that converts String of text to another Facebook4j object, because we are going to publish a status feed to Facebook, and it will need to use the Facebook4j.postUpdate as the input body. 

package org.blogdemo.fbdemo;

import facebook4j.PostUpdate;

public class FBUpdator {
 PostUpdate postUpdate = null;
 public PostUpdate update(String test){
  postUpdate = new PostUpdate(test);
  return postUpdate;

Add two beans to the camel context by referencing it in the blueprint xml. 

  <bean id="birthdayCounter" class="org.blogdemo.fbreader.BirthdayCounter"/>
 <bean id="fbUpdator" class="org.blogdemo.fbreader.FBUpdator"/>

Now, complete the rest of the route. 

                ${body} < 0
                    I am a very mysterious person
                ${body} == 0
                    It's My BIRTHDAY!!!!
                    Counting down... ${body} more days to my birthday

Run the camel route, and you will see the feed posted in Facebook home!

I have break the demo into 2 videos, 

First one shows you how to setup Facebook App and poll data from Facebook.

Second one shows you how to process and publish feed to Facebook status.

You can also find the code and the one click ready in my Github account too! 

Wednesday, November 5, 2014

JBoss Fuse/A-MQ - Playing with Insight/Elastic Search Tech Preview of Fuse

This week in Berlin, I met awesome Red Hat SA Roel Hodzelmans , who showed me the "fun stuff" that you can play with in JBoss Fuse, although this is still a Tech Preview function, I think would be great for people to take play with this and give as much testing as possible.

Kibana is an open source browser based analytics and search dashboard for ElasticSearch.

Steps to do an Insight/Elastic Search demo of Fuse, make sure the environment has enough disk space.

1) In the root container add the Kibana profile - this is the management console for Elastic Search.

It will add a new tab next to Runtime, Wiki, Dashboard, Health and Insight. The preparation takes a couple of minutes, depends on your resource.

2) Add the insight core profile to all containers where you want to capture the logging from

3) Create a new profile or profile version to which you want to add insight in the camel parts to,

then add insight-camel feature to the features of the profile

4) Migrate a container to the new version or create a target container with the new version and add the newly created profile to the container in question

Once you have it install and your application running, you could see 5 different views:

Logs- where you get insight in the log statements

Metric, this should be have data on your JVM etc, but there are still work to be done here

Camel Events shows all Camel exchanges, note the Exchange ID is also posted here

Camel shows a text box into which you can put an Exchange ID. When succesfull (no whitepaces, wildcards or partial strings!) it will draw a sequence diagram detailing the time spend at all components. If your route had good ID's for the endpoints, it will display those names else you get generated id's, making it hard to read

ESHead shows you the elastic search component itself, in which the data is stored and you can
    a) see the cluster health,
    b) make your own queries...etc

You can follow Roel on Twitter @RoelHodzelmans

Thursday, October 30, 2014

JBoss Fuse for xPaaS - How to setup a Fuse on OpenShift Enterprise Virtual Machine with Virtual Box

I am a pure software developer deep from my bones, so when it comes to installing OpenShift, the last thing I want to do is to go through all the Linux, network setups, extra.. Luckily with OpenShift I have 2 choice, First is the easiest, just go to OpenShift Online, and by simply registering an account, you will be able to get 3 gears to play with and no hassle on setting up the openshift environment. The second option is to use the Virtual Machine provided to run a pre-set OpenShift environment, I am going to show you how to do that!

Before we begin, please make sure you have download the OpenShift 2.1 or 2.2 Virtual Machine image from Red Hat Customer Portal. Then install Virtual Box.

Start up Virtual Box, click on "New" to create a new virtual machine,

Before you start up the VM, right click on the instance you created, choose "settings... ", a configuration window will pop up, and then click on the "Network" Tab, and make sure you have selected the Bridge adapter.

Or sometimes depends on your network environment, it is easier to just setup a Host-only Adapter, this can be set under Preference,

Go to Network, setup the Adapter,
And DHCP Server,

Instead of setting to Bridge Adapter, set it up to Host-only Adapter,

Start up your VM instance when done, it might take couple of minutes to start up.  you should see a Terminal and FireFox started. type in "ifconfig" in the terminal console, here you will see the IP for this VM instance. We are going to configure the host machine to look up the DNS.

In Linux, Simply edit the /etc/resolv.conf configuration file and add the IP address of your VM instance. For example


However, in Mac, setting the “resolv.conf” does not work, please go to System Preferences -> Network, and click on the Advance button on the right lower corner, and then on the top TAB, choose “DNS”, add the ip address of your VM instance, as we are going to use it's built in DNS resolver. And add openshife.example.com as the domain to look up.

Open up a browser in your host machine, and go to http://vm.openshift.example.com, and you will immediately ask for the  ID/PWD to logon to OpenShift. Type in demo for ID and openshift for password. There you will see the openshift pages.

Now it’s time to install the client in our host so we can interact with the OSE (short for OpenShift Enterprise). First we need to install the rhc client.

To install the RHC in Mac, simply run, (make sure you have installed Ruby in advance)
            sudo gem install rhc
for Linux or other operating system and more details please visit this page.

After successfully install the client, now it’s time to setup the rhc client, to do that simply go to your command line console, and type
            rhc setup --server vm.openshift.example.com -l demo -p openshift

In the process, you will be asked to provide a phrase for RSA key, type in anything that you will remember, and let the process keep running, in a few seconds, it will be ready to go.

Now we are ready to create a FUSE application, go back to browser. And click on “create yours first application”,  on following page. depend on your OSE version, click on Fuse cartridge, 

or you can type in following URL in define my own application


In the next page, fill in your application name and domain name, 

After a few minutes of download and installing the FUSE application, you will be presented with the authorization information, please keep it. Remember the ID/PWD.

Go to the Fuse URL you will see the, logon using the ID/PWD and congratulation you have created the FUSE application.

And that's it, you can now start playing with Fuse on OpenShift Enterprise in your local environment.