{toc:outline=true}
The first goal of the DSB management is to hide all the JBI complexity by wrapping and provided some JBI independant APIs and solutions. Another important goal is to hide the kernel management originally based on JMX and to provide a Web service management API.

{info}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.{info}

h1. API

The management API is available in the _dsb-kernel-wsapi_ module. It allows to manage business services, but also to manage the DSB kernel : router, registry, monitoring, ... By default, the management API is exposed as Web services at DSB startup on [http://localhost:7600/petals/ws]. The complete list of available service is provided by the getWebService operation on the DSBInformationService service available at [http://localhost:7600/petals/ws/DSBInformationService] (complete list also available at [http://localhost:7600/petals/ws/DSBInformationService/getWebServices]).

h1. Features


h2. {color:#492562}{*}Components{*}{color}

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 :

{code}
# Components to start as CSV
embedded.component.list=petals-bc-soap,petals-bc-rest
{code}
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 for these components is needed).

{code}
petals-bc-soapproxy.port=8083
petals-bc-soap.port=8084
petals-bc-rest.port=8082
{code}

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

Some utilities based on top of the previously mentioned API are also available to preconfigure the DSB at configuration time. With their help you are able to define sets of services which will be automatically bound to the DSB when it starts.

# A list of services to bind at startup
# The key MUST start with the protocol to use to bind the service and MUST be unique in this properties file
# CSV Values are also possible

#soap.0=http://localhost:8080/services/Ping?wsdl
#soap.1=http://localhost:8080/services/Pong?wsdl
#rest.0=http://localhost:7777/rest/Weather

soap.proactivespace=http://ns306320.ovh.net:8090/soa4all-space-proactive/ws/ProactiveSemanticSpaceWS?wsdl
soap.owlimspace=http://94.23.221.97:8080/soa4all-space-owlim/ws/SemanticSpaceWS?wsdl
rest.yahooweather=http://weather.yahooapis.com/

#example of service list as CSV
soap.list=http://foo.com/bar,http://bar.com/foo
rest.list=
{code}

In the previous configuration snippet, 

h4. Runtime

In order to bind an external Web service, simply call the _bindWebService()_ operation of the _SOAPServiceBinder_ DSB service with the WSDL URL of the service to bind as parameter. As a result, a new endpoint will be created in the DSB and each time a message is received on this DSB endpoint, it will be forwarded to the real Web service (the one you bound).
{info}TODO : Example with WSDL and resulting endpoints{info}