Petals Documentation > Petals ESB > Petals ESB 5.3.0 > Page Comparison - Petals ESB Hazelcast Registry (v.8 vs v.9)

Petals ESB Hazelcast Registry

Version 8 by Christophe DENEUX
on Oct 05, 2018 16:21.
<< Changes from 7 to 8
compared with
Version 9 by Christophe DENEUX
on Oct 05, 2018 16:29.
Changes from 9 to 10 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (7)

View Page History
h1. Introduction

Petals ESB Hazelcast Registry is the default registry implementation, based on the [Petals Registry Overlay|Petals Registry Overlay user guide]
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}
...
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">
...
h2. Runtime configuration parameters

Some configuration parameters of the Petals ESB Hazelcast Registry client 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. Petals ESB Hazelcast Registry client. |

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 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
...