Petals ESB "Shared Area"


The Petals ESB "Shared Area" is an internal component storing internal data. The Petals ESB "Shared Area" can be viewed as a database shared by all Petals ESB nodes of a given Petals topology.

For example, before sending a message to a service provider, the Petals ESB "Router" will request the Petals ESB "Shared Area" for the right endpoint according to the information in the message (interface name and/or service name and/or endpoint name).

Data stored in the area are:

  • endpoint name,
  • service name,
  • interface name,
  • topology.
The implementation of Petals ESB "Shared Area" must be the same for all nodes of a domain.
No contributors found for: authors on selected page(s)


A default implementation of the Petals ESB "Shared Area" is provided with the archive of Petals ESB. No extra installation is required.
To install another Petals Shared Area implementation, just put its JAR files in a sub-directory of $PETALS_HOME/lib/implementations/registry.


Configuration parameter

The Petals ESB "Shared Area" implementation selection process is:

  1. if an implementation is set in the topology definition (topology/domain/registry-implementation), it is used,
  2. otherwise, the implementation used is the one available in the Petals ESB classpath.

See the documentation of the Petals ESB "Shared Area" implementations for other configuration parameters.

Logging configuration parameters

The Petals ESB "Shared Area" uses the following logger to trace its execution: Petals.Communication.SharedArea.



Only one implementation exists for the Petals ESB "Shared Area":

Petals ESB Shared Area implementation name Default implementation ?
the Petals ESB Hazelcast Registry Yes
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.