E-mail
Introduction
|
Once Petals ESB is installed through the Debian package, it can be started or stopped with two different ways:
|
Table of contents Contributors
No contributors found for: authors on selected page(s)
|
Starting Petals ESB
Starting Petals ESB at system level
Automatic start
The Petals ESB package comes with an automatic startup script based on System V (initd) to automatically launch Petals ESB containers as system services when the host boots.
To start the Petals containers, for example, launch the following command on a Ubuntu box:
cdeneux@sph-latitude-D630:~$ sudo service petals-esb start
Two natures of containers are identified:
- the "available containers" that are configured. These containers are to configure into the directory /etc/petals-esb/container-available. One sub-directory by container.
- and, the "enable containers" that are automatically started. These containers are to configure into the directory /etc/petals-esb/container-enable. One sub-directory by container.
As "Enable containers" are a subset of "Available containers", we recommend to put the configuration of a container into a sub-directory of /etc/petals-esb/container-available, and create a symbolic link on this sub-directory into /etc/petals-esb/container-enable to "enable" it.
 | It's not possible to automatically start a container in debug mode. Use a manual startup. |
 | The automatic startup starts all Petals ESB containers declared in the directory /etc/petals-esb/container-enable. So if you add a new Petals ESB container in this directory, and use the command "service petals-esb start", all other Petals ESB containers will be also started, and as they are already started, errors will occurs. |
Manual start
A Petals ESB container configured at system level (its configuration is located in /etc/petals-esb/container-available, and uses sub-directories of /var/lib/petals-esb and /var/log/petals-esb) can be started using a manual startup, for example, to test its configuration. This startup is done using the same mechanism as a Petals ESB container configured at user level, but using the system user 'petals' to be compliant with ACL of the filesystem:
sudo -u petals petals-esb -u <container-configuration>
where <container-configuration> is the URL of the container configuration (ie, URL locating the file server.properties)
For example, to launch the default sample container
sudo -u petals petals-esb -u file:///etc/petals-esb/container-available/default/server.properties
| When manually starting a Petals ESB container, it will be automatically stopped when closing your shell. Don't use this way to start a Petals ESB container as a system service. |
Starting Petals ESB at user level
A Petals ESB container configured at user level (its full configuration is located under the user's home directory) can be only started using a manual startup:
petals-esb -u <container-configuration>
where <container-configuration> is the URL of the container configuration (ie, URL locating the file server.properties)
For example:
petals-esb -u file:///home/cdeneux/my-petals-esb-containers/demo1/server.properties
| When manually starting a Petals ESB container, it will be automatically stopped when closing your shell. |