Show Table of Contents
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>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.