Skip to main content


Showing posts from October, 2014

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 sele

JBoss Fuse/A-MQ - Easy way to achieve fault tolerant messaging Part 2

So here is the step by step video to create Failover Client I promise last time. Before you begin, please make sure you have created the Master/Slave broker beforehand. Here are the videos: Create Master/Slave Broker Create Client Camel Application You can find my sample code in github: Before begin, there are some setups you need to do, Download JBoss Fuse from Add fabric server passwords for Maven Plugin to your ~/.m2/settings.xml file the fabric server's user and password so that the maven plugin can login to the fabric. <server>   <id>fabric8.upload.repo</id>   <username>admin</username>   <password>admin</password> </server> There are 2 ways to tackle this example, First is to everything manually, create a Master/Slave Broker, build the client Camel Application from scratch and then deploy them onto Fuse. Secon

JBoss Fuse/A-MQ - Easy way to achieve fault tolerant messaging Part 1

Following some of the questions I got from the people during the enablement in APAC, one of the question I get is how to do achieve fault tolerant, I believe there are already many works done out there that talks very technical and search deeply in this area. But as always, I am going to show few simple steps to achieving fault tolerant messaging with A-MQ. The simplest way to make your messaging system fault tolerant is to make your broker into Master/Slave group. Therefore when one broker goes down a backup server will takeover. So we can now ensure our broker will always be up and running, Fuse does a beautiful job of detecting and switching. There are 2 ways to spin up an the broker, one with the beautiful management GUI with Fuse, or the old hardcore command line. Please make sure you have installed Fuse and boot up the Fabric before you begin. Logon to JBoss Fuse management Console, under Runtime -> MQ-> +Broker Add group, broker name and choose Mast