Skip to main content

JBoss Fuse - Automating your environment with Fuse CLI

If you take a look at few of my startup script in my demo from "jbossdemocentral", you will see that I have automated the process of creating JBoss Fuse Fabric, deploying profiles into fabric, creating containers and install these profiles on top of the containers. 

In normal production environment, you will probably startup the JBoss fuse in the background. Under JBoss Fuse installation directory, under bin, you will find several executable scripts or batch, to start JBoss Fuse in the background, simply run the "start" or "start.bat" depending what  your operating system is. And to stop the background process, simply run the "stop" or "stop.bat".  
To access the command line console when it's running in the background, we can run the "client" or "client.bat" in the bin folder. It'll will take you to the command line console, where you normally see when running fuse. 


To automate and managing JBoss Fuse using CLI in script, we will call this "client" executable script with the command we want to run. This is the basic idea of this tip. 

Creating Fabric

If you take a look at my script, first you will see this, this set up the Fabric in JBoss Fuse. 

sh $FUSE_SERVER_BIN/client -r 3 -d 10 -u admin -p admin 'fabric:create --wait-for-provisioning'

In my demos and example, I am starting from scratch, which installed the JBoss Fuse, but I need fuse fabric installed, that's why you will find this in my script. In normal production, Fuse Fabric should be there to manage the entire fuse environment, so you will probably leave this out. 

There are few parameters in client that might be useful to you, 

  -u [user]     specify the user name
  -r [attempts] retry connection establishment (up to attempts times)
  -d [delay]    intra-retry delay (defaults to 2 seconds)

I added the retry attempts because sometime the karaf is not fully started when it's creating fabric in script, so retry running the command is a really useful feature to me. And then fabric:create --wait-for-provisioning is just normal command line for you to create and setup Fabric in JBoss Fuse. 

Build and Deploy

The next part of my script will go on and start building and deploying my project, here I am taking advantage of a great maven plugin feature in Fabric. Basically what is does, is it will start of building your application, and then create a profile in fabric with all the feature and bundle you specify in pom.xml. (Please see my previous post on this plugin for more details)

mvn fabric8:deploy

After running this part of the script, you will find your application profile in the wiki menu. 


Now we have application ready to go, my next part of the script will start creating new containers, and deploy the profile onto container. 

sh $FUSE_SERVER_BIN/client -r 2 -d 5 'container-create-child --profile demo-travelagency-webendpoint root wsflightcon'

In this sample, it creates a container called "wsflightcon" it inherits from the root container, and we also added a profile name "demo-travelagency-webendpoint". In the console, under runtime, you should see all the container you have created. 


Last thing I want to mention is the checking script. 

echo Testing containers startd,retry when not ready
while true; do
    if [ $(sh $FUSE_SERVER_BIN/client 'container-list'| grep "success" | wc -l ) -ge 7 ]; then
        break
    fi
    sleep 2
done

Here it checks if all the 7 containers are successfully created and application are deployed. By calling the "container-list" it will list all the container and it's status. 

That's all for now. 



Comments

Ian Ellis said…
Thanks. Nice read :)

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 …