{section}
{column}
h1. Introduction
Petals ESB can be deployed into the cloud. By this way, to optimize hardware resources consumption:
* Petals ESB containers are instantiated on-demand,
* Service providers are placed on the right Petals ESB container according to the system load.
In a user point of view, the Petals Virtual Container (PVC) will be the service infrastructure running all service consumers and service providers. The PVC is composed of:
* nodes of the Petals Registry Overlay, that are automatically instantiated according to the system load of the Petals Registry nodes,
* Petals ESB containers that are automatically instantiated according to the system load of containers.
The user will deploy its regular Petals artifacts (shared library, components, SA or deployable SU) into the PVC. Service providers will be placed on the right container, and all dependencies (shared library, components) will be automatically deployed on this container.
{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. Preparing the environment
Deployment of a PVC is assumed by [Roboconf|http://roboconf.net]. Make sure you have an operational Roboconf installation.
Before to install anything, you must define your software components to Roboconf:
* the software components of your applications used as service providers exposed into the PVC,
* the software components of the PVC, ie: mainly service units,
* the software components of your applications consuming service providers available into the PVC.
{gliffy:name=PVC_Overview|align=center|version=2}
h1. Installing the container
The installation of Petals ESB depends on your operating system. The following table resumes which archives is needed according to your operating system. Petals ESB archives are available on the Petals's web-site: [http://petals.ow2.org].
|| Operating System || OS Version || Petals archive to use || Installation procedure ||
| Debian-based Linux | all | Debian packages | [Installing Petals ESB using the Debian packages]|
| Linux | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
| Microsoft Windows | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
| Mac OS | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
\\
+Note:+ The ZIP archive can be used on Debian-based systems. In this case, Petals ESB should be installed as a user software without integration with the operating system.
{column}
h1. Introduction
Petals ESB can be deployed into the cloud. By this way, to optimize hardware resources consumption:
* Petals ESB containers are instantiated on-demand,
* Service providers are placed on the right Petals ESB container according to the system load.
In a user point of view, the Petals Virtual Container (PVC) will be the service infrastructure running all service consumers and service providers. The PVC is composed of:
* nodes of the Petals Registry Overlay, that are automatically instantiated according to the system load of the Petals Registry nodes,
* Petals ESB containers that are automatically instantiated according to the system load of containers.
The user will deploy its regular Petals artifacts (shared library, components, SA or deployable SU) into the PVC. Service providers will be placed on the right container, and all dependencies (shared library, components) will be automatically deployed on this container.
{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. Preparing the environment
Deployment of a PVC is assumed by [Roboconf|http://roboconf.net]. Make sure you have an operational Roboconf installation.
Before to install anything, you must define your software components to Roboconf:
* the software components of your applications used as service providers exposed into the PVC,
* the software components of the PVC, ie: mainly service units,
* the software components of your applications consuming service providers available into the PVC.
{gliffy:name=PVC_Overview|align=center|version=2}
h1. Installing the container
The installation of Petals ESB depends on your operating system. The following table resumes which archives is needed according to your operating system. Petals ESB archives are available on the Petals's web-site: [http://petals.ow2.org].
|| Operating System || OS Version || Petals archive to use || Installation procedure ||
| Debian-based Linux | all | Debian packages | [Installing Petals ESB using the Debian packages]|
| Linux | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
| Microsoft Windows | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
| Mac OS | all | ZIP archive | [Installing Petals ESB using the ZIP archive] |
\\
+Note:+ The ZIP archive can be used on Debian-based systems. In this case, Petals ESB should be installed as a user software without integration with the operating system.