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).
• services2bind.cfg: A list of external services to bind at startup (more details in the DSB Management section).
• wsdm.cfg: Monitoring configuration (more details in the DSB Monitoring section).
• federation.cfg: Federation configuration (more details in the DSB Federation section).
• launcher.cfg: Launcher configuration (details below).

Launcher configuration

In order to be able to create custom DSB distributions, the launcher.cfg file contains some parameters to modify if needed.

• '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.

Main configuration

The $DSB_HOME/conf/dsb.cfg defines parameters for the default DSB kernel:

Some explanations:

• 'webapp.port': There is a webapp hosted by the DSB itself. It is used to display some standard information from your browser.
• The 'mapping.xxx' parameters are used to link protocols to binding components. For example, in the snippet above, it means that the petals-bc-soap component is bound to the soap protocol. This link will be used in other configuration files (services2bind.cfg for example).
• 'embedded.component.list' is the list (CSV) of components to be started when the DSB starts. These components must be available in the artifacts folder under $DSB_HOME/artifacts/components/
• 'endpoint.polling.period' is a period in seconds. This is used to poll for new endpoints and to automatically expose them as services with the help of installed binding components (this is because the current registry does not provide a listener mechanism on new endpoint retrieval). 'endpoint.polling.delay' is the delay to start polling new endpoints.
• 'remote.transport' is the default transport to be used. Default is already set to SOAP/HTTP for standard DSB distribution. You can just override this default with that parameter. It is highly linked on the Fractal configuration so it is mainly for advanced users.