Skip to main content

JBoss Fuse - Enterprise application architecture with JBoss Fuse and JBoss BPM suite

Modern enterprise application consists of cross-communication between departments, dealing with multiple type of technologies from different era. Having a complete well design application in today's enterprise requires more then just tying up all the nots, that is, connecting all the systems, application together. One simple missed decision can lead to disastrous results of having to adjust every single application for every small changes. So it is important to define different role and responsibility of what each individual module of the application should do, and making sure they are independent form each other, so we can limit the impact of changes needed, but also flexible enough to cope with enhancements.

With JBoss BPM suite and JBoss Fuse,they are great when it comes to helping developer who wants to build an enterprise application. JBoss BPM Suite allows developers to create and monitor business process and rules. And JBoss Fuse can help with the application integration. To achieve a better software architecture we want to make sure the business aspect of the application are separated with the other. When combining these two middleware together, I found sometime it's pretty hard to define what belongs to business layer and what should go with integration? So the steps I normally goes through to define what goes where is

  • Define the business process and the people or parties involve in it. 
  • Define the services needs to provide for each step and where they belong. 

For instance, when our inventory department produces a report of old stock and ready for clearance, it require co-ordination between departments, such as finance for cost analysis to set how much lower the price can go down to and create a report, ask manager to approve the clearance base on the cost analysis. It might also need marketing for campaign on television, web advertisement. Lastly we need to make sure all shops are aware of the clearance and ready for this by automatically updating labels, and make rooms for the dispatch inventories … etc.

First thing first, we need to find out where are the business processes, and are there any existing applications providing services, as well as, are there any human interactions allowed?  Do I need to build services for this process, what are the granularity of these services?  We want to automate the process of product clearance, therefore a process is created to deal with product clearance. In the process, we need automatically calls a services that does cost analysis by accessing databases, applying business rules to calculate costs, generate reports, and let managers to review. It is then passed onto marketing team for them to organize advertising, and then a service kicks off, so each shops with the information they need to support the clearance. Here we have identify a process, it require human task interaction in both Finance and Marketing department.

For me process should be a description that even a non-IT personal should understand, this can be done by either a computer application service(either embedded or external services), or needs to pass to a human for further interactions. A process should not have transaction, no rollbacks, transactions should be capsulate in a service. You need to specify in the process to handle exception or error occurred in the process.

We can then start implement this process in JBoss BPM Suite.

Let's see the services we need for this process, few thing to watch out for on the services, look for existing services and reuse them as possible. Avoid building complex business algorithm into integration service, make it simple and small (microservices?), if really need to include these logic, use Drools, or java bean to encapsulate and package them, so whenever if we need to change it, it minimize the impact to integration layer by simply replace the package. In our example case here are the services I defined:

A. A automatic polling services from the inventory that kickstart the clearance process. This polling services pulls

B. Cost analysis that calculate the cost and generates report.

C. Generates and print labels for the clearance.

D. Print out shipping schedule.

E. Handle situation when the clearance was rejected by managers.
All the above services can be easily done by utilizing the Enterprise Integration Pattern in Apache Camel of JBoss Fuse and then deploy onto distributed lightweight ESB container, which can be provision, manage and monitor with JBoss Fuse too.

And put all these together, it'll become an application architecture for this particular case.

As for later monitoring of the application in maintenance phase, in JBoss Fuse, by going to Fuse Console, you will see how each one of the service are doing and manage it through the console accordingly. As for processes, inside BPM suite, there is a BAM, which allows you to see the statistics of processes, tasks and even business related data by configuring it.


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 …