Skip to main content

Red Hat JBoss Fuse - Deploy a WAR file with Servlet

In normal integration project we built SOA architecture, or more recently microservice seems to be the hottest buzz word around, but no matter that how big or small the service is, it's still a service. In integration our primary job is to become the moderator between systems, allow systems to talk, communicate smoothly, by that, we have lots of protocols to work with, MQTT, AMQP for messaging, Restful JSON or SOAP XML for web service, Files, FTPS etc... But what if or end communication or response end is a human? We can't expect a human being to process a bunch of large text, XML or stream of bits, I mean, yes, some may, but not in most cases. There for we often process and simplify information on a page, that is readable by human. For that by creating a web application renders these data to users comes in very handy.

In java space, we will most likely to create a WAR file and run it on a Java EE container (JBoss EAP). But what about running the WAR file on Karaf container in Fuse? And how do I add my Camel file on to it? Here is how.

First, I am going to create a WAR project, just like what  we will normal do when creating a web application.  I prefer to use maven archetype for this.



And then we will need to add the dependency needed to run Camel route, please add the following camel related dependencies in pom.xml.

    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-core</artifactId>
      <version>2.15.1.redhat-62xxxx</version>
     
    </dependency>
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-spring</artifactId>
      <version>2.15.1.redhat-62xxxx</version>
     
    </dependency>
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-stream</artifactId>
      <version>2.15.1.redhat-62xxxx</version>
     
    </dependency>
   
    <!-- Spring Web -->
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>4.1.6.RELEASE</version>
    </dependency>
   
    <!-- logging -->
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-api</artifactId>
      <version>1.7.10</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-log4j12</artifactId>
      <version>1.7.10</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>log4j</groupId>
      <artifactId>log4j</artifactId>
      <version>1.2.17</version>

    </dependency>

Then we need to think about setting Spring, since all the Spring beans lives in ApplicationContext,we need to set it up. By setting the ContextLoaderListener it will load my camel files match *-context.xml and create an ApplicationContext for it.

  <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>/META-INF/*-context.xml</param-value>
  </context-param>
   
  <listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>

  </listener>

And then we can start adding our Camel application. Here I am going to create a very simple Hello World Camel route, that prints out "Hello world" in every 5 seconds.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
       http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
       http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
    <!--
        Simple camel route which send every one minute a message on the console.
    -->
    <camelContext xmlns="http://camel.apache.org/schema/spring">
        <route id="timer-to-console">
            <from uri="timer://foo?fixedRate=true&amp;period=5s"/>
            <transform>
               <simple>Hello Web Application, how are you?</simple>
            </transform>
            <to uri="stream:out"/>
        </route>
    </camelContext>

</beans>

There are many options available to deploy our WAR application in JBoss Fuse, I am going to show you on of them, maybe later, if I have time, I can go through how to deploy through Maven plugins. But let's stick to the basics for now. First we do what we normal do to generate the WAR file.

mvn clean install




Go to JBoss Fuse, Install it, and make sure you have created Fabric. If you are not sure how, please check out my Fuse 101 Workshop. Once JBoss Fuse is started, go to http://localhost:8181. Create a container with Profile name feature-fabric-web




After container started. Go into container view, and in console, click on the OSGi tab. And on the top right corner, enter

  • war:mvn:com.redhat/springtest/1.0.0-SNAPSHOT/war?Web-ContextPath=springtest

and click the tick to install.


After install successful message appear, select it on the list and start it.


You will see the logs running under log console.


So, this is how you add Camel Route to your web application. That's all.

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 …