Skip to main content

JBoss Fuse - How to setup cluster of servers in Fabric

Staying in Beijing for a technical enablement, one question I have been ask a lot is how to setup a Fabric in a cluster of servers with JBoss Fuse?

I am going to setup 2 Fuse on 2 different servers, and then join them together to form a fabric cluster.
BUT!!!! In the real world please make it at least 3 servers, as zookeeper needs more then 3 to successfully setup it's ensembles! 


First we need to create a fabric, so unzip the JBoss Fuse zip file in Server1, setup password by editing etc/user.properties.

And please do the same thing to server2. If you are testing, and tries to setup on the same machine, please remember to go to "org.apache.karaf.management.cfg" under etc/ and change the RMI related port.



also there are a few more port you need to adjust,

org.apache.karaf.shell.cfg, change the

  • sshPort

and last inside system.properties

  • org.osgi.service.http.port
  • activemq.port
  • activemq.jmx.url


Now, getting back to setting the cluster of fabric, start up JBoss Fuse by going into bin/ and execute fuse on server one. After it starts up, create a fabric by entering the following command:

fabric:create --wait-for-provisioning

This spins up a fabric on a container call root, now, start up JBoss Fuse on server2 by going to bin/ and execute fuse on server two. And instead of creating a fabric, we are going to join, by entering following command, as fabric:join [options] zookeeperUrl [containerName] .

fabric:join --zookeeper-password admin 192.168.0.1:2181 root1

To find out what the zookeeper URL, go to your fuse command line console in Server1 and type
config:edit io.fabric8.zookeeper
config:proplist

this will give you your zookeeper details

                       JBossFuse:karaf@root> config:proplist
            service.pid = io.fabric8.zookeeper
            zookeeper.password = ZKENC=YWRtaW4=
            zookeeper.url = 192.168.0.1:2181
            fabric.zookeeper.pid = io.fabric8.zookeeper

And now we have successfully created a fabric on 2 servers. If you type in container-list in the command line, you should be able to see we now have 2 working server.

JBossFuse:karaf@root> container-list 
[id]                           [version] [connected] [profiles]                                         [provision status]
root*                          1.0       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full    success
root1                          1.0       true        fabric                            

And if you login to Fuse management console, under Runtime-> Containers you will see the 2 root containers on both servers


To add a new container, click on +Create on top right hand corner of the page, select the parent container so it will run on the server base on the parent container. Then choose the profile you need to install on the container.

And we are done!




Comments

Hi Christina!
Supposing my server1 (root container) goes down, what happens to the profile that I published in it?

Thanks
...or is it a good practice to publish profile on both containers?
Christina Lin said…
Actually, the profile is published to the fabric, not on a single container. so the fabric servers in the ensembles will duplicate these profiles within. So if any of them goes down, the other one will still work.
Hello , First i want to thank you for all the efforts you have done.
I followed all the steps you did on this tutorial.
i'm going to describe what i did exctely , i created a fabric on server1 after i have joined two containers (fabric:join as you did) (once at the same machine , the second from a remote pc at the same lan)
but when i executed the command "fabric:ensemble-add " to add the two containers already created to the ensemble , i had this error message "connection refused to host 192.168.56.1"
but i don't have any device runing with that ip knowing that my ip on lan have this structure 192.168.3.?
i don't why fuse had created a virtual network with that ip adress?
Christina Lin said…
When creating you fabric, try use "--manual-ip" to force setting your desire ip, so zookeeper wont go all over the place to get the IP. See if that works?
Mahran MJ said…
This comment has been removed by the author.
Mahran MJ said…
Hi Christina , Thank you for the tutorials you made , they helped me so much to learn Fuse ,
i Have a question about this tutorial , i did exactly what you did and i successfully created my Fabric Ensemble that contains 3 Fabric Server (that 2 fabric seervers at the same machine and the 3rd at a remote machine at the same lan ), until now i have no problem :)
My question is : if i want to link a profile (contains an application fuse Project web-Service) to a fabric, on which container should i link it? should i link it to one container on each fabric servers ? and what ip address should be called to invoke that webservice? what to do if one of this server goes down ?
i hope that you understand my question,Thanks

Popular posts from this blog

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 …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

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 …