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}
E-mail
...