h2. Configuration files

The Distributed Service Bus is based on and uses Petals ESB configuration files for standard features such as server name, topology, loggers. Details on these files can be found in the Petals ESB documentation. Additionally, there are also some new configuration files which have been introduced for specific DSB purposes under the _$DSB_HOME/conf_ folder :
* *dsb.cfg*: The main configuration file containing the required configuration values for the Distributed Service Bus (more details below).
* *components.cfg*: The components to start when the DSB starts (more details in the [DSB Management section|petalsdsb:DSB Management]).
* *services2bind.cfg*: A list of external services to bind at startup (more details in the [DSB Management section|petalsdsb:DSB Management]).
* *wsdm.cfg*: Monitoring configuration (more details in the [DSB Monitoring section|petalsdsb:DSB Monitoring]).
* *federation.cfg*: Federation configuration (more details in the DSB Federation section).
* *launcher.cfg*: Launcher configuration (details below).

h2. Launcher configuration

In order to be able to create custom DSB distributions, the launcher.cfg file contains some parameters to modify if needed.
{code:language=none|title=launcher.cfg|linenumbers=true|theme=Confluence}# The distribution name
name=PetalsLink Distributed Service Bus

# The distribution URL
url=http://dsb.petalslinklabs.org

# The contact mail
mail=chamerling@petalslink.com

#Kernel JARs as CSV. Contains the DSB kernel JAR and its extensions
jars=dsb-kernel,soa4all-petals-federationtransporter,dsb-monitoring

# The main class of the DSB kernel. This is the class which instanciate DSB
class=org.petalslink.dsb.kernel.PetalsServerImpl{code}Here are the parameters descriptions:
* 'name' is just a name displayed in the terminal at startup.
* 'url' is an URL displayed in the terminal at startup.
* 'mail' is the contact email for this distribution displayed in the terminal at startup
* 'jars' is a list as CSV which is used to add some libraries in the container classpath. This is quite useful when you extend the DSB and when you need to add dependencies. There is no need to define any version number but just the beginning of the dependency name, the DSB will do the rest.
* 'class' is the main class to be started by the launcher, this class will load all the architecture components. This predefined class should work in most cases.

h2. Main configuration

The _$DSB_HOME/conf/dsb.cfg_ defines parameters for the default DSB kernel:
{code:title=dsb.cfg|linenumbers=true|theme=Confluence}# Embedded Web application port
webapp.port=8080

# The mappping between protocols and components
mapping.soap=petals-bc-soap
mapping.rest=petals-bc-rest

# list of component (CSV) to be installed and started after kernel is started
embedded.component.list=petals-bc-soap,petals-bc-rest,petals-bc-soap-proxy

# poll for new endpoints period
endpoints.polling.period=120

# delay
endpoints.polling.delay=120

#Remote transport definition (optional)