E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History
...
{section} 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 registry area are:
* endpoint name,
* service name,
* service name,
...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 Registry Shared Area implementation, just put its JAR files in a sub-directory of {{$PETALS_HOME/lib/implementations/registry}}.
{anchor:Configuration}
...h2. Configuration parameter
The Petals ESB "Registry" "Shared Area" 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.
# otherwise, the implementation used is the one available in the Petals ESB classpath.
...h1. Implementations
Only one implementation exists for the Petals ESB "Registry": "Shared Area":
|| Petals ESB Shared Area implementation name || Default implementation ? ||
| the [Petals ESB Hazelcast Registry] | Yes |
| the [Petals ESB Hazelcast Registry] | Yes |