|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page History...
{column}
The ZIP archive comes with elementary startup and stop mechanisms. No automatic startup is provided. It supports several Petals ESB registry 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}
...
{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
cdeneux@sph-latitude-D630:~/petals-registry/bin/petals-registry.sh -c file://$PETALS_REGISTRY_HOME/conf/member.properties
...
{info}
Change the URL given with the argument {{-c}} to launch another Petals ESB Hazelcast Registry node.
{info}
...
{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
cdeneux@sph-latitude-D630:~/petals-registry/bin/petals-registry.sh -c file://$PETALS_REGISTRY_HOME/conf/member.properties stop
...