To deploy a project into a container, you must either have already started the container using its command shell, or you must start it up from inside the JBoss Fuse Tooling (for details, see Managing servers.
Table of Contents
The Deploy to... tool () makes deploying applications into containers a one step
process.
The tooling supports direct deployment into the following containers:
Red Hat JBoss Fuse
Apache ServiceMix
Apache Karaf
You can deploy Fuse projects into a container three ways:
via a container's deploy folder
You copy the package generated by the tooling into the container's deploy folder. This method has two drawbacks, as the tooling does not:
verify that the project builds a package that is compatible with the target container
provide feedback as to whether the deployment succeeds or fails
via a JMX connected container
The tooling builds the project, and, regardless of the packaging specified in the project's POM, installs the generated artifacts as a bundle. You can use Fabric Explorer to determine whether the project deploys successfully.
via a fabric profile
The tooling builds 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.
![]() | Important |
---|---|
If 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 Fabric Explorer, or onto a fabric profile in Fabric Explorer. |