Architecting and designing : Business Process Analysis (BPA) : BPEL generation : BPEL to BPMN mapping reference : BPMN to BPEL mapping for Start Events
  
BPMN to BPEL mapping for Start Events
You can generate BPEL code for BPMN Start Events.
Pattern
BPMN comments
Only Abstract (Public) Processes are suitable for bpel synchronization.
In BPMN though the Start event can be used it is not necessary. Its use is merely to aid the reader in the navigation of the diagram; the Start event has no meaning or relevance in BPEL.
There must be ONLY one Start and at least one End Event on the diagram that is the starting point for the generation.
Children diagrams need not have any Start or End Events.
Note that in these patterns it is not necessary for the "BPMN Process"."Task Type" value to be specified since the pattern explicitly reads that the process is a "Receive" task type.
BPEL comments
1 If the patterns as depicted in Figure 1 or Figure 2 exist on a diagram then a <receive > element is created.
2 The message flow can ONLY originate from a Pool or Lane symbol and NOT any activity contained within the pool or lane symbol.
3 The ncname of the <receive name> attribute is taken from the name of the BPMN process that the Start event is connected to. "Business Process".Name
4 The ncname of the <partnerLink> attribute is derived from the pool or lane that the message symbol is connected from by examining the name of the definition used in the pool or lane's property Participant.Participant.name. If the Participant property is not populated then the name is taken from the pool or lane name Participant.name.
5 The qname of the "portType" is constructed from the message flow symbol definition, which is a "Class" definition as follows.
"Message Flow"."Port Type" gives a "Class" definition, in which its stereotype must be a " WSDL PortType" Determined from Class.Stereotype
The name of the "Class", Class.name is prefixed with the name of the "Namespace" property Class.Namespace and a colon.
6 The ncname of the <operation> is determined from the "Class" definition "Message Flow".Operation.name. The class stereotype must be a "WSDL Operation" determined from Class.Stereotype
7 The ncname of the <variable> is taken from the BPEL Variable definition contained in "Message Flow"."Input Variable".name
8 The createInstance attribute value is taken from the BPMN Process definition property "BPMN Process".Instantiate? and will be either a "yes" or "no"
9 The standard-attributes are determined from the respective Process or Event symbol that the Message flow is connected to.
Element construct
<receive>
name = "ncname"
partnerLink="ncname"
portType="qname"
operation="ncname"
variable="ncname"
createInstance="yes|no"
standard-attributes
<sapattern>
<guid>nnnnnnnnnnnn</guid>
<guid>nnnnnnnnnnnn</guid>
<guid>nnnnnnnnnnnn</guid>
</sapattern>
</receive>
See also
BPEL to BPMN mapping reference