{composition-setup}{composition-setup}

{multi-excerpt:name=abstract}{em} Petals Platform is a fully-fledged open source middleware solution, capable of meeting all your integration, exchange and architecture needs. It provides you with a lightweight, [distributed open source ESB|petalsesb:], [integration & configuration wizards (IDE)|petalsstudio:], [administration web console|webconsole:], [business monitoring tool|petalsview:] and [SOA governance tool|petalsmaster:].{em}{multi-excerpt}

h1. What is Petals Platform?

Petals Platform is a middleware solution suite of open source software consisting of:
- Petals ESB - the enterprise service bus (core component of the Petals Platform) including many components (Petals components) for communication/data integration and data transformation using common and open standards.
- Petals Studio - integrated development environment (IDE), based on Eclipse with wizards, interface and code validation specific to the Petals ESB environment.
- Petals View - business activity monitoring for Petals Platform.
- Petals Master - a governance toolset to improve utility and productivity of your services architecture.

Petals Link has already provided its services to more than fifty companies and administrations.
Our core technology, Petals ESB, is used in Telecommunications (Orange), Defense & Security (French Air Force, French General Directorate for Armament), Health (Cegedim Activ, Almerys) and Public administrations (DGME, URSSAF, General Councils of Gironde and Limousin, City of Lyon).{em}
[http://www.petalslink.com]

h1. Petals Platform Features in a nutshell

{excerpt}
{toggle-cloak:id=distributed|exclusive=true}{important}Distributed{important}
{cloak:id=distributed}{multi-excerpt-include:welcome:Petals Platform Features|name=distributed|nopanel=true}
{cloak}

{toggle-cloak:id=light powerful|exclusive=true}{important}Light & Powerful{important}
{cloak:id=light powerful}{multi-excerpt-include:welcome:Petals Platform Features|name=light powerful|nopanel=true}
{cloak}

{toggle-cloak:id=standard open-source|exclusive=true}{important}Standard & Open Source{important}
{cloak:id=standard open-source}{multi-excerpt-include:welcome:Petals Platform Features|name=standard open-source|nopanel=true}
{cloak}

{toggle-cloak:id=configuration|exclusive=true}{important}Ease of configuration{important}
{cloak:id=configuration}{multi-excerpt-include:welcome:Petals Platform Features|name=configuration|nopanel=true}
{cloak}

{toggle-cloak:id=administration|exclusive=true}{important}Ease of administration{important}
{cloak:id=administration}{multi-excerpt-include:welcome:Petals Platform Features|name=administration|nopanel=true}
{cloak}

{toggle-cloak:id=business monitoring|exclusive=true}{important}Business-oriented monitoring{important}
{cloak:id=business monitoring}{multi-excerpt-include:welcome:Petals Platform Features|name=business monitoring|nopanel=true}
{cloak}

{toggle-cloak:id=business management|exclusive=true}{important}Business-oriented management{important}
{cloak:id=business management}{multi-excerpt-include:welcome:Petals Platform Features|name=business management|nopanel=true}
{cloak}

[See detailed Petals Platform Features list|Petals Platform Features]

{excerpt}

h1. What is Petals Platform used for?

h3. Modern enterprise needs

As a extensible platform revolving around an open source Enterprise Service Bus, Petals Platform can cover traditional needs as well as more ambitious projects. Most companies / organisations have three typical needs nowaday:

- application integration: connecting heterogeneous applications to share data or features, automate some processes, in overall lessening the human intervention in data processing.
- mediation platform: exposing data and/or services outside one's infrastructure, to allow employees to work in travelling, providing online services to clients or partners, to gather data from external sources...
- flexible infrastructure: being able to adapt services, processes or modifying software composition (like, replacing a business-oriented solution for a more performant one) without impacting the running infrastructure.

The two first needs are being covered for years, with the help of EAI (Enterprise Applications Integrations) solutions, ancestors of today's {toggle-cloak:id=ESB history}Enterprise Service Buses.
{cloak:id=ESB history}{em}
{multi-excerpt-include:glossary:ESB|name=history|nopanel=true}{em}
{cloak}

As for the need for an agile infrastructure, that's where [Services-Oriented Architectures|glossary:SOA] shine, and that's why SOA market soared up since the last years, while SOA as a concept gained analyst's approval. [FIXME mettre sources]

h3. SOA integration, a pragmatic approach

A typical SOA project using Petals Platform could be as such:

h6. +Phase 1: Building a small-range project to integrate Petals ESB in your infrastructure, and learn its use.+

# Draw the "map" of your infrastructure, so you can see where you start from. (Chief Information Officer)
# Define a simple case in which you could use Petals ESB (interconnect two applications, expose a service through a webportal, chain several applications's features as services to create a business process. (SOA Architect / Project Manager)
# Deploy Petals ESB and necessary components with the Petals Webconsole. (Developer)
# Create necessary services, thanks to Petals Studio. (Developer)
# If necessary, orchestrate the services to create a business process. (???)
# If planned, expose the resulting process. (???)
# Set up notifications on desired exchanges (Developer)
# Configure Petals View to monitor and retrieve desired information for further exploitation (Business Analyst)
With this, a specific part of the infrastructure has been made flexible, interoperable, SOA-ready.
# Deploy Petals Master, to set the bases for a good SOA-oriented management: build services index, create companies/users/roles, associate these data to related services.

With this, you have set up a fully functional environment with SOA capabilities, while keeping complexity and resources consumption to a low level, thanks to limited field of implementation.

h6. +Phase 2: Once the container is installed, and you gained design/configuration knowledge, you can expand your SOA integration on a step-by-step basis, depending on needs and resources.+

# Define another use-case, in same or another business department.
# Check the Petals Master's database to find any reusable service.
# Deploy new components if necessary.
# Build services and orchestrate them.
# Set up messages notifications
# Configure related monitoring in Petals View
# Update Petals Master with new users/company/roles and services association.

Repeat this phase to blend new services and business processes in your modern, agile ESB-based infrastructure, without disrupting global reliability or functional range.

h1. Let's get it on\!

First step will be to download our latest released products, at our download center : [http://download.petalslink.com]
Then, dive into action, with the help of our user guides, starting with [Petals ESB|http://doc.petalslink.com/x/TwAT].

Register on doc.petalslink.com and [take the most out of documentation with useful features|welcome:Wiki User Guide#registering] (favorites, followup, comments...).
For any question, [feel free to visit our forums|http://forums.petalslink.com]\!

{show-to:user=llacote}

h1. {toggle-cloak:id=brouillon}Brouillon
{cloak:id=brouillon|hidden=true}
Why use Petals ESB?

It provides a reliable, progressive and convenient way to migrate your infrastructure towards one based on service-oriented architecture.
As you answer daily integration and mediation needs for a specific department / process, while preparing a new

Its natively distributed architecture, modular conception
As you progress in integrating Petals ESB with parts of your infrastructure, you're seamlessly preparing your SOA infrastructure at the same time.

Beyond core middleware capabilities of Petals ESB, the whole Platform allows each and every role to build an infrastructure more fitted to business needs:
- Developer:
- Project Manager:
- End-user

{cloak}
{show-to}