PetrisWINDS Enterprise (PWE) uses some BPEL 1.1 constructs to define and manage workflows. PWE Messages (see opposite) use XML to control interaction between PWE services. These use the BPEL concept of execution processing, with nested workflows and service interactions.
Transfer service
A PWE Message informs a ‘Transfer service’ about which adapters are going to be invoked, and what function they are supporting. The <flow> section defines the process, and the <service> tag defines which action is requested, passing parameters to the service.
BPEL
BPEL provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. BPEL defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces. Petris does not deploy strict BPEL tagging but plans to deploy the standard at a future date.
OASIS
IBM, Microsoft, BEA (supplier of the technology that underpins PWE), Siebel and SAP submitted BPEL for Web Services version 1.1 to the OASIS standards body earlier this year.
PetrisWINDS code snippet
<flow>
<service>
<name>Add QC Status</name>
<action>add-attribute</action>
<parameters>
<param>
<name>datatype_name</name>
<value>curve</value>
</param>
<param>
<type>attribute-add</type>
<name>status</name>
<value>PUBLISHED</value>
</param>
</parameters>
<flow>
<service>
<name>Update Catalog</name>
<action>catalog-insert</action>
<parameters>
<param>
<name>datasource_id</name>
<value>-9999</value>
</param>
etc...
© Oil IT Journal - all rights reserved.