Table of Contents
![]() | Subscription Only |
|---|---|
This feature is available only to FuseSource subscribers. |
Available from the tool bar and from the project's context menu, the Deploy
to... tool(
) provides three methods for deploying your Apache Camel applications into
external containers:
Deploying into a container's hot deployment folder
First you to configure each container's hot deployment folder, and then select the one into which you want to deploy your application from the Deploy to... submenu.
Supported containers for hot deployment are:
Fuse ESB Enterprise
Apache ServiceMix
Apache Karaf
This method does not verify that the project builds a package compatible with the target container. You must ensure that your project's POM file is configured to package the route in a form that the target container can load. And Fuse IDE does not provide feedback as to whether the deployment succeeds or fails. You need to check the target container's logs to determine if the application deployed successfully.
Deploying a project to Fuse ESB Enterprise
To use this method, Fuse IDE must be connected to Fuse ESB Enterprise; otherwise it does not appear as a selection from the Deploy to... menu.
This method works with any Maven project. It builds the project, runs all tests, and installs the project as a bundle inside Fuse ESB Enterprise.
Deploying a project to a fabric profile that will provision target containers across a fabric
To use this method, Fuse IDE must be connected to the fabric; otherwise the fabric's profiles do not appear as selections from the Deploy to... menu.
This method works with any Maven project. It builds the project, runs all tests, installs the project as a bundle inside the profile, and copies the profile into the fabric's internal Maven repository.
![]() | Tip |
|---|---|
In Fuse Integration perspective, you can drag and drop a project onto a FuseESB container in JMX Explorer, or onto a fabric profile in Fabric Explorer. |