Skip to main content

Red Hat JBoss Fuse - Fuse Management Console in EAP

One thing I love about JBoss Fuse is the ability to visualize my Camel route and see how it is doing on the fly in pretty GUI interface. In JBoss Fuse, you will able to see these from Fuse management console under http://INSTALL_IP:818/, It provide an GUI interface to manage available Profiles in Fabric in Wiki page, logs view, health view, JMX console, OSGi views, A-MQ Broker manage console, Apache Camel, and Fuse Fabric. What happens when if I want to deploy my Camel Application on JBoss EAP? Is it possible to see the same thing in JBoss EAP? The answer is Yes!

When you install the JBoss Fuse patch on to JBoss EAP, you will notice there are two WAR files also deployed on to it as well. One of them is our JBoss Fuse management console! By going to http://localhost:8080/hawtio/login with the same ID/PWD as you enter in Enterprise Admin Console. You will be greeted with the welcome page. 


On the top, You will see Connect, Dashboard, JBoss, JMS and Threads tabs, notice I did not mention Camel as it appears in my diagram, that is because it will only show when there are Camel application deploy on the container. 

Anything you can do with Camel route in JBoss Fuse on Karaf container, you can find it here too in JBoss EAP. You can view the diagram representation of your camel route, along with the statistics of messages passing through each node. And you can also debug the route in the console, start debugging under "Debug" tab, set break point, and then off we go, 



As the message reach the break point, it will pause and you can see all the body content, header information on the console, click continue button to keep going,


 If you don't like pausing between endpoints, there is an option to trace your messages running in the route. By turning the Trace function on, you will be able to trace messages going through the route.


The detail header content will also display.

You can also see how each endpoint or processor are doing with each route.


 Edit the route on the fly.
 And don't forget there are also summarized view how all the route in the container too. Speaking of container, there are sometimes needs to see how it is doing, by going to Dashboard tab, it will show the CPU load, JVM status, and various states of the container.


Under JBoss tab, from here we can manage specific to the container that is running, for instance, in Application, it shows all the applications deployed on the container, here you can undeploy, start, stop or restart it.



 This is another piece of useful information, it shows all the used port in the container, so you know where to find all the endpoints.


 And lastly, a console display how the threads are doing.

That's all for now, I found this management console comes in quite handy when trying to deploy a Camel application on EAP. I hope you do too. :) 

Comments

Patrick Steiner said…
Hi Christina, my Hawtio console is not connected to Fuse, any advice on how to achieve that?

Thanks, Patrick
D.Naranjo said…
Christina, I have both Fuse - Karaf flavor and Fuse - EAP scent installed on my machine, since I'd like to perform tests with both containers.

When I try to enter the Hawtio GUI using the port assigned to the EAP version, the user+password used to enter the EAP Management console does not work at all!

Any advice?

Thanks,
Dennis J. Naranjo
Santiago, Chile.

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 …