Installing JBoss Fuse on JBoss EAP and WildFly

In this article we will learn about the JBoss Fuse 6.2.1 server release, and how you can use it to provision both JEE applications and OSGi bundles

In the release of JBoss Fuse 6.2.1, you can now choose between two alternative container technologies:

• JEE (JBoss EAP)
• OSGi (Apache Karaf)

Both container types now offer a very similar technology stack (SwitchYard, Apache Camel, Apache CXF, and so on), so you can choose your preferred container type without limiting your options. You can download JBoss Fuse from the following link:

http://developers.redhat.com/products/fuse/download/

As you can see from this picture, two server releases are available:

The Installer which contains the Patch for installing the core libraries (SwitchYard, Apache Camel, Apache CXF, and so on) on EAP or WildFly

The Full Zip version which contains the Apache Karaf Container

The Apache Karaf Fuse Container is covered in this tutorial: JBoss Fuse Lesson 1: Helloworld Fuse .In this tutorial: so we will cover the Installer and we will show how to patch a Jboss EAP 6.4 installation.

Patching EAP 6 with JBoss Fuse 6.2.1

Place the fuse-eap-installer-6.2.1.redhat-084.jar in the JBOSS_HOME then execute:

$ java -jar fuse-eap-installer-6.2.1.redhat-084.jar

The patch procedure will start. At the end, when the procedure completes, you will be logged with:

12:26:31,209 INFO  [org.wildfly.extras.patch.internal.WildFlyServer] Installed fuse-eap-distro-6.2.1.redhat-084

What happened to my EAP ?

In practice, the configuration files have been backed-up. New configuration files have been created, including the required extensions and subsystems:

<extension module="org.wildfly.extension.camel" />
<extension module="org.switchyard" />

Besides it, the hawtio console will be installed as well on your distribution.

Start the application server as usual:

./standalone.sh

and reach the hawtio console:

http://localhost:8080/hawtio/

Now you have your SOA enabled EAP. You can verify the new features by activating the, for example by adding a Camel route definition in it:

        <subsystem xmlns="urn:jboss:domain:camel:1.0">
          <!-- You can add static camelContext definitions here. -->
         
             <camelContext id="system-context-1">
               <![CDATA[
               <route>
                 <from uri="direct:start"/>
                 <transform>
                   <simple>Hello #{body}</simple>
                 </transform>
               </route>
               ]]>
             </camelContext>
          
        </subsystem>

As you can see, the Camel feature is now activated on the hatwio console:

The fusepatch command can be used to patch also different server releases, like wildfly for example:

./fusepatch.sh --server /home/jboss/wildfly-10.0.0.Final --update fuse-patch-distro-wildfly

Found the article helpful? if so please follow us on Socials