E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (10)
View Page History
...
{section} h1. Introduction
The Petals ESB "Registry" is an internal component storing internal data. The Petals ESB "Registry" can be view as a distributed in-memory database shared by all Petals ESB nodes of the Petals network.
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|Topology Configuration].
For example, before to send sending a message to a service provider, the Petals ESB "Router" will request the Petals ESB "Registry" to elect "Shared Area" for the right endpoint according to the information of in the message (interface name and/or service name and/or endpoint name).
Data stored in the registry are:
...* topology.
{note}The implementation of Petals ESB "Registry" "Shared Area" must be the same for all nodes of a domain.{note}
{column}
...h1. Installation
A default implementation of the Petals ESB "Registry" "Shared Area" is provided with the archive of Petals ESB. No extra installation is required.
To install another Petals Registry implementation, just put its JAR files in a sub-directory of {{$PETALS_HOME/lib/implementations/registry}}.
...The Petals ESB "Registry" implementation selection process is:
# if an implementation is set in the [topology definition|Topology Configuration] ({{topology/domain/registry-implementation}}), it is used,
# otherwise, the implementation used is the one available in the Petals ESB classpath.
See the documentation of the Petals ESB "Registry" implementation "Shared Area" implementations for other configuration parameters.
h2. Logging configuration parameters
The Petals ESB Artifact Repository "Shared Area" uses the following logger to trace its execution: {{Petals.JBI-Messaging.EndpointRegistry}}. {{Petals.Communication.SharedArea}}.
{code}
Petals.JBI-Messaging.EndpointRegistry.level=FINE Petals.Communication.SharedArea.level=FINE
{code}
...Only one implementation exists for the Petals ESB "Registry":
|| Petals ESB registry Shared Area implementation name || Default implementation ? ||
| the [Petals ESB Hazelcast Registry] | Yes |