Petals SOA Suite

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]

{cloak}

{column}
{column}
{float:right}!welcome:Images^petalsplatform_overview.png|width=500px!{float}
{column}

- {important}Mediation platform{important}: 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...
- {important}Flexible infrastructure{important}: 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 since 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.

!PetalsESB_Typical_Uses.png|border=1!

h1. Let's get it on\!

First step will be to get 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|Wiki User Guide#registering] (favorites, followup, comments...).
For any question, [feel free to visit our forums|http://forums.petalslink.com]\!

{show-to:llacote, vzurczak}
{petalslink:author=llacote|type=FIXME A REPRENDRE POUR CONSTRUIRE SCHEMA}

# 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.
{petalslink}
{show-to}