View Source

{section}
{column}

h1. Starting Petals ESB

Petals ESB offers various startup modes :
* Non-interactive command line
* Interactive command line
* Daemon command line (available only under Unix based systems)

{note:title=Note}
In order to be able to start Petals ESB, under Linux or Windows, you must have defined a valid {{JAVA_HOME}} environment variable.
{note}

h2. Linux / MacOS X

*Non-interactive command line startup*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
./startup.sh
{noformat}
# Done :-)

\\
*Interactive command line startup*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command : {noformat}
./startup.sh -C
{noformat}
# Done :-)

\\
*Daemon startup*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
./startup.sh -D
{noformat}
# Done :-)

h2. Windows

*Non-interactive command line startup*

# Go to {{%PETALS_HOME%\bin}}
# Execute the following command :
{noformat}
startup.bat
{noformat}
# Done :-)

\\
*Interactive command line startup*

# Go to {{%PETALS_HOME%\bin}}
# Execute the following command : {noformat}
startup.bat -C
{noformat}
# Done :-)

h1. Stopping Petals ESB

There are two ways of stopping Petals ESB. :
* the *"stop procedure"* stops Petals ESB *without uninstalling anything*
* the *"shutdown procedure"* *uninstall everything* and cleans up Petals ESB

In most case, you should prefer using the "stop procedure".

h2. Using the "Stop Procedure"

The "Stop Procedure" stops Petals ESB without uninstalling any component, shared library or service assembly.

h3. Linux / MacOS X

*Stop a Petals ESB instance launched in non-interactive, command line or daemon mode*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
./stop.sh
{noformat}
# Done :-)

\\
*Stop a Petals ESB instance launched in non-interactive or interactive mode*

# In the Petals ESB console, type *ctrl + c*.
# Done :-)

\\
*Stop a Petals ESB instance launched in interactive mode*

# In the Petals ESB console, type 'q'
{noformat}
petals@localhost:/> q
{noformat}
# Done :-)

h3. Windows

*Stop a Petals ESB instance launched in non-interactive, command line or daemon mode*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
stop.bat
{noformat}
# Done :-)

\\
*Stop a Petals ESB instance launched in non-interactive or interactive mode*

# In the Petals ESB console, type *ctrl + c*.
# Done :-)

\\
*Stop a Petals ESB instance launched in interactive mode*

# In the Petals ESB console, type 'q'
{noformat}
petals@localhost:/> q
{noformat}
# Done :-)

\\
{note:title=Note}
As we've seen, some Petals ESB modes supports various "Stop Procedures".
{note}


h2. Using the "Shutdown Procedure"

The "Shutdown Procedure" shut Petals ESB down and uninstall every component, shared library or service assembly that has been installed.

h3. Linux / MacOS X

*Stop a Petals ESB instance launched in non-interactive, command line or daemon mode*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
./shudown.sh
{noformat}
# Done :-)


\\
*Stop a Petals ESB instance launched in interactive mode*

# In the Petals ESB console, type 'x'
{noformat}
petals@localhost:/> x
{noformat}
# Done :-)

h3. Windows

*Stop a Petals ESB instance launched in non-interactive, command line or daemon mode*

# Go to {{$PETALS_HOME/bin}}
# Execute the following command :
{noformat}
shutdown.bat
{noformat}
# Done :-)


\\
*Stop a Petals ESB instance launched in interactive mode*

# In the Petals ESB console, type 'x'
{noformat}
petals@localhost:/> x
{noformat}
# Done :-)

\\
{note:title=Note}
As we've seen, some Petals ESB modes supports various "Shutdown Procedures".
{note}
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}