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 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 。
加上…

JBoss Fuse - Fuse workshop 101 - Part One

On my way to Hong Kong for a day of workshop on JBoss Fuse, and as I go through my Slide deck, I cannot find any decent easy workshop for beginners. Therefore I decide make a workshop that is easy for Camel first timer to get their hands dirty.

The first of part of the workshop is an introduction to Camel, it first goes through what is exactly inside JBoss Fuse.

For part one of the workshop, it takes your through the very basic of Camel, one of the very important component inside JBoss Fuse.
Every Camel need to have a runtime container to run in, inside camel we call it a CAMEL CONTEXT.  Inside every Camel context, you can define lots of camel route and registry, don't worry about what those are, we will explain later.


So inside out blueprint xml, you will see a tag called camelContext.



Next up is camel route, they are a chain of command or process defined by you, as a developer.
Inside the camel route, there are consumer endpoints that listens to the incoming messages, producers …