h1. Introduction

Petals ESB Hazelcast Registry client is the default registry implementation for distributed topology, based on the [Petals ESB Hazelcast Registry|Petals Registry Overlay user guide]

{anchor:Configuration}
h1. Configuration

h2. Topology parameters

The configuration parameters of the Petals ESB Hazelcast Registry client that must be shared by all containers of the domain are available in the [topology definition|Topology Configuration]:
{code}
<tns:domain name="Domain" mode="static" xmlns:tns="http://petals.ow2.org/topology">
...
<tns:registry-implementation>org.ow2.petals.microkernel.registry.overlay.RegistryOverlayImpl</tns:registry-implementation>
...
<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>
</registry:overlay-members>
</registry:configuration>
</tns:domain>
{code}

|| Parameter name || Default value || Description ||
| {{configuration/group-name}} | - | Group name of the cluster. Must be unique for this domain. |
| {{configuration/group-password}} | - | Password used to secure access to the group. |
| {{configuration/overlay-members}} | - | List of the cluster members that the containers member of the current domain can join. |
| {{configuration/overlay-members/overlay-member}} | - | Host name of the cluster member. |
| {{configuration/overlay-members/overlay-member@port}} | {{7901}} | Listening port of the cluster member. |
where the namespace of parameters is: {{http://petals.ow2.org/petals-registry-overlay-client/configuration}}.

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 Petals ESB Hazelcast Registry client,
* *{{com.hazelcast}}*: the low-level client part based on Hazelcast stack.

As the Petals ESB Hazelcast Registry client 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}