Skip to main content

JBoss Fuse - Tips, Expose your Camel Route Endpoint and Web Services in Fabric.

Here is another tips and trick I think it is very useful when you want to deploy your Camel application with Fuse Fabric.

If you go back to my previous demo, my project were all deploy to container via Fuse Fabric. Fabric is great to manage and expand the environment for your applications. So what is in Fuse Fabric, a fabric is a collection of containers that share a fabric registry, within the registry you can find all the data that is needed to provisioning and managing.

If you logging to the console of Fuse Fabric. you will find four main tabs, "Runtime", "Wiki", "Dashboard" and "Health".


In the "Runtime" tab contains all the runtime operation, and management options,  such as container for run time container create/deletion. In "Profiles",we can find all the running profile(application) and the container it is running on in the page. Whereas in "Manage" actually allow you to add and remove profiles in a more clustered view. "MQ" tab allows you to configure the settings for messaging broker. And entire view of broker in the fabric environment. Registry has the exposed services in the Fabric registry. "API" and "EIP" are the 2 Tabs I want to talk about.



The "APIs" show the available web service in the fabric, and "EIP" shows the relation of the endpoints in fabric.

If you deploy you applications with only the dependency that you need in your profile, they might not be able find them in Fabric.





So to do this, it is very simple. all you have to do is just adding these feature into your profile.

  • fabric-cxf
  • fabric-groups
  • fabric-cxf-registry
  • fabric-zookeeper

And it's done.

1. Go to Wiki, and in your profile,



2. add the following feature into it.







For those of you using the fabric8 maven plugin, just add the 4 features in you configurations.

<fabric8.profile>demo-claim</fabric8.profile>
<fabric8.parentProfiles>feature-camel feature-cxf</fabric8.parentProfiles>          <fabric8.features>camel-jackson camel-cxf fabric-cxf-registry fabric-cxf fabric-zookeeper fabric-groups</fabric8.features>               
<fabric8.featureReposmvn:org.apache.camel.karaf/apache-camel/${version:camel}/xml/features </fabric8.featureRepos>

And that's it! Thanks, and good luck! :)

Comments

neha chauhan said…
Hi Christina -I wanted your demo videos
(https://www.youtube.com/watch?v=I-RIq-QCVJ8) and must say they are really helpful. However i do have a few questions - if you could answer those for me would help me in my project.

1) Why Fuse ESB - can't this(example loan demo) be achieved with pure Apache Camel ? - if yes how do I run it ? 2) Can you give me a use case when would i need FUSE ESB in this example ? 3) What is the difference between Jboss EAP and FUSE container ? 4) When does FUSE come into picture it is difficult for me to visualize it - if you could explain with a use case
Dear Neha,
Let me try to explain based on my understanding...
Jboss fuse is an ESB platform which also uses Camel for mediation, routing and transformation mechanism.

Now Jboss is a Redhat product , so for commercial benefits, Redhat can support better way than Apache group with the additional features with low cost as compared to other Integration tools like TIBCO,IBM and Oracle .

Fore more info on features on Jboss Fuse, please login to redhat portal.

To run the camel project for demo , you just need JDK,Maven , compile using mvn clean install and run using mvn camel:run


Best regards,
Sayed A.Islam

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 …