{section}
{column}
h1. Installing Petals ESB using the Debian packages
Several Debian packages are available:
|| Package || Description || Depends on || Required for a production use ||
| {{petals-esb}} | The base package of Petals ESB to run a minimalist container | {{java2-runtime}} | required |
| {{petals-esb-autoloader}} | The extension "Petals ESB Autoloader" | {{petals-esb}} | not recommended |
| {{petals-esb-artfifact-repository}} | The extension "Petals ESB artfifact repository" | {{petals-esb}} | optional |
+Note 1:+ The Petals ESB Autoloader is not recommended in production mode because of security reasons.
+Note 2:+ If your security policy requires to push your JBI artifacts on the host instead of downloading them, you can:
* use the extension Petals ESB artifact repository and push your JBI artifacts in its repository,
* or, push your JBI artifacts in a dedicated directory and use a remote Petals CLI with local file-based URLs.
{column}
{column:width=35%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. Content of the packages
h2. Content of the package "{{petals-esb}}"
This package arrives with following directories and files:
* {{/usr/bin/petals-esb}}: The script used to start a Petals container,
* {{/etc/petals-esb/container-enable/<container-name>}}: A directory containing the configuration of a Petals container:
** {{server.properties}}: the base configuration of the Petals container,
** usually, the following configuration files are placed in the same directory than the file {{server.properties}}:
*** {{topology.xml}}: the Petals topology of which the container is a member,
*** {{loggers.properties}}: configuration file of the logging system based on JDK Logging,
*** {{log4j.properties}}: configuration file of the logging system Log4J,
* {{/etc/petals-esb/container-available}}: A directory containing links to sub-directoryies of {{/etc/petals-esb/container-enable}}. If a container is linked into this directory, it will be automatically started on machine startup,
* {{/var/lib/petals-esb/<container-name>}}: Default location of the root directory of the Petals container data area. It will contain:
** the sub-directory {{repository}} is the *default* storage area of the internal repository containing installed/deployed artefacts,
** the sub-directory {{work}} used as internal working area of the *default* container,
* {{/var/log/petals-esb/<container-name>}}: Default location in which logging files of the Petals container will be written.
{color:red}
* a directory {{bin}} that contains the startup script and launcher of Petals ESB,
* a directory {{lib}} where all libraries required by the core of Petals ESB are put,
{color}
h2. Content of the package "{{petals-esb-autoloader}}"
This package arrives with 2 new sub-directories of the root directory of the Petals container data area:
* the sub-directory {{install}}: the directory scanned by the auto-loader of the container to install/deploy artfifact,
* the sub-directory {{installed}}: the directory scanned by the auto-loader of the container to uninstall/undeploy artfifact.
h2. Content of the package "{{petals-esb-artfifact-repository}}"
This package arrives with one new sub-directory of the root directory of the Petals container data area:
** the sub-directory {{artifact}} in which artifacts should be placed before installation/deployment.
{column}
h1. Installing Petals ESB using the Debian packages
Several Debian packages are available:
|| Package || Description || Depends on || Required for a production use ||
| {{petals-esb}} | The base package of Petals ESB to run a minimalist container | {{java2-runtime}} | required |
| {{petals-esb-autoloader}} | The extension "Petals ESB Autoloader" | {{petals-esb}} | not recommended |
| {{petals-esb-artfifact-repository}} | The extension "Petals ESB artfifact repository" | {{petals-esb}} | optional |
+Note 1:+ The Petals ESB Autoloader is not recommended in production mode because of security reasons.
+Note 2:+ If your security policy requires to push your JBI artifacts on the host instead of downloading them, you can:
* use the extension Petals ESB artifact repository and push your JBI artifacts in its repository,
* or, push your JBI artifacts in a dedicated directory and use a remote Petals CLI with local file-based URLs.
{column}
{column:width=35%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. Content of the packages
h2. Content of the package "{{petals-esb}}"
This package arrives with following directories and files:
* {{/usr/bin/petals-esb}}: The script used to start a Petals container,
* {{/etc/petals-esb/container-enable/<container-name>}}: A directory containing the configuration of a Petals container:
** {{server.properties}}: the base configuration of the Petals container,
** usually, the following configuration files are placed in the same directory than the file {{server.properties}}:
*** {{topology.xml}}: the Petals topology of which the container is a member,
*** {{loggers.properties}}: configuration file of the logging system based on JDK Logging,
*** {{log4j.properties}}: configuration file of the logging system Log4J,
* {{/etc/petals-esb/container-available}}: A directory containing links to sub-directoryies of {{/etc/petals-esb/container-enable}}. If a container is linked into this directory, it will be automatically started on machine startup,
* {{/var/lib/petals-esb/<container-name>}}: Default location of the root directory of the Petals container data area. It will contain:
** the sub-directory {{repository}} is the *default* storage area of the internal repository containing installed/deployed artefacts,
** the sub-directory {{work}} used as internal working area of the *default* container,
* {{/var/log/petals-esb/<container-name>}}: Default location in which logging files of the Petals container will be written.
{color:red}
* a directory {{bin}} that contains the startup script and launcher of Petals ESB,
* a directory {{lib}} where all libraries required by the core of Petals ESB are put,
{color}
h2. Content of the package "{{petals-esb-autoloader}}"
This package arrives with 2 new sub-directories of the root directory of the Petals container data area:
* the sub-directory {{install}}: the directory scanned by the auto-loader of the container to install/deploy artfifact,
* the sub-directory {{installed}}: the directory scanned by the auto-loader of the container to uninstall/undeploy artfifact.
h2. Content of the package "{{petals-esb-artfifact-repository}}"
This package arrives with one new sub-directory of the root directory of the Petals container data area:
** the sub-directory {{artifact}} in which artifacts should be placed before installation/deployment.