Page History

...

This is just an example of one way to deploy components. The preferred method is in the next section, however, the deployment tool
is still under development, so this section is included for the interim.

First some background. A JBI component is either a service engine (SE) or a binding component (BC). These terms are defined in #Introduction to ESB and/or the #Glossary. A BC/SE is installed on ServiceMix by copying it into the {{install}] directory which resides under the ServiceMix home directory. So what gets deployed? JBI components can act as containers themselves. Artifacts can be deployed to an existing BC or SE to add more functionality to that component. Adding artifacts to installed components is called deployment.

Let's use one of the existing examples and modify it to make it a deployment unit.
The quartz example is a good one. 
For a source distribution"
  cd \[servicemix_install_dir\]\assembly\target\servicemix-2.0.2\bin\servicemix-2.0.2\examples\quartz-binding
  create a directory elsewhere, such as \temp\JBIcomponent
  copy servicemix.xml to \temp\JBIcomponent
  cd \temp\JBIcomponent
  edit servicemix.xml
    -- need to change a few things to make this a service unit

...