Skip to main content

JBoss Fuse - Fuse workshop 101 - Part Two

In an ideal world, all software system should use the same protocol, and passing the same type of documents, but sadly, due to time, needs and other reasons that I can't think of, current software systems are full with different types of protocol and formats of data. As a integration developer, we spend a great deal of time just to make two software system understand each other.

Fuse workshop 101 part two is all about message transformation.


In JBoss Fuse, there are different kind of transformations,

So Format or Type and Message content enrichment or reduction are types of transformation that plays around and changes your message body. and Metadata updates mainly modify the header of your messages.

An example of Format transformation is from XML to CSV or from CSV to JSON, or simply just flattening out from one XML to another. whereas Type transformation is about changing the Object type to another, such as from java.lang.String to java.lang.Integer.

So there are few ways you can do format/type transformation, Camel has built-in component, called Marshal, basically converting from a more higher level of data (here we simply means java bean) to lower levels of data like XML, CVS or JSON etc...

the opposite of that is, of course, Unmarshal. Converting from files into complex java object.

The tooling in JBoss Developer studio will show all the available ready to use data format.
take for example, converting from XML to JSON, this is the why to describe it.

<unmarshal>
  <xmljson/>
</unmarshal>

Or you can do it with JAXB

<unmarshal> 
  <jaxb partClass=“example.TradeOrder” contextPath=“example"/>
</unmarshal>

Another way of transforming the message is to use the transform tag(component) in Camel. It uses various scripting languages, by running message body through the script you set, it will generate the result as the transformed output. Here is an example using javascript.

<javaScript> 
   request.body.toLowerCase()

</javaScript>

OK! Now we have Processor and Bean left, the last two ways of transformation are very similar, in both cases you need to create a java class. You will pass in the message through the Processor or Bean. And inside Processor and Bean, you will add your transformation logic there. This is highly customizable.


The only difference between the two, is the parameter you pass through them, with Process, you need to first implements the camel.Processor interface, then in the execute method, you will find the parameter is the exchange object, so you will have the access to the whole message. Whereas, in Bean, it's just a POJO, by adding the transform logic inside a method, the message will pass through it. And NOTICE, it's only the BODY of the message. So the parameter of the method is actually your message body.

There is another way of transforming messages, using the Enterprise Integration Pattern, there are a few built-in patterns that allows you to easily change or transform your message, I won't go too much detail into that. We will talk about EIP in the later workshop.



Time for another Camel Ride, this time, we are taking the Camel route we built, which is taking a file from a vendor and then place it in another folder for another vendor to retrieve later. Now we know that Vendor sending us the stock ordering info is providing their content in XML, and the vendor that needs this info needs it to be in JSON. And beside both vendor, our company needs to process the content too, and since we are a Java-shop, we want to make sure the content is turned into POJO.

Here is the slides for part 2


And this is the lab instruction.
Enjoy! JBoss Fuse workshop part 3 is coming up next!

Workshop part 1 - Camel basic and components
Workshop part 3 - Enterprise Integration Patterns


Comments

Hi,
I followed your 2nd ride lab but stuck at adding dependency to pom.xml

JDBS show following error:

missing artifact org.apache.camel:camel-jaxb:2.12.0.redhat-610379

and
missing artifact org.apache.camel:camel-jackson:2.12.0.redhat-610379

(for jaxb, I can search from Dependencies tab of pom.xml but search not found for jackson)

Please helps. How to fix this?
Christina Lin said…
Check which repo you are pulling your maven dependency from.

<repository> ​ <id>fusesource</id> ​ <url>http://repo.fusesource.com/nexus/content/groups/public/</url> ​ <snapshots> ​ <enabled>false</enabled> ​ </snapshots> ​ <releases> ​ <enabled>true</enabled> ​ </releases> ​ </repository>
Hi Christina
My problem is fix by change repo.
Thanks!
jmandawg said…
Order3.xml does not work. I don't think it is valid for the schema. I get the following error:

Caused by: com.sun.istack.SAXParseException2; lineNumber: 3; columnNumber: 11; unexpected element (uri:"", local:"multiple"). Expected elements are <{}stocktrading>
Shoaib Khan said…
Hi Christina,

So far I found it to be very informative and updated tutorial based on latest release of JBoss Fuse. Thank you so much for making it available out there on web.

Just curious to know if the slides here can be available in PDF format as its bit difficult to switch full screen slides and back to JBoss Developer to follow step by step. Thank you.
Hi Cristina....

I got this issue when i finish the Data Transformation box.

Unexpected error: String index out of range: -1
String index out of range: -1
M Vishukumar said…
Hi Christina...

Could you please answer this question?
I am not able to see options in Marshall and Unmarshall pellet.
https://stackoverflow.com/questions/43329162/jboss-marshall-options-are-not-showing

Thanks, Vishu

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

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

事先將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 …