E-mail
Introduction
|
The ZIP archive comes with elementary startup and stop mechanisms. No automatic startup is provided. It does not support several container with only one installation. If you need these features, see "Installing Petals ESB using the Debian packages" or write yours.
|
Table of contents Contributors
No contributors found for: authors on selected page(s)
|
Starting Petals ESB
To start the Petals ESB container configured in $PETALS_HOME/conf, go into the directory $PETALS_HOME/bin and execute the following command from a command-line:
cdeneux@sph-latitude-D630:~/petals-esb/bin/petals-esb.sh
 | Use the script petals-esb.bat instead of petals-esb.sh for Windows-based system. |
| Use the JAVA_OPTS environment variable to add more JVM options. They will take precedence over those specified in $PETALS_HOME/conf/env.sh but both will nevertheless be used. |
Stopping Petals ESB
To stop a Petals ESB container, just kill it with a Ctrl-C on its console, or use the following command from another shell:
cdeneux@sph-latitude-D630:~/petals-esb/bin/petals-esb.sh stop
| Use the script petals-esb.bat instead of petals-esb.sh for Windows-based system. |
Debugging your services
Petals ESB container can be started in debug mode to be able to connect it to a debugger as the one provided with Eclipse.
To start the Petals ESB container in debug mode, just go into the directory $PETALS_HOME/bin and execute the script debug.sh instead of petals-esb.sh from a command-line:
cdeneux@sph-latitude-D630:~/petals-esb/bin/debug.sh
Once, Petals ESB container is started in debug mode, just connect your debugger UI to the debugger agent started with Petals ESB container. By default, the debugger agent listens on port 8000. If you want to use another port value, set it directly in the script debug.sh|bat.
| Use the script debug.bat instead of debug.sh for Windows-based system. |