
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