Index
A
- <assign> activity / Data manipulation and assignments
- activities
- activity / Understanding the BPEL language
- alarm event handler
- alarm events
- AnotherBookstoreBPEL process
- arrays
- assignments
- asynchronous BPEL process
- asynchronous BPEL processes / What just happened?
- asynchronous example
- asynchronous invocation, implementing
- asynchronous invocations
- asynchronous process
- asynchronous service invocations
- asynchronous web service invocation
B
- BookOrderManagement process
- BookshelfEvent
- Book Shelving BPEL process
- BookShelvingBPEL process
- bookstore
- BookstoreAResponse activity / What just happened?
- Bookstore BPEL process
- book warehousing BPEL
- BookWarehousingBPEL
- BookWarehousingBPEL process
- Book Warehousing BPEL process
- BookWarehousing process
- book warehousing process
- BPEL
- bpel$doXslTransform() function / The XSLT transformations
- BPEL activities
- BPEL code
- BPEL language
- BPEL process
- ending / Ending a process, Ending and terminating a BPEL process
- empty activities / Empty activities
- faults, signaling from / Signaling faults within the BPEL process
- terminating / Ending and terminating a BPEL process
- fault handlers, adding / Have a go hero – adding fault handlers to BPEL process
- restructuring, into scopes / Have a go hero – restructuring a BPEL process into scopes
- response variable, constructing / Constructing the response variable of the BPEL process
- human task, invoking from / Invoking a human task from the BPEL process, Time for action – invoking a human task from the BPEL process, What just happened?
- event-driven BPEL process, developing / Developing an event-driven BPEL process
- business event, triggering from / Triggering a business event from a BPEL process
- event handler, adding / Time for action – adding an event handler to the BPEL process, What just happened?
- message event handler, adding / Time for action – adding a message handler to the BPEL process, What just happened?
- fault, triggering within / Time for action – triggering a fault within the BPEL process, What just happened?
- compensation, initiating for scopes / Initiating a compensation for scopes within a BPEL process
- compensation, triggering for / Time for action – triggering compensation for the BPEL process, What just happened?
- BPEL process interface
- BPEL runtime fault handler, selecting
- BPEL structure
- branches
- business events
- business processes
- business process faults
C
D
- data
- data copying
- data manipulation
- data manipulation, for external partner links
- dateTime expressions
- dateTime expressions, alarm events / Alarm events
- deadline expressions
- deadline expressions, alarm events
- default domain
- delays
- duration expressions
- duration expressions, alarm events
- dynamic parallel invocations
- dynamic partner link
E
- EDA
- element option / Variable types
- empty activities / Empty activities
- empty WS BPEL 2.0 process
- environment
- event-driven book shelving BPEL process
- event-driven BPEL process
- event handler
- events
- example
- execution errors / Faults thrown from the business process
- existing variables
- exitOnStandardFault attribute, <process> tag / <process>
- expressionLanguage attribute, <process> tag / <process>
- expressions
- external party
- external web services fault
F
- <faultHandler> activity / Triggering compensation handlers
- <flow> activity
- <forEach> activity
- <forEach> loop
- fault
- faultElement attribute / Configuring a fault handler
- fault handler
- fault handling
- fault handling logic
- faultMessageType attribute / Configuring a fault handler
- faultName attribute / Configuring a fault handler
- faults
- about / Introducing faults and fault handlers
- communication, issues / Communication issues
- contract, issues / Contract issues
- thrown, from external web service / Faults thrown from the external web service
- thrown, from business process / Faults thrown from the business process
- WS-BPEL 2.0 standard faults / Modeling execution errors with WS-BPEL 2.0 standard faults
- <throw> activity / Modeling logical (explicit) errors with the <throw> activity
- external web services / Modeling errors propagated from external web services
- WSDL faults / Modeling errors propagated from external web services
- handling, logic / Handling faults
- propagating, to parent scopes / Propagating faults to parent scopes
- signaling / Time for action – signaling faults
- signaling, to external party / Time for action – signaling faults, What just happened?
- signaling, within BPEL process / Signaling faults within the BPEL process
- signaling, to synchronous clients / Signaling faults to the synchronous clients
- signaling, from asynchronous process / Signaling faults from the asynchronous process
- BPEL process, ending / Ending and terminating a BPEL process
- BPEL process, terminating / Ending and terminating a BPEL process
- faultVariable attribute / Configuring a fault handler
- first BPEL process
- for, <wait> activity / Delays
- for each loop
G
H
- handler, types
- human task
- human task, BookWarehousingBPEL process
- human task definition, creating / Creating a human task definition, Time for action – creating a human task definition, What just happened?
- human task, configuring / Configuring human tasks
- human task, invoking from BPEL process / Invoking a human task from the BPEL process, Time for action – invoking a human task from the BPEL process, What just happened?
- human task case branches, configuring / Configuring human task case branches, Time for action – configuring human task case branches
- human tasks forms, creating / Creating human task forms, Time for action – creating human task forms
- human task case branches
- human task configuration
- human task deadlines
- human task definition
- human task notifications
- human task payload
- human tasks
- human tasks forms
- human task title
I
- <if> activity
- <invoke>
- <invoke> activity
- <invoke>activity
- ignoreMissingFromData attribute / Optional attributes
- in-line fault handling
- initializePartnerRole, partner link / Defining partner links
- input variable
- inputVariable activity / What just happened?
- Integrated Development Environments (IDEs) / Introduction to BPEL
- invocation logic, <forEach> activity
- invoke activity
- invoked partner links
- ISO 8601 lexical format / Alarm events
- isolated scopes
- ISO web page
J
K
L
M
- message correlation
- message event activities
- message event handler
- message events
- messageType option / Variable types
- multiple values
- myRole
- myRole, partner link / Defining partner links
N
O
P
Q
R
- <receive> activity / <receive> and <reply>, <receive>
- <repeatUntil> loop
- <reply> activity
- receive activity
- Reference Schema, WS-BPEL 2.0
- repeat until loop
- response messages
- response variable
S
T
- <throw> activity
- targetNamespace attribute, <process> tag / <process>
- termination handler
- type option / Variable types
U
V
W
- <wait> activity
- <while> loop
- WarehousingConfirmation service
- warehousing process
- WebLogic
- while loop
- worklist application / Worklist application
- WS-Addressing schema
- WS-BPEL 2.0
- WS-BPEL 2.0 standard faults
- WSDL
- WSDL faults
- WSDL message property
- WSDL messages / Variable types
- WSDL message type variable
X
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.