A Pick activity is a structured BPEL and is pa rt of our process definition, and a Pick activity can contain one or more OnMessage and OnAl arm activities.
Used to have the process wait until one of a set
of events is triggered
– Message events via onMessage element
– Alarm events via onAlarmelement And Plays a role in the lifecycle of a business
process
– If createInstance="yes"
z Instructs the BPEL engine to create a new process instance
z As a result of receiving one of a set of possible messages
– Each onMessage is equivalent to a receiveactivity
with the createInstance="yes"
– No alarms are permitted in this case
The Pick activity forces the process to wait until one of a set of events is triggered.
All of these events are eith er onMessage elements or onAlarm elements. You canhave as many onMessage and onAlarm activities as you want, but exactly one of them will be executed. Once one event is executed, all others are disabled. A Pick Activity can create an instance in response to an onEvent, making it equivalent to a Receive activity, but no onAlarm events are permitted in the Pick if doing so. Note that it is the Pick that is creat ing the instance, not the onMessage.
Here is the syntax of the Pick activity. Fi rst, the attribute for “createInstance” is setto either yes or no, and then we have all the standard attributes and elementsThen we have the optional onMessage definitions, which require the PartnerLink, PortType, Operation and the optional variable and optional messageExchange.
Following that, we have the Correlation Sets, with the initiate attribute choices of yes/no and join, because the Pick is part of our partner conversations, so they have to be correlated. Then we have the From pa rts with their variable, followed by the primary activity of the onMessage element. Finally, we have our onAlarm activity, which has the expression language and the expression itself for our deadline or duration elements, followed by the onAlarm’s primary activity.
Used to have the process wait until one of a set
of events is triggered
– Message events via onMessage element
– Alarm events via onAlarmelement And Plays a role in the lifecycle of a business
process
– If createInstance="yes"
z Instructs the BPEL engine to create a new process instance
z As a result of receiving one of a set of possible messages
– Each onMessage is equivalent to a receiveactivity
with the createInstance="yes"
– No alarms are permitted in this case
The Pick activity forces the process to wait until one of a set of events is triggered.
All of these events are eith er onMessage elements or onAlarm elements. You canhave as many onMessage and onAlarm activities as you want, but exactly one of them will be executed. Once one event is executed, all others are disabled. A Pick Activity can create an instance in response to an onEvent, making it equivalent to a Receive activity, but no onAlarm events are permitted in the Pick if doing so. Note that it is the Pick that is creat ing the instance, not the onMessage.
Here is the syntax of the Pick activity. Fi rst, the attribute for “createInstance” is setto either yes or no, and then we have all the standard attributes and elementsThen we have the optional onMessage definitions, which require the PartnerLink, PortType, Operation and the optional variable and optional messageExchange.
Following that, we have the Correlation Sets, with the initiate attribute choices of yes/no and join, because the Pick is part of our partner conversations, so they have to be correlated. Then we have the From pa rts with their variable, followed by the primary activity of the onMessage element. Finally, we have our onAlarm activity, which has the expression language and the expression itself for our deadline or duration elements, followed by the onAlarm’s primary activity.
