Skip to main content

JBoss Fuse - Updates of Fuse 101 Labs

I have been updating my previous demos and lab so they can be all up to date and applies to the latest Fuse 6.2 version. And now I am starting to regret why I have created so many demos … But when every time I go back to previous work, there are always something that can be worked on or improve. It's actually a good thing. So don't be surprised if I end up re-writing the entire demo.

I spent a few days updating My Camel 101 Labs, so here are the links to my labs and things I've changed when migrating to Fuse 6.2, summarizing for those of you who has already done the lab, and wants to see what has been updated in a quick glance. (Note, the page counts in things I've changed, does not include the title page.)

Lab 1. Camel basic and components

Things I update: 
Page 2, updated to new Camel version : 2.15.1.redhat-620133
Page 6,7, new JBDS tooling, with a lot more built-in component, before I ask people to fill in the uri of each component, but now we can take advantage of using the tooling by filling in variable in properties view.
Page 10,11,12 Introduce the new debugging capability in Fuse 6.2

Lab 2. Data Transformation

Things I update:
Page 4,5, Since we now have a great drag and drop data mapping tool in JBDS, I remove the simple jaxb unmarshaller, and use dozer and jaxb that comes with the data mapping tool. So first added the XSD file needed for the conversion.
Page 7, added image to make instruction more clear
Page 8,9,  Start the Data Mapping using new data mapping tool.
Page 10, Update marshaller with new screen shots
Page 12, Remove test dependency as it will mess up when deploy to fabric

Lab 3. Enterprise Integration Pattern

Things I update:
Page 1, update to the new route diagram in Fuse 6.2
Page 2,3,4,5,6,7, Instead of listing all the node and properties participants needs to fill in, I change the way describing how to add, delete modify the components. By relinking, re-ordering the nodes. And allow more interaction with the new component tooling.
Page 8, updated Route diagram.
Page 9,10, same as before, more screen shots.
Page 11. updated the diagram to latest Fuse 6.2 look.

Lab 4. Bean Registry

Things I update:
Page 3,4 Add more screen shots, and more detail description on how to add bean reference.
Page 8, use new Component in Tooling and update active-camel dependency version to 5.11.0.redhat-620133

Lab 5. OSGi Container

Things I update:
I rewrite the entire lab for this one, because of the updated of the tooling, we can now set JBoss Fuse Karaf as server in JBDS. And add application just like using Java EE containers.

  • Shows how to setup server in JBDS
  • Show how to use the shell console in JBDS
  • Show how to add application to server
  • Show OSGi JMX view and Camel route view in Fuse integration Tooling 

Lab 6. Fuse Fabric

Things I update:
Page 2, Update to new console view
Page 3,4, updates the new fabric8:deploy setup, remove the jolokia address setting.
Page 5,6,7,8 update to new Fuse console view
Page 9, Add how to stop container and servers.

Link on the Lab title will take you back to my previous workshop blog, Enjoy!


Popular posts from this blog

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.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


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


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

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

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 …

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 …