Skip to main content

Red Hat JBoss Fuse - Integrating Database, Java Bean and Restful Services in EAP, Java DSL with CDI

We have talked about how to start develop application in EAP with Java DSL, and most interestingly how to utilize the CDI framework in JavaEE. And in this post we are going to take that example a bit more further, show you how to integrate with Databases, Java beans in the application, creating a servlet and lastly setup a Restful webservice.

For this currency exchange project, I have store the exchange rate in the h2 database. What we are going to do is to display the entire exchange rate on the webpage provided by a restful web service and provide a servlet that takes in the amount of money and the currency to exchange to, send them back to server, calculated and return the result. So here are the things I am going to do


  • Database
  • Java Bean
  • Servlet
  • Restful Web Services

Database
Of course we want to use the datasources in EAP. So first thing first, create the datasource in EAP. Make sure you started the JBoss EAP. Go to Configuration, select Connector and then to datasources.

  • Name :MyCamelDS
  • JNDI Name: java:jboss/datasources/MyCamelDS


 Select the Driver we are going to use, and it's h2 this case,

Enter the

  • Connection URL: jdbc:h2:file:~/h2/fuseoneap;AUTO_SERVER=TRUE
  • Username: sa
  • Password: 


Change the min and max pool size to 1 and 10. And then enable the MyCamelDS datasource.


And there we are, datasource ready!
We can then use the CDI framework to lookup datasource in JNDI. So create a CDI Producer, in CDI, the producer produce an object that can be injected which we are going later inject the datasource into our camel context.

public class DatasourceProducer {

  @Resource(lookup= "java:jboss/datasources/MyCamelDS")
  DataSource dataSource;

  @Produces
  @Named("MyCamelDS")
  public DataSource getDataSource() {
    return dataSource;  }
 

}

You will be surprised on how easy it really is to use it in Camel, because it's done. Now in our RouteBuilder class, we are going select every single exchange rate in the database. We are going to use the SQL component in Camel, provide the SQL, and then provide the datasource name we named in the producer we created. 

Lastly we are going to transform the resultset in JSON format, using the built-in transformation components in Camel.  

  from("direct:getCurrencies").routeId("allcurrencies")
  .to("sql:select * from currencyexchange?dataSource=MyCamelDS")
  .marshal()
  .json(JsonLibrary.Jackson);

That's it!

Java Bean
First thing, create a Java class that has a method takes in amount of money and currency to exchange. And on top of the class, place the @Name annotation, this will allow the bean we created to accessible through the EL. And we can lookup the bean from Camel.

  @Named("currencyconvertor")
  public class CurrencyConvertor {
    public double convertUSD(double amt, ArrayList<Map<String, Object>> data){
      Double rate = (Double)data.get(0).get("rate");
      return amt*rate;
    }

  }

To use it in the Camel route, just use the bean components in Camel. 

  from("direct:getCurrency").routeId("covertcurrency")
  .log("Got currency: ${headers.amt} and amt${headers.currency} ")
  .choice()
    .when()
      .header("currency")
      .to("sql:select * from currencyexchange where currencycode = :#currency?dataSource=MyCamelDS")
      .log("exchange rate ====> ${body[0][rate]}")
      .to("bean:currencyconvertor?method=convertUSD(${headers.amt},${body})")
  .otherwise()
    .log("nothing to lookup")
     .transform().constant("nothing to lookup");

Servlet
We need to setup the Servlet, under webapp, create the WEB-INF/web.xml file. Right click on Deployment Descriptor and choose Generate Deployment Descriptor Stub. It will create an empty web.xml file for you.

Add the servlet setting in the web.xml and publish it 

  <servlet>
    <servlet-name>camel</servlet-name>
    <servlet-class>org.apache.camel.component.servlet.CamelHttpTransportServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
  </servlet>

  <servlet-mapping>
    <servlet-name>camel</servlet-name>
    <url-pattern>/services/*</url-pattern>
  </servlet-mapping>

Once it's done, we can then use the Servlet component in Camel, it will publish a servlet endpoint through the Servlet we set earlier.


    from("servlet:///currency?servletName=camel&matchOnUriPrefix=true")
  .routeId("servletCurrency")
  .to("direct:getCurrency");

Restful Web Service
The Restful web services needs to have the CamelHttpTransportServlet setup too, since we have already done that in Servlet, all we have to do is to builds Rest endpoints as consumers in Rest DSL. And then configure it to servlet.

  restConfiguration().component("servlet")
      .contextPath("/camel").port(8080).bindingMode(RestBindingMode.json);
 
  rest("/currenciesrest")
      .get()
      .produces(MediaType.APPLICATION_JSON)

      .to("direct:getCurrencies"); 

That's all you have to do. You can find the entire project code here.


Comments

Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …