Table 2.1 lists the available installation files for Fuse ESB.
Table 2.1. Installer Files
| File | Description |
|---|---|
apache-servicemix-4.4.1-fuse-00-08.zip | Binary installation package for Windows platforms. |
apache-servicemix-4.4.1-fuse-00-08.tar.gz | Binary installation package for Linux, OS X, and all UNIX platforms. |
apache-servicemix-4.4.1-fuse-00-08-src.zip | Source code installation package for all platforms. If you prefer to build Fuse ESB from source, see Installing from Source Code. |
The binary distribution is packaged either as a .zip file (Windows)
or a .tar.gz file (*NIX). Using a suitable archive tool, such as Zip or Gunzip,
unpack the distribution into a directory to which you have full access.
![[Warning]](imagesdb/warning.gif) | Warning |
|---|---|
Do not unpack the archive file into a folder that has spaces in its path name. For
example, do not unpack into |
After unpacking the distribution and checking the prerequisites, you are now ready to use the product. See Product Introduction for more details.
The JBI container is installed as a sub-container of the OSGi container in Fuse ESB. If you do not intend to use the JBI container, however, you might prefer to remove it from the OSGi container altogether. To remove the JBI container, perform the following steps:
You need to perform a cold start of the OSGi container. That is, you must completely wipe the data stored by the current instance of the container. While the container is shut down, delete the entire
EsbInstallDir/datadatadirectory might not exist, if you have not yet run the OSGi container).Edit the
etc/org.apache.karaf.features.cfgfile to customize the list of features installed during a cold start. In thefeaturesBootsetting, delete all of the entries in the comma-separated list that match the patternsjbi-*orservicemix-*. For example, after deleting the relevant entries from the default list, thefeaturesBootsetting would look as follows:# # Comma separated list of features to install at startup # featuresBoot=config,activemq-broker,camel,war
The next time you start up the OSGi container, it initializes itself without the JBI features.
 |  | |
 |
