The main goal of the DSB management is to hide all the JBI complexity by wrapping and provided some JBI independant APIs and solutions. In order to achieve this, some hacks have been performed on the DSB side and are explained in the new sections.

In the next sections we will refer to the DSB distribution folder with the $DSB_HOME variable even if it is not set in the system environment.

Components

Startup

We assume that we do not need to deal with JBI components and let the Service Bus manage them. To achieve this, we introduced an artifact repository where JBI artefacts are stored on the Service Bus side. This artefact repository is available under $DSB_HOME/artifacts/ and is splited into 3 parts : components, sa and sl.

The components available under $DSB_HOME/artifacts/components can be automatically started at DSB startup by filling the embedded.component.list property in $DSB_HOME/conf/dsb.cfg. For example, if the dsb.cfg file is filled like :

and if the SOAP and REST components are available in the components folder, they will be started automatically when the container starts (no more JBI lifecycle management).

Configuration

Web Service

The DSB can be managed from remote clients using the Web Service API. The initial goal of the Web service API is to hide the JBI layer which is not Internet-friendly (even if some JBI aspects are used and will be explained in this section). This section gives details on how to use the Web service client library.

Deploy a Service Assembly

A JBI Service Assembly (SA) can be uploaded to the DSB artefact repository (a folder in the default implementation). Once the SA is uploaded, one can call the SA lifecycle operations on the uploaded SA.

A code sample is available at (http://chamerling.org/2010/04/12/librairie-cliente-pour-petals-esb/)