Red Hat SummitFuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Chapter 8. Deploying Projects to a Container
| Revision History | ||
|---|---|---|
| 8/11/11 | EMJ | |
| made a chapter with sections to include container config | ||
| 7/13/12 | EMJ | |
| rewrote for clarity and accuracy | ||
| 7/13/12 | EMJ | |
| merged configuration of hot deploy folder and hot deploy procedure into a single section | ||
The developer tools' Deploy to... tool(
) makes deploying applications into containers a one step process.
) makes deploying applications into containers a one step process.
The developer tools support direct deployment into the following containers:
- Red Hat JBoss Fuse
- Apache ServiceMix
- Apache Karaf
There are three ways to deploy Fuse projects into a container:
- into a container's deploy folderYou copy the package generated by the developer tools into the container's deploy folder. This method has two drawbacks:
- The developer tools do not verify that the project builds a package that is compatible with the target container.
- The developer tools do not provide feedback as to whether the deployment succeeds or fails.
- to a JMX connected containerThe developer tools build the project, and, regardless of the packaging specified in the project's POM, installs the generated artifacts as a bundle. You can use the Fuse JMX Navigator to determine if the project deploys successfully.
- to a fabric profileThe developer tools build the project, packages the generated artifacts into a bundle, adds the bundle to the profile, and copies the bundle into the fabric's internal repository.ImportantIf the profile is not assigned to a running container the project will not be deployed into the fabric. You must assign the profile to a running container before you can see the project running.
Note
You can deploy a project by dropping it onto a connected container in Fuse JMX Navigator, or onto a fabric profile in Fabric Navigator.
8.1. Using a Container's Deploy Folder
Copy linkLink copied to clipboard!
When the developer tools deploy a project into a container's deploy folder, they build the project as specified in the project's POM and copies the resulting package to a predetermined location. The developer tools assume two things:
- the specified location is a container's deploy folder
- the package generated by the project is compatible with the container
Before you can deploy a project to a container's deploy folder you must add the container's deployment information to the developer tools. Once the developer tools know the container's information, the container will appear as an option in the menu.
8.1.1. Configuring a Container's Deploy Folder
Copy linkLink copied to clipboard!
| Revision History | ||
|---|---|---|
| 7/22/11 | EMJ | |
| Added info about opening the container preferences | ||
| 7/13/12 | EMJ | |
| changed deployment folder to deploy folder so it is consistent with the UI | ||
| 7/13/12 | EMJ | |
| edited for clarity | ||
Overview
Copy linkLink copied to clipboard!
Before you can deploy applications into a container's deploy folder, you must provide the developer tools with the location of the container's deploy folder. The Deploy Folders preference panel enables you to configure one or more containers. You provide a name for the container and the full path to the container's deployment folder.
Accessing the Deploy Folder preference panel
Copy linkLink copied to clipboard!
You can access the deployment folders preference panel two ways:
- selecting
from the main menu This method opens the general Eclipse preference window. You need to select from the list of preferences in the panel on the left side of the widow. - selecting
from the project's context menu This method opens the preferences window and ensures that the Deploy Folders panel is selected.
Add a container's deploy folder
Copy linkLink copied to clipboard!
To add a container's deploy folder:
- Open the Deploy Folder preference panel.
- In the Name field, enter a name for the target container.The name can be any unique string.
- In the Deploy Folder field, enter the full path to the container's deployment folder.The
button opens a file explorer.
ImportantThe developer tools do not validate whether the selected folder is a valid deployment folder for a container. - In the Description field, enter a description for the container.
- Click to add the new container to the table of configured containers.
- Click to close the preferences window.
When add a container to the list, it appears in the context menus'
Deploy to... submenu.
Deploy to... submenu.
Edit a container's deploy folder
Copy linkLink copied to clipboard!
To edit a container's deploy folder:
- Open the Deploy Folder preference panel.
- Select the container whose configuration you want to edit.
- Edit the information that needs updating.ImportantChanging the value of the Name field creates a new container configuration.
- Click
.
- Click to close the preferences window.
Delete a container's deploy folder
Copy linkLink copied to clipboard!
To delete a container's deploy folder:
- Open the Deploy Folder preference panel.
- Select the container to be deleted.
- Click
.
- Click to close the preferences window.
Related topics
Copy linkLink copied to clipboard!
| Chapter 8, Deploying Projects to a Container |
| Deploy Folders |
8.1.2. Deploying a Project to a Container's Deploy Folder
Copy linkLink copied to clipboard!
| Revision History | ||
|---|---|---|
| 8/11/11 | EMJ | |
| Split into a section | ||
Overview
Copy linkLink copied to clipboard!
When the developer tools deploy a project to a container's deploy folder it builds the project and copies the results to the deploy folder configured for the container.
Procedure
Copy linkLink copied to clipboard!
To deploy a project to a container's deploy folder:
- Select the routing context file that you want to deploy.ImportantThe project must be configured to package the results in a format that the target container can deploy.
- Select
Deploy to...
from the project's context menu. Red Hat JBoss Fuse Plugins for Eclipse builds the project and copies the results to the selected container's deploy folder.NoteIf you have not already configured a container, you can do so by selecting
Deploy to... from the context menu. - Check the Console view to see if your project was successfully built and copied to the target container.
- Check the container's log files to see if the project was successfully deployed.
Related topics
Copy linkLink copied to clipboard!
| Section 8.1.1, “Configuring a Container's Deploy Folder” |
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}