Skip to main content

Red Hat JBoss Fuse - 3 ways to develop you Fuse application in JBoss EAP, XML route with JNDI

In this series post I am going to show the different ways of developing a Camel web application running in JBoss EAP.
  • Spring Framework
  • CDI with Java DSL
  • XML without Spring
To make things clear and easy, I will be using the exact same Camel route for all there different methods.What this Camel route does, is it starts up a timer that will log every 5 second, simple, easy, not much going on.

Before we start develop our simple camel route, we need to a base WAR project to work on, so first we need to create a WAR file, I am sure you must have a million way to create that, every one sort of have their own best practice for this. For me, in the example, I will create one with maven, using the webapp-javaee6 artifact. 

A. Create Project, select Maven Project, 

B. Click Next when you are at New Maven Project, and it will take you to the next step, select the webapp-javaee6 artifact.

C. Add your project name, and then click Next, you will have a ready to go WAR project in your JBoss Developer Studio. (Note, for my examples later, I am going to give them different project Names)

D. Add Camel dependency in the pom.xml file (do make sure you maven repo is configure properly pointing to http://repo.fusesource.com/nexus/content/repositories/releases)

    <!-- camel -->
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-core</artifactId>
      <version>2.15.1.redhat-621xxx</version>
      <scope>provided</scope>
    </dependency>


E. Optional, change your JDK version accordingly in pom.xml of the WAR project.




Camel Route without Spring

Sometimes we just don't want to rely on Spring or CDI, just to keep everything simple. Camel uses the JNDI registry to achieve this. So no spring library is needed nor do we have to enable the CDI framework in JavaEE. A perfect solution if you don't want any heavy framework involve.

  • Before we start, we are going to need another camel dependency, this is the package we need to scan and kickstart our camel route.
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-servletlistener</artifactId>
            <version>2.15.1.redhat-620133</version>
        </dependency>

Under webapp, we need to create the WEB-INF/web.xml file, as we need it to configure the listener that reading our Camel route and then kicks it off. Right click on Deployment Descriptor and choose Generate Deployment Descriptor Stub. It will create an empty web.xml file for you.




  • Add the location of your camel file, and the listener that register and kicks off the camel route in the web.xml

<context-param>
    <param-name>name</param-name>
    <param-value>MyCamel</param-value>
</context-param>
<context-param>
    <param-name>routeBuilder-MyRoute</param-name>
    <param-value>classpath:myfisrtcamel.xml</param-value>
</context-param>
<listener>
    <listener-class>org.apache.camel.component.servletlistener.JndiCamelServletContextListener</listener-class>
</listener>

  • This is what your web.xml will look like:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
  <display-name>myjndidemo</display-name>
  
  <context-param>
    <param-name>name</param-name>
    <param-value>MyCamel</param-value>
  </context-param>
  <!-- location of Camel route xml files -->
  <context-param>
    <param-name>routeBuilder-MyRoute</param-name>
    <param-value>
    classpath:myfisrtcamel.xml
    </param-value>
  </context-param>

  <!-- the listener that kick-starts Camel -->
  <listener>
    <listener-class>org.apache.camel.component.servletlistener.JndiCamelServletContextListener</listener-class>
  </listener>
  
  <welcome-file-list>
    <welcome-file>index.html</welcome-file>
  </welcome-file-list>

</web-app>

  • Create folder called "resources" under main for Camel Route XML file.   



  • Then add the folder in the Class Path, right click on the project, and select Build Path, configure build path




  •  Check the resource folder we just created!




Create Camel route called "myfisrtcamel.xml", make sure choose the "Routes" framework. 


  • Within route, drag and drop timer and log component and configure them. 
    • Timer URI: timer:mytimer?period=5000
    • Log Message: JNDI EAP Camel Demo
  • This is what your XML look like: 
 <?xml version="1.0" encoding="UTF-8"?>
  <routes xmlns="http://camel.apache.org/schema/spring">
  <route>
    <from uri="timer:mytimer?period=5000"/>
    <log message="JNDI EAP Camel Demo"/>
  </route>
</routes>

  • And then we are done, ready to go. Run mvn clean install to generate the war file. 





  • Start up your JBoss EAP with Fuse subsystem enabled. If you are not sure how to do it, please take a look at this post. In side bin folder, start JBoss EAP with 
    • standalone.sh
    • standalone.bat
  • Go to http://localhost:9990/, login to admin console, under Runtime/

  • Click on Add, choose the war generated under the project target folder. Click Next, Next to deploy the application. 
  • Start up application by click on the En/Disable button. 


  • Switch to the log, you will find it's now printing the message "JNDI EAP Camel Demo" every 5 seconds.

Comments

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …