{section}
{column}

These Debian packages can be downloaded on [Petals' website|http://petals.ow2.org].

h1. Installing Petals ESB Registry

Nowadays, no public repository exists containing the Debian packages of Petals ESB Registry. So to install yours, you must download them, next install them with your favorite Debian tools ({{synaptic}}, {{apt-get}}, {{dpkg}}).

Several Debian packages are available:
|| Package || Description || Depends on || Required for a production use ||
| {{petals-commons}} | The base package of all Petals products | {{base-files}} | required |
| {{petals-registry}} | The base package of Petals ESB to run a minimalist container | {{java7-runtime-headless}}, {{curl}} and {{petals-commons}} | required |

{column}
{column:width=35%}
{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. Uninstalling Petals ESB Registry

According to Debian policies, Petals ESB Registry packages can be uninstalled with or without purging configuration files, with your favorite Debian tools ({{synaptic}}, {{apt-get}}, {{dpkg}}).

In addition to the runtime files, the purge will remove following directories containing some configuration or working files:
* {{/etc/petals-registry/member-enable}}
* {{/var/lib/petals-registry}}
* {{/var/log/petals-registry}}
* {{/var/run/petals-registry}}

The dedicated Petals system user and group are also removed when purging packages. The Petals ESB Registry node configurations ({{/etc/petals-registry/member-available}}) are never removed except the sample one, to be reused eventually.

{tip}All Petals ESB Registry nodes declared into {{/etc/petals-registry/member-enable}} will be automatically stopped during the uninstallation process. If you have started manually other Petals ESB Registry nodes, you must stop them before to launch the uninstallation process.{tip}

h1. Upgrading Petals ESB Registry

To update the installed version of Petals ESB Registry:
* just uninstalled Petals ESB Registry packages without purging it:
{code}> sudo dpkg -r petals-registry ...{code}
* and installed new Petals ESB Registry packages.

{tip}All Petals ESB Registry nodes declared into {{/etc/petals-registry/member-enable}} will be automatically stopped during the uninstallation process and restarted during the installation process. If you have started manually other Petals ESB Registry nodes, you must stop them before to launch the uninstallation process, and restart them after the installation process.{tip}

h1. Content of the packages

h2. Content of the package "{{petals-registry}}"

This package arrives with following directories and files:
* {{/usr/bin/petals-registry}}: The script used to start a Petals ESB Registry node,
* {{/usr/bin/petals-registry.sh}}: A link to {{/usr/bin/petals-registry}},
* {{/usr/share/petals-registry}}: Directory containing all Java libraries required by Petals ESB Registry,
* {{/etc/init.d/petals-registry}}: Automatic startup/stop script
* {{/etc/petals-registry/member-available/<member-id>}}: A directory containing the configuration of a Petals ESB Registry node:
** {{member.properties}}: the base configuration of the Petals ESB Registry node,

* {{/usr/share/petals-registry/licenses}}: Directory containing license files.