Skip to main content

Red Hat JBoss Fuse - Moving Camel application between OSGi and JavaEE containers

Now that JBoss Fuse supports both OSGi Karaf and JavaEE JBoss EAP container. When to use which one, is there any best practice for which container to use? And same as the answer as any other software related question, well, any questions in life actually. "it depends" .... Situation varies between cases, here are my point of view, you many like it or disagree, I am very happy to hear more of your thoughts.

Here is the thing, I think, it is BEST if you stick with Karaf container if possible for now. It is more light weight, which means you can deploy application much more quickly and expend faster horizontally with application distributed everywhere. And the may OSGi manages the lifecycle of the services allows you to dynamically deploy and undeploy service without affecting the others service in the same container. That, is very important in for mission critical services. So if you get to choose which ever to use go with Karaf.
What I also believe is, in an enterprise you should not be restricted to use Single kind of container, different container framework exist for a reason. Especially if you are providing a web application with EJB, JARs complex application glue together to serve as the core business for the web application. Maybe it's a legacy application that has everything done in the Application server. Or it simply has too many non-OSGi compatible libraries to work with. Then I will go for the JBoss EAP scenario.

So how to move from OSGi to JavaEE container or vise versa? Moving a bundle from OSGi to JavaEE is dead simple. But please note, use the Spring framework instead of Blueprint, if you are using OSGi, I would first convert it Spring then work with it.

In this case I will be using a WAR application, since most people use this format in JavaEE and it is supported in Karaf as well.

So there are few ground rules if you want to switch back and forth between the containers, is


  • Use Spring Framework
  • Make sure your Camel route is placed under META-INF under webapp and named *-camel-context.xml

  • Set you plugins to generate metadata needed for OSGi container.
    • Add maven-bundle-plugin        
       <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <version>2.3.7</version>
        <extensions>true</extensions>
        <executions>
          <execution>
            <id>bundle-manifest</id>
            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <supportedProjectTypes>
            <supportedProjectType>jar</supportedProjectType>
            <supportedProjectType>bundle</supportedProjectType>
            <supportedProjectType>war</supportedProjectType>
          </supportedProjectTypes>
          <instructions>
            <Bundle-SymbolicName>camel-blueprint</Bundle-SymbolicName>
            <Private-Package>com.redhat.springtest</Private-Package>
            <Import-Package>*</Import-Package>
          </instructions>
        </configuration>
       </plugin>

By sticking with these rules will allow you to create a project that can deploy on both containers.
In JBoss Fuse Karaf Container,

  • Install with Profile or using OSGi command, 
    • war:mvn:com.redhat/springtest/1.0.0-SNAPSHOT/war?Web-ContextPath=springtest
  • Make sure to have feature-fabric-web profile in your container

Running JBoss EAP Container with Fuse application.

  • Deploy and install by
    • Drag and drop the WAR file under deployment folder
    • Using Console/CLI deployment
  • Make sure Fuse subsystem is installed and activated. 
  • Remember to disable ContextLoaderListener in web.xml

Here is a video showing how to move application between containers.

Comments

Unknown said…
Hi Christina,
Very helpful post, have you uploaded the sources of the example anywhere ?
Thanks !
Shoaib Khan said…
Hi Christina,

Thanks for the insight and sharing your views on this. Actually after trying JBoss Fuse 6.3 on EAP I felt the same.

Just to clarify, doesn't it mean Red Hat is taking away the concept of Microservices with this new model of deployment where again it goes like huge WAR deployment and aweful method of manual configurations? Why not to just stick with Apache Karaf + Camel as the best ESB solution in the world adhering to Micro Services archicture and lifting all the load of such manual configurations and confusions. After using Fuse ESB with blueprint DSL i even don't see need for Spring DSL for ESBs. Ofcouse spring/java or any other DSL can be used in embedded integration solutions. But I really don't see any need to bundle JBoss Fuse with EAP.

I fear if in future Red Hat might discontinue the Karaf backend container and only provide support for EAP. That would be the worst decision in my opinion.

Popular posts from this blog

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 …

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 …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …