PEtALS will allow you
* to make services out of existing web services, rmi services, CSV or
XML batch file, databases and many more, as Roland says
* to adapt (transformation with various languages) their document
format to your own service's business APIs, or to your BP engine's
requirements, to quickly mash up services using code or scripting to
bridge the delta between business level and technical level. That's
actually a *very* common use when doing SOA integration, have a look at
http://www.infoq.com/articles/louis-dutoo-esb-routing to see how and why
it complements orchestration.
* to monitor their uses
In short, if you've already got all (web) services you need defined at
the right (business) level, deployed and connected to your information
system, then maybe you don't need PEtALS. Otherwise...
Regards,
Marc Dutoo
Open Wide
Roland Naudin - EBM WebSourcing a écrit :
> BPEL is good to design the orchestration of services.
> But where your services will be processed, by who?
>
> PEtALS provides the framework to process them.
>
> Le mardi 19 mai 2009 à 11:11 +0200, Rudy Commenge a écrit :
>
>> Hello,
>>
>> I'm creating BPEL processes.
>> I deploy on Orchestra, and it works.
>> So I think Orchestra is an ESB.
>>
>> However, it's recommended to use Petals with Orchestra.
>> So what are the benefits to use Petals with Orchestra ?
>>
>> Thanks.
>> pièce jointe document texte brut (message-footer.txt)
>> --
>> You receive this message as a subscriber of the
petals-users@... mailing list.
>> To unsubscribe: mailto:
petals-users-unsubscribe@...
>> For general help: mailto:
sympa@...?subject=help
>> OW2 mailing lists service home page:
http://www.ow2.org/wws>>
--
You receive this message as a subscriber of the
petals-users@... mailing list.
To unsubscribe: mailto:
petals-users-unsubscribe@...
For general help: mailto:
sympa@...?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws