E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (37)
View Page History
...
{composition-setup}{composition-setup} {multi-excerpt}
h1. Petals Platform Features in a nutshell
h1. What is Petals Platform used for?
h2. Petals ESB, a light, flexible, natively distributed bus
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:
Beyond the inherent improvments of an ESB over traditional EAI solutions, Petals ESB uses a best-of-breed approach and open source development model to distinguish from other ESB solutions, bringing essential features.
- 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.
- 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.
h3. Natively Distributed Architecture
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}
{cloak:id=ESB history}{em}
{multi-excerpt-include:glossary:ESB|name=history|nopanel=true}{em}
{cloak}
Most of EAI and ESB solutions are based on a centralized architecture. This choice brings simplicity of configuration and maintenance. One risk however is the great loss the company would sustain in case of serious problem with the middleware.
Choosing a middleware clusters reduce this risk but adds great complexity to the infrastructure.
Petals ESB chose the third way, using a P2P-like approach: the container can be installed on several machines, each one hosting its set of services, router and shared registry of services.
- high availability, thus SLA respect, thanks to replication of services on several nodes and intelligent routing;
- inherent load balancing.
[Learn more on architecture models|http://www.petalslink.com/en/technologies/what-is-a-highly-distributed-architecture]
Choosing a middleware clusters reduce this risk but adds great complexity to the infrastructure.
Petals ESB chose the third way, using a P2P-like approach: the container can be installed on several machines, each one hosting its set of services, router and shared registry of services.
- high availability, thus SLA respect, thanks to replication of services on several nodes and intelligent routing;
- inherent load balancing.
[Learn more on architecture models|http://www.petalslink.com/en/technologies/what-is-a-highly-distributed-architecture]
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. Light & Powerful
However, setting up a services-oriented architecture from an existing infrastructure can be very time&money consuming. This is where Petals Platform play its cards. Thanks to its native conception and configuration / administration / business-oriented tools, Petals Platform allows a pragmatic approach for SOA integration.
Petals ESB is entirely modular, making it a light platform, running without application server. Numerous components are already available for data exchange (FTP, SOAP, REST, POP...) and data manipulation (POJO, Quartz, XSLT, Talend...)
h2 Monitoring and Orchestration capabilities
By combining Petals BPEL/SCA service engines and our dedicated IDE, Petals Studio, you can easily assemble individual services to form business processes, with GUI and code validation.
Using notifications service engine, Petals View allows easy monitoring configuration, so that end business users can watch their business processes and analyse their efficiency.
h2 Monitoring and Orchestration capabilities
By combining Petals BPEL/SCA service engines and our dedicated IDE, Petals Studio, you can easily assemble individual services to form business processes, with GUI and code validation.
Using notifications service engine, Petals View allows easy monitoring configuration, so that end business users can watch their business processes and analyse their efficiency.
A typical SOA project using Petals Platform could be as such:
h3. Standard and Open Source
Roles (broad-grained)
Petals ESB is one of the few to be fully compliant with the Java Business Integration specification. It makes full use of standards protocols.
As an open source product, you can freely adapt it to fit your need, be it through a new component or container adaptation, or ask any expert to do it for you, without being bound to Petals Link (although we are probably the finest experts on these matters hehe).
As an open source product, you can freely adapt it to fit your need, be it through a new component or container adaptation, or ask any expert to do it for you, without being bound to Petals Link (although we are probably the finest experts on these matters hehe).
Roadmap
+Phase 1: Building a small-range project to integrate Petals ESB in your infrastructure, and learn its use.+
+Phase 1: Building a small-range project to integrate Petals ESB in your infrastructure, and learn its use.+
h3. Ease of Configuration
# 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.
# 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.
Setting up services, orchestrating them, creating data transformation jobs, can prove a hassle from middle-sized projects on. [Petals Studio|petalsstudio:] greatly facilitates these steps, by providing numerous service creation wizards, import/export tools, a graphical interface to create services orchestrations.
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.
h3. Ease of Administration
Petals ESB is bundled with a [Web Console|webconsole:], web-GUI to easily watch and administer the ESB: deployement of new services units and assemblies, components management, fine-grained technical monitoring, testing facilities.
Petals ESB is bundled with a [Web Console|webconsole:], web-GUI to easily watch and administer the ESB: deployement of new services units and assemblies, components management, fine-grained technical monitoring, testing facilities.
+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.+
h3. Business-oriented monitoring
# 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.
# 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.
While previous items appealed more to developers and system administrators, Petals View is aimed more at non-technical users. Once Petals View has been set up and connected by the former, end-users can further configure fine-grained, detailed business reports on any message exchange going through Petals ESB. With this, they can easily follow their business procedures, identify any problem and use this data to build process efficiency analyses.
h1. Petals Platform Features in a nutshell
h3. Business-oriented services management
{include:Petals Platform Features}
In contrast with the webconsole, which allows technical deployment and management of services, Petals Master provides a graphical way to manage services from a business point of view. Associate services to roles, users and company to build a structured business-oriented view of all your services, document them with attached documents. All of this allows better business management, processes improvement and optimal reuse of services. Thus ensuring a proper evolution of your infrastructure.
{show-to:user=llacote}
{toggle-cloak:id=brouillon} ANCIEN
{cloak:id=brouillon}
{cloak:id=brouillon}
h1. Who is Petals Platform for? - setting up your typical Petals Platform instance
...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
- Developer:
- Project Manager:
- End-user
{cloak}
h1 ANCIEN
h2. What is an Enterprise Service Bus?
{multi-excerpt-include:glossary:ESB|name=abstract|nopanel=true}
{multi-excerpt-include:glossary:ESB|name=|nopanel=true}
h2. From EAI to ESB
{multi-excerpt-include:glossary:ESB|name=history|nopanel=true}
h2. ESB Technology Overview
{multi-excerpt-include:glossary:ESB|name=overview|nopanel=true}
{multi-excerpt-include:glossary:ESB|name=definition|nopanel=true}
{show-to:group=petalslink-team}
h2. The Service Oriented Architecture FIXME
{show-to}
h1. Petals ESB, the Enterprise Service Bus
[Check the full Petals ESB datasheet|http://www.petalslink.com/en/product/petals-esb]