Skip to main content

JBoss Fuse for xPaaS - How to setup a Fuse on OpenShift Enterprise Virtual Machine with Virtual Box

I am a pure software developer deep from my bones, so when it comes to installing OpenShift, the last thing I want to do is to go through all the Linux, network setups, extra.. Luckily with OpenShift I have 2 choice, First is the easiest, just go to OpenShift Online, and by simply registering an account, you will be able to get 3 gears to play with and no hassle on setting up the openshift environment. The second option is to use the Virtual Machine provided to run a pre-set OpenShift environment, I am going to show you how to do that!

Before we begin, please make sure you have download the OpenShift 2.1 or 2.2 Virtual Machine image from Red Hat Customer Portal. Then install Virtual Box.

Start up Virtual Box, click on "New" to create a new virtual machine,

Before you start up the VM, right click on the instance you created, choose "settings... ", a configuration window will pop up, and then click on the "Network" Tab, and make sure you have selected the Bridge adapter.

Or sometimes depends on your network environment, it is easier to just setup a Host-only Adapter, this can be set under Preference,

Go to Network, setup the Adapter,
And DHCP Server,

Instead of setting to Bridge Adapter, set it up to Host-only Adapter,

Start up your VM instance when done, it might take couple of minutes to start up.  you should see a Terminal and FireFox started. type in "ifconfig" in the terminal console, here you will see the IP for this VM instance. We are going to configure the host machine to look up the DNS.

In Linux, Simply edit the /etc/resolv.conf configuration file and add the IP address of your VM instance. For example


However, in Mac, setting the “resolv.conf” does not work, please go to System Preferences -> Network, and click on the Advance button on the right lower corner, and then on the top TAB, choose “DNS”, add the ip address of your VM instance, as we are going to use it's built in DNS resolver. And add as the domain to look up.

Open up a browser in your host machine, and go to, and you will immediately ask for the  ID/PWD to logon to OpenShift. Type in demo for ID and openshift for password. There you will see the openshift pages.

Now it’s time to install the client in our host so we can interact with the OSE (short for OpenShift Enterprise). First we need to install the rhc client.

To install the RHC in Mac, simply run, (make sure you have installed Ruby in advance)
            sudo gem install rhc
for Linux or other operating system and more details please visit this page.

After successfully install the client, now it’s time to setup the rhc client, to do that simply go to your command line console, and type
            rhc setup --server -l demo -p openshift

In the process, you will be asked to provide a phrase for RSA key, type in anything that you will remember, and let the process keep running, in a few seconds, it will be ready to go.

Now we are ready to create a FUSE application, go back to browser. And click on “create yours first application”,  on following page. depend on your OSE version, click on Fuse cartridge, 

or you can type in following URL in define my own application

In the next page, fill in your application name and domain name, 

After a few minutes of download and installing the FUSE application, you will be presented with the authorization information, please keep it. Remember the ID/PWD.

Go to the Fuse URL you will see the, logon using the ID/PWD and congratulation you have created the FUSE application.

And that's it, you can now start playing with Fuse on OpenShift Enterprise in your local environment.  


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


Connection Pool 最少會存留的connection 數量


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


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

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

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…