* *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)
#remote.transport=soap
#remote.transport=xmpp{code}
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.
...