Table of Contents
The developer tools' Deploy to... tool() 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 folder
You 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 container
The 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 profile
The 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.
![]() | 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 Fuse JMX Navigator, or onto a fabric profile in Fabric Explorer. |