View Source

The container configuration is located into the file {{server.properties}} and expressed as property (key/value):
|| Parameter/Property name || Default value || Description ||
| {{petals.container.name}} | \- | Name of the container. *MUST* match a container name defined in the topology. |
| {{petals.classloaders.isolated}} | {{true}} | If {{true}}, the classloaders of JBI components are fully isolated, ie. they have the system classloader parent instead of the container classloader. If {{false}}, the container classloader is the parent of the classloaders of JBI components. |
|| Topology || || ||
| {{petals.topology.url}} | 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. | URL of the [topology definition|Topology Configuration]. |
| {{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. |
|| 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 |

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"] |