h1. Introduction

Petals ESB Hazelcast Registry is the default registry implementation, based on the [Petals Registry Overlay]

{anchor:Configuration}
h1. Configuration

...
<registry:configuration xmlns:registry="http://petals.ow2.org/petals-registry-overlay-client/configuration">
<registry:group-name>default-sample</registry:group-name>
<registry:group-password>s3cr3t</registry:group-password>
<registry:overlay-members>
<registry:overlay-member port="7901">localhost</registry:overlay-member>

where the namespace of parameters is: {{http://petals.ow2.org/petals-registry-overlay-client/configuration}}.

h2. Runtime configuration parameters

Some configuration parameters of the Petals ESB Hazelcast Registry are available into the container local configuration (ie. into the file {{server.properties}}:
|| Parameter/Property name || Default value || Description ||
| {{org.ow2.petals.microkernel.registry.overlay.RegistryOverlayImpl.map-cache.max-size}} | {{500}} | Max size, in endpoint number, of the cache associated to each map of the registry overlay client implementation. |

h2. Logging configuration parameters

The Petals ESB Hazelcast Registry uses the following loggers to trace its execution:
* *{{Petals.System.Registry}}*: associated to the Petals ESB internal component associated to the registry client,
* *{{com.hazelcast}}*: the low-level client part based on Hazelcast stack.

As the Petals ESB Hazelcast Registry is provided as default into the ZIP and Debian archives of Petals ESB, its logging configuration is already configured as following:
{code}
Petals.System.Registry.level=INFO
com.hazelcast.level=WARNING
{code}