E-mail
Introduction
|
The container configuration is located into the file server.properties and expressed as property (key/value).
myserver.host=localhost
petals.topology.url=http://${myserver.host}/petals/${petals.container.name}/topology.xml
|
Contributors
No contributors found for: authors on selected page(s)
|
Configuration reference
ContainerConfigRef
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. |
| Directories | ||
| petals.data.basedir | see note 1 | 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. |
| General | ||
| 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. |
| petals.task.timeout | 120000 | The maximum duration, in milliseconds, of the processing of a life-cycle operation on a JBI components and SAs (start, stop, ...). It prevents from hanging threads. |
| petals.exchange.validation | false | Flag to activate the control of exchange acceptance by target component when the NMR routes messages (see isExchangeWithConsumerOkay and isExchangeWithProviderOkay methods in JBI Component interface. |
| Topology | ||
| petals.topology.url | topology.xml2 | URL of the topology definition. |
| 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. |
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.
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.
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" |
| petals.artifact... | Petals ESB "Artifact repository" |