View Source

h1. Introduction

{section}
{column}

The ZIP archive comes with elementary startup and stop mechanisms. No automatic startup is provided. It supports several Petals ESB Hazelcast Registry nodes with only one installation.

{info}
In this chapter, we consider that the Petals ESB Hazelcast Registry ZIP archive was extracted in the directory {{$PETALS_REGISTRY_HOME}}.
{info}

{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. Starting Petals ESB Hazelcast Registry

To start the Petals ESB Hazelcast Registry node configured in {{$PETALS_REGISTRY_HOME}}/conf, go into the directory {{$PETALS_REGISTRY_HOME/bin}} and execute the following command from a command-line:
{code}
cdeneux@sph-latitude-D630:~/petals-registry/bin/petals-registry.sh -c file://$PETALS_REGISTRY_HOME/conf/member.properties
{code}

{info}
Change the URL given with the argument {{-c}} to launch another Petals ESB Hazelcast Registry node.
{info}

{info}
Use the script {{petals-registry.bat}} instead of {{petals-registry.sh}} for Windows-based system.
{info}

h1. Stopping Petals ESB Hazelcast Registry

To stop a Petals ESB Hazelcast Registry node, just kill it with a Ctrl-C on its console, or use the following command from another shell:
{code}
cdeneux@sph-latitude-D630:~/petals-registry/bin/petals-registry.sh -c file://$PETALS_REGISTRY_HOME/conf/member.properties stop
{code}

{info}
Use the script {{petals-registry.bat}} instead of {{petals-registry.sh}} for Windows-based system.
{info}