Installing Petals ESB using the Debian packages

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (20)

View Page History
h1. Creating the users
h1. Installing Petals ESB using the Debian packages

todo
Several Debian packages are available:
|| Package || Description || Depends on || Reauired 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 |

h1. Database setup
+Note:+ The Petals ESB Autoloader is not recommended in production mode because of security reasons.

todo
h1. Content of the packages

h1. WebConsole setup
h2. Content of the package "{{petals-esb}}"

todo
The ZIP archive contains:
* 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,
* a directory {{conf}} containing the *default* configuration of the Petals container,
* a directory {{data}} that is the root directory of the data area required by The *default* container:
** 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,

h1. Tunning
* a directory {{logs}} that is the directory in which log files of the *default* container will be written.

h2. Adapting Petals ESB to the version of IP network stack
h2. Content of the package "{{petals-esb-autoloader}}"

{include:Adapting Petals ESB to the version of IP network stack}
** the sub-directory {{install}}: the directory scanned by the auto-loader of the *default* container to install/deploy artfifact,
** the sub-directory {{installed}}: the directory scanned by the auto-loader of the *default* container to uninstall/undeploy artfifact,

h2. Avoid the "too many open files" when heavily use the BC-SOAP

# At the end of the {{/etc/limits.conf}} or {{/etc/security/limits.conf}} add the following line :
{noformat}
user hard nofile 4096
{noformat}

# In the {{.bashrc}} file of the user who launches Petals ESB, add the following line :
{noformat}
ulimit -n 4096
{noformat}

# Reboot

# Login and check the result of the following command :
{noformat}
ulimit -a
{noformat}

# Done, you should never see that error...if so, try to increase the limit.
h2. Content of the package "{{petals-esb-artfifact-repository}}"
{color:red}TO DO{color}