You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This page introduces JBI components and shows how to install them in ServiceMix

Components

Before you can start building your own integration application (also known as service assemblies), you need to add support to the JBI container for the types of transports and services you will be building. You can do this by installing additional components on the JBI container. The components come in two flavors:

  • Binding Components provide additional transports to the container.
    An example: the servicemix-http binding component allows to send messages into the ESB using HTTP
  • Service Engines add support for another type of business logic to the container.
    An example: the servicemix-saxon service engine allows you to easily build applications that do XSL-T transformations

Installing components

Out-of-the-box, ServiceMix has a lot of components readily available for you to use. You can find them in <servicemix_home>/components.

In order to install a component, you have to copy it to <servicemix_home>/install (this is the hot-install directory for components: whenever you drop a component installer archive in there, it will be automatically extracted and installed on the container).

For our next example, we want to use:

  • servicemix-shared: a shared libary by all ServiceMix JBI components
  • servicemix-http: binding component to provide the HTTP/SOAP transport
  • servicemix-jsr181: service engine which adds support for building JSR-181 compliant web services within ServiceMix

Install the required components now. After you have copied all 3 archives into the install directory, your console should look like this.

Things to remember

  • JBI Components (Binding Components and Service Engines) are plug-ins that add features to the JBI Container
  • You can install a JBI Component by copying it to <servicemix_home>/install
  • No labels