
The Embedded Petals Registry Overlay provided with this extension is one configured with the following cluster definition:
{code:xml}
<tns:petals-registry-overlay xmlns:tns="http://petals.ow2.org/registry-overlay/configuration/1.0">
<tns:credentials>
<tns:group>default-sample</tns:group>
<tns:password>s3cr3t</tns:password>
</tns:credentials>
<tns:members>
<!-- Default listening port: 7900 -->
<tns:member id="sample-member-0">localhost</tns:member>
</tns:members>
<!-- By default, the support of the Hazelcast Management Center is enable -->
<!--tns:management-console enable="true">http://localhost:8080/mancenter</tns:management-console-->
</tns:petals-registry-overlay>
{code}
You can connect your Hazelcast Management console to this registry.
{anchor:Configuration}
h1. Configuration
h2. Runtime configuration parameters
Configuration parameters of the Embedded Petals Registry Overlay are available into the container local configuration (ie. into the file {{server.properties}}:
|| Parameter/Property name || Default value || Description ||
| {{petals.embedded-registry-overlay}} | {{true}} | Flag enabling/disabling the extension if the topology authorizes to use this extension |
| {{petals.embedded-registry-overlay.port}} | {{7900}} | The listening TCP port of the embedded registry |
h2. Logging configuration parameters
This extension uses the following logger name to trace its execution: {{Petals.Extensions.EmbeddedRegistryOverlayService}}.
As this extension is provided into the ZIP Archive of Petals ESB, its logging configuration is already configured. If you install this extension through Debian or RPM package, just add something like the following lines to your {{loggers.properties}}:
{code}
Petals.Extensions.EmbeddedRegistryOverlayService.level=FINEST
{code}