h1. Introduction

{section}
{column}

The container configuration is located into the file {{server.properties}} and expressed as property (key/value).
A property value can be set using the value of another property as a variable using a placeholder mechanism, and you can add your own properties:
{code}
myserver.host=localhost
petals.topology.url=http://${myserver.host}/petals/${petals.container.name}/topology.xml
{code}

{column}
{column:width=35%}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}

h1. Configuration reference

h2. Container configuration reference

|| Parameter/Property name || Default value || Description ||
| {{petals.container.name}} | \- | Name of the container. *MUST* match a container name defined in the [topology|Topology Configuration]. |
|| Directories || || ||
| {{petals.data.basedir}} | see [note 1|#default_value_data_basedir] | The root directory where the Petals ESB container will write its data |
| {{petals.repository.path}} | {{$\{petals.data.basedir}/repository}} | The absolute path of the Petals working area. |
| {{petals.work.path}} | {{$\{petals.data.basedir}/work}} | The absolute path of the Petals repository in which it holds its JBI configuration and can recover this configuration from it. |

| {{petals.topology.passphrase}} | {{petals}} | Pass-phrase used as security to get sensible information of other Petals nodes of the topology as JMX credentials from this node. |
|| Router || || ||
| {{petals.router.strategy}} | {{highest,3,2,1}} | The strategy of the router. |
| {{petals.router.send.attempt}} | {{2}} | Defines the number of attempt to send a message to an endpoint. Several attempts can be done when there is transport failure during the convey of a message. |
| {{petals.router.send.delay}} | {{1000}} | The delay, in milliseconds, between the send attempts. |
|| Transporter || || ||
| {{petals.transport.queue.max-size}} | {{10000}} | Queue size, in message number, of the message exchange transporter. If the queue is full, new message exchange can rejected. |
| {{petals.transport.queue.offering.timeout}} | {{2500}} | How long to wait, in milliseconds, to put the message exchange in the queue before to reject it. |
|| Remote Transporter || || ||
| {{petals.transport.tcp.receivers}} | {{10}} | The number of messages that can be received by the remote transporter at the same time. |
| {{petals.transport.tcp.senders}} | {{10}} | The number of messages that can be sent by the remote transporter at the same time, per JBI component. |
| {{petals.transport.tcp.connection.timeout}} | {{5000}} | The timeout, in milliseconds, to establish a connection to a remote Petals node, for a sender. |
| {{petals.transport.tcp.send.timeout}} | {{5000}} | The timeout, in milliseconds, to send a TCP packet to a remote Petals node, for a sender. |
| {{petals.transport.tcp.send.evictor.delay}} | {{60000}} | The delay, in milliseconds, before running the eviction thread removing unused message exchange senders. |
| {{petals.transport.tcp.send.evictable.delay}} | {{60000}} | The delay, in milliseconds, before an idle 'message exchange sender' is set evictable. |
|| Persistence Service || || ||
| {{petals.persistence.duration}} | {{3600000}} | The duration, in milliseconds, of temporary persisted data, such as Message Exchange. |
| {{petals.persistence.fetch-size}} | {{10}} | The persistence SQL request fetch size, in rows. |

{anchor:default_value_data_basedir}+Note 1:+ If the container configuration, ie. {{server.properties}}, is defined by a file-based URL, the default value is the directory '{{data}}' contained in the parent directory of the directory containing the file 'server.properties'. Otherwise, no default value is defined and a value *MUST* be provided.

{anchor:default_value_topology_xml}+Note 2:+ If the container configuration, ie. {{server.properties}}, is defined by a file-based URL, the default value is {{topology.xml}} in the same directory than the container configuration. Otherwise, no default value is defined and a value *MUST* be provided.

h2. Extensions configuration

Other parameters associated to Petals ESB extensions can be found in the file {{server.properties}}:
|| Property name pattern || Extension ||
| {{petals.autoloader.*}} | [Petals ESB "Autoloader"] |
| {color:red}{{petals.artifact...}} | [Petals ESB "Artifact repository"] |