2.2. Getting Started with Camel on EAP Subsystem


Camel on EAP Subsystem provides you the capability to add Camel routes to your Java EE applications.

2.2.1. Running Camel on EAP Subsystem

Before running the subsystem, you need to check your system to make sure that you have a working Java 1.7 version and Maven 3.2.3 version or higher.
  • Standalone Server: Run the following command in your JBoss EAP home directory.
    $ bin/standalone.sh -c standalone-camel.xml
    
  • Domain Mode: Run the following command in your JBoss EAP home directory.
    $ bin/domain.sh -c domain-camel.xml
    

2.2.2. Enabling Camel on EAP Subsystem

The Camel on EAP distribution patch does not modify the existing JBoss EAP configuration files. However, it comes with a number of additional configuration files.
Run the following command to add the Camel subsystem to an existing configuration.
$ bin/fuseconfig.sh --configs=camel --enable

2.2.3. Disabling the Camel Subsystem

If you do not want to add camel subsystem into your deployment, set the attribute enabled to false. For example, In jboss-all.xml file, set the attribute enabled to false in jboss-camel XML element
<jboss umlns="urn:jboss:1.0">
<jboss-camel xmlns="urn:jboss:jboss-camel:1.0" enabled="false"/>
</jboss>

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.