Petals EE 5.1.0

Released on Febr. 15^th, 2018
The release notes are available here.
This release comes mainly with improvements on components:
- Petals BC Rest was been reworked to improve its provider side.
- Petals BC Mail is now able to provides your own services, the internal port type is no more required.
- Petals SE Activiti has been replaced and improved by Petals SE Flowable.
- Petals SE Mapping is a new service engine to “facadize” an existing service provider.
- Maven URLs are now supported by Petals CLI and Petals ESB to deploy artefacts (SL, BC, SE or SA).
- A lot of bug fixes and other improvements.
Access the Petals ESB container documentation
Access the Petals ESB component documentation

Petals Studio 1.4.0

Petals Studio 1.4.0 is the maintenance release of Petals Studio for Petals 5.0.0 / 5.1.0. Select the right version of Petals Studio for your operating system.

Released on March 21^th, 2017
Take a look at the Release Notes
Access the documentation

Docker Images

Docker images for Petals can be downloaded from Docker Hub.

Debian Packages

The essential parts of Petals EE are available as Debian packages. This is useful in particular for production environments.

The Petals commons package required for all packages.

The Petals ESB container.
The auto-loader extension for the container.

The Petals ESB Registry node.
Petals ESB Registry CLI, the command-line administration tool for Petals ESB Registry.

Petals CLI, the command-line administration tool for Petals ESB.
Debian package adding commands for:
- BC Gateway,
- BC SFTP
Debian packages to monitor Petals with Cacti: Base package - Cacti extension.
Debian packages to monitor Petals with Nagios: Base package - Nagios extension.

Notice the base package is the same for both monitoring tools.

ZIP Archives

In addition to the Petals Enterprise Edition ZIP archive, several Petals ESB variants and tools are provided as ZIP Archive. This is useful in particular for development environments.

The Minimal Petals container is a Petals ESB container without any extensions.
The default Petals container is a Petals ESB container with following extension: Petals Auto-loader, Petals Embedded Overlay Registry.
The auto-loader extension to add to a minimal Petals container.

The Petals ESB Registry node.
Petals ESB Registry CLI, the command-line administration tool for Petals ESB Registry.

The Minimal Petals CLI, the command-line administration tool for Petals ESB, without any extension.
The default Petals CLI, the command-line administration tool for Petals ESB with following extension: monitoring command with its Cacti and Nagios extensions, the command to check BC SFTP connections and commands to operate the Petals BC Gateway.

Community Pack

Now, each version of Petals ESB Enterprise can be completed by elements delivered with the Community Pack for Petals EE. This pack contains extra components and shared libraries.