Skip to main content

JBoss Fuse - Fuse workshop 101 - Part Six

This is the last part of Fuse workshop 101, we have gone through the development part, what about in real production environment? This workshop is all about the operation and management side of JBoss Fuse. The technology we use for this purpose is called Fabric8. Fabric8 mainly takes care of  provision, automate, configure, and manage from a central location.
Since in real production environment, we will need to manage tens and hundreds of Karaf containers, we need a way to coordinate between containers and to be able to discover all the available service on them, this is where zoo keeper comes in. To discover all the service, we have a place to store all the runtime information, it's call runtime registry. And all the configuration for containers are grouped into something called profile, where you can apply the profile to sets of containers. Hawtio is the GUI for you to visualize the entire environment. 

So to provide this fabric service, we will need a server to actually run the fabric, the server running the fabric is called "Fabric Server", it provide the registry service, maintains a replicable database of information about the state of the fabric. And in order to make sure our server does not became the single point of failure, we will create multiple Fabric server to achieve high availability. It's called ensemble. 
So within every Fabric server, the runtime state of the fabric is stored, in side the run time registry you will find all the relevant information about each container. 
As well as the runtime status, Fabric also stores the configuration data in a git repository, each fabric server has the complete copy of this data. And because we are using git, all the configurations are versioned. And we combined a set of configuration into a profile, and then apply these profiles into the container we want it to run in.

Inside each Profiles, you will have static configuration files like, json, xml, properties and the links or URL of where to get your code(bundle), it also has information on what features and bundles you want to include in this profile.
Just to clarify, the program package you as the developer develops are called bundles. (It's actually a jar with some META-DATA of your endpoint). A feature is a set of bundles and also features that you combine together.
So, last thing I want to talk about before we move on to how to deploy, is the maven proxy embedded inside fabric. The proxy actually connects to 2 different set up maven repository, one is the local repo, the other is the remote one locate outside your machine. The container uses it to locate the actual program describe in the profile and download it to the container to run.
To make it absolutely clear, the way we normally deploy is

  1. Write your code and then package it into bundle
  2. Create a profile in the fabric, add the necessary feature and bundle you need for the profile, including your program
  3. In fabric, create a new container (or use the existing one)
  4. Add the profile you created to the container.
Or you can simply deploy your program using the fabric8:deploy maven plugin. It will automatically installed the profile and settings according to the configuration that is set in the pom.xml. 

There are several way to operate in fabric, using the command line using the fabric client, or through the GUI interface Hawtio. Below is a picture of what each tab takes you to in the fabric. 

The Slides are here:

This time for the lab, we are going to just deploy our camel route into the fabric. And see it running. 

And the lab instruction:



Workshop part 1 - Camel basic and components
Workshop part 2 - Data Transformation 
Workshop part 3 - Enterprise Integration Pattern
Workshop part 4 - Bean Registry
Workshop part 5 - OSGi Container

Comments

Rick said…
Very nice. Thank you!
There's no link from Part Five to this Part Six, should have it ;)
Christina Lin said…
Thanks César, I updated!

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

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …