Explore chapters and articles related to this topic
Methods and techniques for acquiring manufacturing knowledge
Published in Justyna Patalas-Maliszewska, Managing Manufacturing Knowledge in Europe in the Era of Industry 4.0, 2023
Each of the categories is divided into subsets. The first group of elements includes such subsets as events, activities, gates, connectors and others. BPEL is a programming language based on XML (Extensible Markup Language), used to define business processes based on web services. Any business process specified in BPEL notation is also a web service, and can enter and be included in other processes. The BPEL distinguishes five main sections:Message flow – triggering an operation, sending a request and waiting for the result.Control flow – the way actions follow one another, i.e. hierarchical or graph flow.Data flow – variables used in the business process.Orchestration of processes – determining the relationship between services.Error and exception handling – error handling procedure.
Cloud Computing
Published in Vivek Kale, Agile Network Businesses, 2017
The orchestration and choreography of Web services are enabled under three specification standards—namely, the Business Process Execution Language for Web Services (BPEL4WS or BPEL for short), WS-Coordination (WS-C), and WS-Transaction (WS-T). These three specifications work together to form the bedrock for reliably choreographing Web service–based applications, providing BPM, transactional integrity, and generic coordination facilities. BPEL is a workflow-like definition language that describes sophisticated business processes that can orchestrate Web services. WS-C and WS-T complement BPEL to provide mechanisms for defining specific standard protocols for use by transaction processing systems, workflow systems, or other applications that wish to coordinate multiple Web services.
Cloud Computing
Published in Vivek Kale, Enterprise Process Management Systems, 2018
The orchestration and choreography of Web services are enabled under three specification standards, namely, the Business Process Execution Language (BPEL) for Web Services, WS-Coordination, and WS-Transaction. These three specifications work together to form the bedrock for reliably choreographing Web service-based applications, providing BPM, transactional integrity, and generic coordination facilities. BPEL is a workflow-like definition language that describes sophisticated business processes that can orchestrate Web services. WS-Coordination and WS-Transaction complement BPEL to provide mechanisms for defining specific standard protocols for use by transaction processing systems, workflow systems, or other applications that wish to coordinate multiple Web services.
PDDL4J: a planning domain description library for java
Published in Journal of Experimental & Theoretical Artificial Intelligence, 2018
In many companies, information systems have to undertake activities such as accessing remote data, integrating heterogeneous data, analysing and deriving new data, etc. These activities are implemented as business processes controlling and interacting through different information flows. Usually, business processes are manually specified in languages such as BPEL in order to produce the adequate workflow in terms of data manipulations. Automated planning techniques have been used to automatically compose process skeletons (Hoffmann, Weber, & Kraft, 2009). Considered as a promising technique for Web Service Composition, several research works in non-deterministic planning have investigated how to extract planning models from existing industrial solutions (Hoffmann et al., 2009, Dongning, Zhihua, Yunfei, & Kangheng, 2010) and automatically connect the outputs of a process with the inputs of another Ambite and Kapoor (2007).
A decision support system for healthcare system quality improvement in blood centres: a case from Turkey
Published in Enterprise Information Systems, 2020
Web services choreography – Many applications consume more than a single service and service consumption requires specifying an order in which they should be consumed. Web services supported that functionality through Business Process Execution Language (BPEL), which allows the order in which a set of services should be accessed.