{section}
{column}
h1. Installing Petals ESB Hazelcast Registry using the ZIP archive
Once the Petals ESB Hazelcast Registry ZIP archive is downloaded, extract all files into a directory of your choice.
When files are extracted, Petals ESB Hazelcast Registry is ready to be run. Go to "[Configuring Petals ESB Hazelcast Registry]" to configure your own Petals ESB Hazelcast Registry node.
{warning}Don't use a directory containing space as Petals ESB Hazelcast Registry home directory{warning}
{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 Hazelcast Registry
Removing the Petals ESB Hazelcast Registry home directory will uninstalled Petals ESB Hazelcast Registry.
{warning}If needed, you must backup your configuration files before removing the directory.{warning}
h1. Upgrading Petals ESB Hazelcast Registry
Before to upgrade your Petals ESB Hazelcast Registry installation, you must stop all Petals ESB Hazelcast Registry nodes running from the installation to update. Next, just extract files of the new ZIP archives into your Petals ESB Hazelcast Registry home directory. And restart your Petals ESB Hazelcast Registry nodes.
{info}If you have updated the sample configuration, it will be replaced by the new one. So don't forget to backup it if needed before to upgrade your Petals ESB Hazelcast Registry installation.{info}
h1. Content of the ZIP archive
The ZIP archive contains:
* a directory {{bin}} that contains the startup script and launcher of Petals ESB Hazelcast Registry,
* a directory {{lib}} where all libraries required by the core of Petals ESB Hazelcast Registry are put,
* a directory {{conf}} containing the *default* configuration of the Petals ESB Hazelcast Registry node,
* a directory {{logs}} that is the directory in which log files of the *default* node will be written.
{column}
h1. Installing Petals ESB Hazelcast Registry using the ZIP archive
Once the Petals ESB Hazelcast Registry ZIP archive is downloaded, extract all files into a directory of your choice.
When files are extracted, Petals ESB Hazelcast Registry is ready to be run. Go to "[Configuring Petals ESB Hazelcast Registry]" to configure your own Petals ESB Hazelcast Registry node.
{warning}Don't use a directory containing space as Petals ESB Hazelcast Registry home directory{warning}
{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 Hazelcast Registry
Removing the Petals ESB Hazelcast Registry home directory will uninstalled Petals ESB Hazelcast Registry.
{warning}If needed, you must backup your configuration files before removing the directory.{warning}
h1. Upgrading Petals ESB Hazelcast Registry
Before to upgrade your Petals ESB Hazelcast Registry installation, you must stop all Petals ESB Hazelcast Registry nodes running from the installation to update. Next, just extract files of the new ZIP archives into your Petals ESB Hazelcast Registry home directory. And restart your Petals ESB Hazelcast Registry nodes.
{info}If you have updated the sample configuration, it will be replaced by the new one. So don't forget to backup it if needed before to upgrade your Petals ESB Hazelcast Registry installation.{info}
h1. Content of the ZIP archive
The ZIP archive contains:
* a directory {{bin}} that contains the startup script and launcher of Petals ESB Hazelcast Registry,
* a directory {{lib}} where all libraries required by the core of Petals ESB Hazelcast Registry are put,
* a directory {{conf}} containing the *default* configuration of the Petals ESB Hazelcast Registry node,
* a directory {{logs}} that is the directory in which log files of the *default* node will be written.