How to Install and Run Red Hat JBoss Fuse: Step-by-Step

How to install JBoss Fuse ?

Go to the site and download JBoss Fuse Service Works 6.1.0 Jar (Installer). Or check other versions.

Make sure you have a JDK of your choice installed. We recommend OpenJDK or Oracle JDK.

In Windows or Mac, you can extract the contents of the ZIP archive by double clicking on the ZIP file. In Linux, open a terminal window in the target machine and navigate to where the ZIP file was downloaded. Extract the ZIP file by executing the following command:

    unzip jboss-fuse-full-6.1.0.redhat-379.zip

You can now (optionally) install the Integration Stack for JBoss Developer Studio. This provides IDE support for developing JBoss FSW applications. For more details, see the Getting Started Page.

Once you exact the zip file you will the folder as jboss-fuse-6.1.0.redhat-379 . Go to the folder as command below.

dev@jdg-developer-desktop ~/Downloads $ cd /home/dev/Downloads/jboss-fuse-6.1.0.redhat-379

dev@jdg-developer-desktop ~/Downloads/jboss-fuse-6.1.0.redhat-379 $ ls

bin  data  dependencies.txt  deploy  etc  extras  fabric  lib  licenses  license.txt  notices.txt  quickstarts  readme.txt  system

dev@jdg-developer-desktop ~/Downloads/jboss-fuse-6.1.0.redhat-379 $ cd bin/

dev@jdg-developer-desktop ~/Downloads/jboss-fuse-6.1.0.redhat-379/bin $ ls

admin  admin.bat  client  client.bat  fuse  fuse.bat  karaf  karaf.bat  patch  patch.bat  setenv  setenv.bat  start  start.bat  status  status.bat  stop  stop.bat

dev@jdg-developer-desktop ~/Downloads/jboss-fuse-6.1.0.redhat-379/bin $ ./fuse

Please wait while JBoss Fuse is loading...

100% [========================================================================]

      _ ____                  ______

     | |  _ \                |  ____|             

     | | |_) | ___  ___ ___  | |__ _   _ ___  ___

 _   | |  _ < / _ \/ __/ __| |  __| | | / __|/ _ \

| |__| | |_) | (_) \__ \__ \ | |  | |_| \__ \  __/

 \____/|____/ \___/|___/___/ |_|   \__,_|___/\___|

  JBoss Fuse (6.1.0.redhat-379)

  http://www.redhat.com/products/jbossenterprisemiddleware/fuse/

Hit '<tab>' for a list of available commands

and '[cmd] --help' for help on a specific command.

Open a browser to http://localhost:8181 to access the management console

Create a new Fabric via 'fabric:create'

or join an existing Fabric via 'fabric:join [someUrls]'

Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown JBoss Fuse.

No user found in etc/users.properties. Please use the 'esb:create-admin-user'

command to create one.

JBossFuse:karaf@root> 

Installation Success 

 

Now your JBoss Fuse Started and ready for your service. You can now configure and deploy any supportive service. Now test your JBoss Fuse is running from browser as below screenshots.

Open your browser with this published link http://localhost:8181

Remember, if this page is showing it means your JBoss Fuse is running.Now you need the login to access the management console. So, you need to create the fabric as instructed in the command. Here I have used the default admin/admin username and password. You need to un-comment the username and password line inside /etc/ user properties.

After login successful the below screens :- 

Welcome Page 

Dashboard

ActiveMQ : This need proper configuration and its not in this scope.

Really there are so many other useful and supportive implementation are there, which will really helpful if you are really looking a SOA play station :) Will keep posting with useful examples and configuration for your help.

Top 5 Oracle Service Bus (OSB) Fundamental Interview Questions

Q1. What is OSB and why do we need OSB?

Ans – In simple terms, it is a middleware tool provided by Oracle. It stands for Oracle Service Bus. It is used to deliver low-cost, standards-based integration for mission-critical SOA environments where performance and scalability are important. It simply helps to transform a complex architecture into a simple one by connecting different applications and services.

Q2. What is Proxy Service?

Ans - A proxy service is a service which you can expose to the outside world. Instead of publishing the actual service to the real world, we can publish the proxy service with additional/optimized business logic.

A proxy service can call any other proxy service (PS), local proxy service (LPS), and business service (BS). It is often called over the HTTP protocol.

Q3. What is Business Service?

Ans – A business service represents the configuration required to connect to an external or backend service. It can use a WSDL or other service definitions, depending on the type of service.

A business service is normally not called directly from the outside world. It is generally called by a proxy service. It directly communicates with the backend/business application.

Q4. What is Local Proxy Service?

Ans – A local proxy service is treated as an internal service. It is not exposed to the outside world. It is normally used for internal processing, validation, or common business logic, and it is used internally between proxy services, local proxy services, and business services.

It is called over the "local" protocol. They do not have an endpoint which a consumer sitting outside the OSB can invoke.

In order to invoke an internal proxy service, the consumer will have to invoke an external proxy service, which in turn will route it to the internal service.

Q5. What is VETO pattern?

Ans – VETO stands for Validation, Enrich, Transform and Operate. A commonly used approach in ESB/OSB is the VETO pattern.

The "Validate" step is usually the first part of an ESB process. It checks whether the incoming message meets the required conditions. Validation can be performed at different layers depending on the integration design.

The "Enrich" step involves adding additional data to a message to make it more meaningful and useful to a target service or application.

The "Transform" step converts the message to a target format.

The "Operate" step is the invocation of the target service or an interaction with the target application.

You can share your interview experience with the questions and answers asked in interviews for publishing on this blog.