Introduction The Petals ESB "Shared Area", more generally called "Registry", is an internal component in charge of 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 all data that must be shared by all Petals ESB containers: endpoint name, service name, interface name, topology. The implementation of Petals ESB "Shared Area" must be the same for all nodes of a domain.

Table of contents 1 Introduction 2 Implementations 3 Installation 4 Configuration 4.1 Configuration parameter 4.2 Logging configuration parameters Contributors No contributors found for: authors on selected page(s)

Implementations

Several implementation exist for the Petals ESB "Shared Area". According to your use-case, select the right one:

Installation

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

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.

Petals.Communication.SharedArea.level=FINE