E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History
...
h1. Introduction To start the Petals containers, for example, launch the following command on a Ubuntu box:
{code}
{code}
cdeneux@sph-latitude-D630:~$ sudo service petals-esb start
{code}
...* 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.
* 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.
{info}It's not possible to automatically start a container in debug mode. Use a manual startup.{info}
{info}It's not possible to automatically start a container in debug mode. Use a manual startup.{info}
{note}Caution: 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 the sirectory, 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.{note}
h3. 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:
{{code}}
sudo -u petals petals-esb -u <container-configuration>
{{code}}
where {{<container-configuration>}} is the URL of the container configuration (ie, URL locating the file {{server.properties}})
{quote}For example, to launch the default sample container
{{code}}
sudo -u petals petals-esb -u file:///etc/petals-esb/container-available/default/server.properties
{{code}}
{quote}
{{code}}
sudo -u petals petals-esb -u <container-configuration>
{{code}}
where {{<container-configuration>}} is the URL of the container configuration (ie, URL locating the file {{server.properties}})
{quote}For example, to launch the default sample container
{{code}}
sudo -u petals petals-esb -u file:///etc/petals-esb/container-available/default/server.properties
{{code}}
{quote}
...