{section}
{column}

h1. Introduction

The Petals ESB "Registry" is an internal component storing internal data. The Petals ESB "Registry" can be view as a distributed in-memory database shared by all Petals ESB nodes of the Petals network.

* service name,
* interface name,

{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}

h1. Installation

A default implementation of the Petals ESB "Registry" is provided with the archive of Petals ESB. No extra installation is required.

{anchor:Configuration}
h1. Configuration

h2. Configuration parameter

The Petals ESB "Registry" implementation selection process is:
# if an implementation is set in the topology definition ({{topology/domain/sub-domain/registry-implementation}}), it is used,
# otherwise, the implementation used is the one available in the Petals ESB classpath.

See the documentation of the Petals ESB "Registry" implementation for other configuration parameters.

h2. Logging configuration parameters

The Petals ESB Artifact Repository uses the following logger to trace its execution: {{Petals.JBI-Messaging.EndpointRegistry}}.

{code}
Petals.JBI-Messaging.EndpointRegistry.level=FINE
{code}