Appendix E.1 Importing business process definitions for BPEL1.1

This section describes the support range of BPEL files and rules for converting to business process definitions for BPEL1.1.

Service Platform does not support some elements and attributes defined in the BPEL file for BPEL1.1. The following table indicates the elements and attributes defined in the BPEL file for BPEL1.1 that are supported or not supported in Service Platform.

Table E-2 Elements and attributes defined in the BPEL file for BPEL1.1 that are supported or not supported in Service Platform

CategoryElementLower element or attributeSupport range
Elements related to overall business process definitionsprocess elementname attributeN
targetNamespace attributeN
queryLanguage attributeN
expressionLanguage attributeN
suppressJoinFailure attributeN
enableInstanceCompensation attributeN
abstractProcess attributeN
partnerLinks elementN
partners elementN
correlationSets elementN
variables elementvariable elementname attributeY
messageType attributeY
type attributeY
element attributeN
faultHandlers elementcatch elementfaultName attributeN
faultVariable attributeY
activity#1Y
catchAll elementactivity#1Y
compensationHandler elementN
eventHandlers elementN
activity#1Y
Elements related to basic activitiesreceive elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
partnerLink attributeN
portType attributeN
operation attributeY
variable attributeY
createInstance attributeC
target elementN
source elementN
correlations elementN
reply elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
partnerLink attributeN
portType attributeN
operation attributeY
variable attributeY
faultName attributeY
target elementN
source elementN
correlations elementN
invoke elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
partnerLink attributeN
portType attributeY
operation attributeY
inputVariable attributeY
outputVariable attributeY
target elementN
source elementN
correlations elementN
catch elementfaultName attributeN
faultVariable attributeY
activity#1Y
catchAll elementactivity#1Y
assign elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
copy elementfrom elementvariable attributeY
expression attributeY
part attributeN
partnerLink attributeN
endpointReference attributeN
property attributeN
opaque attributeN
query attributeN
Tag value#2Y
to elementvariable attributeY
part attributeN
partnerLink attributeN
property attributeN
query attributeN
empty elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
throw elementfaultName attributeN
faultVariable attributeY
name attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
wait elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
for attributeY
until attributeY
terminate element#3name attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
compensate element#3name attributeY
joinCondition attributeN
suppressJoinFailure attributeN
scope attributeN
target elementN
source elementN
Elements related to structure activitiesscope elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
variableAccessSerializable attributeN
target elementN
source elementN
correlationSets elementN
variables elementvariable elementname attributeY
messageType attributeY
type attributeY
element attributeN
faultHandlers elementcatch elementfaultName attributeN
faultVariable attributeY
activity#1Y
catchAll elementactivity#1Y
compensationHandler elementN
eventHandlers elementN
activity#1Y
while elementname attributeY
joinCondition attributeN
condition attributeY
suppressJoinFailure attributeN
target elementN
source elementN
activity#1Y
switch elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
case elementcondition attributeY
activity#1Y
otherwise elementactivity#1Y
flow elementname attributeY
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
links elementN
activity#1Y
sequence elementname attributeN
joinCondition attributeN
suppressJoinFailure attributeN
target elementN
source elementN
activity#1Y
pick element#3name attributeY
joinCondition attributeN
suppressJoinFailure attributeN
createInstance attributeN
target elementN
source elementN
onAlarm elementN
onMessage elementN
Legend:
Y: Supported.
C: Supported, but with restrictions.
N: Not supported.
#1
In practice, elements such as receive, reply, and invoke are entered in activity.
#2
The tag value of the from element becomes the conversion source.
#3
Because this element is an unsupported activity, it is incorporated as an empty activity to which only the name attribute is applied.

Organization of this subsection
(1) Converting elements related to overall business process definitions
(2) Converting elements related to basic activities
(3) Converting elements related to structure activities

(1) Converting elements related to overall business process definitions

This subsection explains the conversion of the elements defined in the BPEL file that are the contents related to the overall business process (such as settings of the business process and variables used).

(a) Converting the process element

The process element and its lower elements and attributes are converted to the contents related to the overall business process definitions.

The following table describes the conversion details.

Table E-3 Converting the process element

Elements of the BPEL fileBusiness process definitions
Definition itemExplanation
process elementvariables elementVariableFor details, see (1)(b) Converting the variables element.
correlationSets elementCorrelation setFor details, see (1)(c) Converting the correlationSets element.
faultHandlers elementFault handlingFor details, see (1)(d) Converting the faultHandlers element.
activity#ActivityThis element is converted to activities that constitute a business process.
--Business process nameThis item is set to the business process name specified in the dialog box for adding a business process definition.
--Business process versionThis item is set to 1.
--PersistenceThis item is set to the persistence settings (persistent or non-persistent) specified in the dialog box for adding business process definitions.
Legend:
--: No corresponding element. Definition information is set automatically, or the information specified in the dialog box for adding business process definitions is set.
#
In reality, elements such as receive, reply, and invoke are entered in activity.

For practice about the elements converted to each activity of a business process, see (2) Converting elements related to basic activities and (3) Converting elements related to structure activities.

(b) Converting the variables element

The variables element and its lower elements and attributes are converted to definitions of the variables set in the business process (or in the scope). After importing the definitions, you can change the definitions in the List Of Variables And Correlation Sets dialog box.

Note
In Service Platform, the variables defined in the scopes above the scope that contains fault handling can be defined as the allocated variables of the activities that constitute the fault handling within the scope.
For this reason, if the elements below the scope or faultHandlers element in the BPEL file use the variables in the same scope element, redefine the allocated variables in the business process after importing the BPEL file.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the List Of Variables And Correlation Sets dialog box.

Table E-4 Converting the variables element

Lower element or attribute of the variables elementBusiness process definitions
ItemExplanation
variable elementname attributeVariable nameThis attribute is set to the name of the variable.
messageType attributeTypeIf this attribute has been defined, the type attribute is converted to the string type (string).
For this reason, after converting the attribute, you must change the variable type to the message type (XML), and register the message format.
type attributeTypeThis attribute is set to the following variable types:
  • For boolean
    boolean is set.
  • For a type that can be represented by double#
    numeric is set.
  • For other types or undefined types
    string is set.
--Part SpecificationsNo value is set in part specifications of a variable. To use part specifications, specify settings in the List Of Variables And Correlation Sets dialog box after importing the definitions.
Legend:
--: No corresponding element.
#
The following types are applicable:
int, short, byte, unsignedInt, unsignedShort, unsignedByte, float, double

(c) Converting the correlationSets element

The definition information of the correlationSets element corresponds to a correlation set in business process definitions. No value is set even if you create a business process by importing a BPEL file.

To use a correlation set in a business process, after importing the business process, first define a correlation set in the List Of Variables And Correlation Sets dialog box. Then, allocate the correlation set by using the Allocating Correlation Set Group dialog box for the activity that uses the correlation set.

(d) Converting the faultHandlers element

The faultHandlers element and its lower elements and attributes are converted to the definitions of the fault handling within the business process. You can change the converted definitions in the Fault Handler dialog box.

Note
  • If a faultHandlers element is defined immediately below the process element, a scope is created in the highest-level business process, and the faultHandlers element is defined as the fault handling in that scope. In such a case, the activities immediately below the process element are moved to the scope that has been created.
  • If a faultHandlers element is defined below the scope element, fault handling is set in the upper scope.

The table below describes the conversion details. The names listed in the Item column in the following table are the item names in the Fault Handler dialog box.

Table E-5 Converting the faultHandlers element

Lower element or attribute of the faultHandlers elementBusiness process definitions
ItemExplanation
catch elementfaultVariable attributeAllocated variableFor details about the variable, see also the notes in (1)(b) Converting the variables element.
activity#ActivityThis element is converted to activities that constitute a business process.
catchAll elementactivity#ActivityThis element is converted to activities that constitute a business process.
--Allocated variablecatch-all is set at all times.
--Transition destinationIf the catch or catchAll element is defined, the transition destination of the fault handling is set automatically.
Legend:
--: No corresponding element. Definitions are set automatically.
#
In reality, elements such as receive, reply, and invoke are entered in activity.

(2) Converting elements related to basic activities

This subsection explains the conversion of the elements defined in the BPEL file that are converted to basic activities.

(a) Converting the receive element

The receive element and its lower elements and attributes are converted to the definition contents of the receive activity. After importing the definitions, you can change the definitions in the Receive Activity dialog box.

Note
If more than one receive element that meets the following conditions is defined, the second and subsequent receive elements are converted to empty activities:
  • The portType attribute has the same value.
  • The operation attribute has the same value.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Receive Activity dialog box.

Table E-6 Converting the receive element

Lower element or attribute of the receive elementBusiness process definitions
ItemExplanation
operation attributeOperation nameIf a receive element with a different portType attribute value and the same operation attribute value is already defined, n (n is an integer value of 1 or more) is appended at the end of the operation name.
variable attributeAllocated variableFor details about the variable, see also the notes in (1)(b) Converting the variables element.
createInstance attributeInstance generationThis attribute is converted to yes, regardless of the attribute value.
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
--Communication modelSync or Async is set according to the contents of the business process definition.
Legend:
--: No corresponding element. Definitions are set automatically.

(b) Converting the reply element

The reply element and its lower elements and attributes are converted to the definition contents of the reply activity. After importing the definitions, you can change the definitions in the Reply Activity dialog box.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Reply Activity dialog box.

Table E-7 Converting the reply element

Lower element or attribute of the reply elementBusiness process definitions
ItemExplanation
operation attributeOperation nameIf n (n is an integer value of 1 or more) is appended at the end of the operation name of a receive element where the portType attribute value and the operation attribute value match (see the operation attribute in Table E-6), the same value n is also appended at the end of the operation name of the reply element.
Figure E-1 shows the conversion of a receive element and a reply element where the portType attribute value and the operation attribute value match.
variable attributeAllocated variableFor details about the variable, see also the notes in (1)(b) Converting the variables element.
faultName attributeFault nameThe fault name is converted to a local name if a prefix is assigned.
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.

Figure E-1 Conversion of a receive element and a reply element where the portType attribute value and the operation attribute value match

[Figure]

(c) Converting the invoke element

The invoke element and its lower elements and attributes are converted to the definition contents of the invoke service activity. Furthermore, if a catch element or catchAll element is defined as a lower element of the invoke element, these elements are converted to a fault handler (an activity connected with a fault connection) for the invoke service activity. After importing the definitions, you can change the definitions in the Invoke Service Activity dialog box or Fault Handler dialog box.

The table below describes the conversion details. The names listed in the Item column in the following table are the item names in the Invoke Service Activity dialog box or Fault Handler dialog box.

Table E-8 Converting the invoke element

Lower element or attribute of the invoke elementBusiness process definitions
ItemExplanation
portType attributeService nameThis attribute is converted only when the corresponding service components and operations exist in the repository. The service name is converted to a local name.
operation attributeOperation nameThis attribute is converted only when the corresponding service components and operations exist in the repository.
inputVariable attributeBody allocated variable for request messageThis attribute is set only when the corresponding service components and operations exist in the repository.
For details about the variable, see also the notes in (1)(b) Converting the variables element.
outputVariable attributeBody allocated variable for reply messageThis attribute is set when the service components and operations exist in the repository, and the communication type is synchronous.
For details about the variable, see also the notes in (1)(b) Converting the variables element.
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
catch elementfaultVariable attributeAllocated variableThis element is an item in the Fault Handler dialog box.
For details about the variable, see also the notes in (1)(b) Converting the variables element.
activity#ActivityThis element is converted to activities that constitute a business process.
catchAll elementactivity#ActivityThis element is converted to activities that constitute a business process.
--Allocated variableThis element is an item in the Fault Handler dialog box.
catch-all is set at all times.
Legend:
--: No corresponding element. Definitions are set automatically.
#
In practice, elements such as receive, reply, and invoke are entered in activity.

(d) Converting the assign element

The assign element and its lower elements and attributes are converted to the definition contents of the assign activity. After importing the definitions, you can change the definitions in the Assign Activity dialog box or Assign Activity sub-dialog box.

The table below describes the conversion details. The names listed in the Item column in the following table are the item names in the Assign Activity dialog box or Assign Activity sub-dialog box.

Table E-9 Converting the assign element

Lower element or attribute of the assign elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
copy elementfrom elementvariable attributeName (under Variable in the Copy source frame)This attribute is an item in the Assign Activity sub-dialog box.
For details about the variable, see also the notes in (1)(b) Converting the variables element.
expression attributeValue (under Expression in the Copy source frame)This attribute is an item in the Assign Activity sub-dialog box.
This attribute is not converted if the variable attribute has been defined.
Tag value#Value (under Expression in the Copy source frame)This attribute is an item in the Assign Activity sub-dialog box.
If the variable and expression attributes are not defined, the tag value is set as the value of the expression.
to elementvariable attributeVariable name (in the Copy destination frame)This attribute is an item in the Assign Activity sub-dialog box.
For details about the variable, see also the notes in (1)(b) Converting the variables element.
#
The tag value of the from element becomes the conversion source.

(e) Converting the empty element

The empty element is converted to the definition contents of the empty activity. After importing the definitions, you can change the definitions in the Empty Activity dialog box.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Empty Activity dialog box.

Table E-10 Converting the empty element

Lower element or attribute of the empty elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
(f) Converting the throw element

The throw element and its lower elements and attributes are converted to the definition contents of the throw activity. After importing the definitions, you can change the definitions in the Throw Activity dialog box.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Throw Activity dialog box.

Table E-11 Converting the throw element

Lower element or attribute of the throw elementBusiness process definitions
ItemExplanation
faultVariable attributeAllocated variableFor details about the variable, see also the notes in (1)(b) Converting the variables element.
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
(g) Converting the wait element

The wait element is converted to the definition contents of the standby activity. After importing the definitions, you can change the definitions in the Wait Activity dialog box.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Wait Activity dialog box.

Table E-12 Converting the wait element

Lower element or attribute of the wait elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
for attribute#ExpressionThis attribute sets information about the standby interval. The For radio button is selected.
until attribute#ExpressionThis attribute sets information about the standby time period. The Until radio button is selected.
#
If both the for attribute and the until attribute are defined, the for attribute is enabled and the until attribute is disabled. If neither the for attribute nor the until attribute is defined, the For radio button is selected.

(3) Converting elements related to structure activities

This subsection explains the conversion of the elements defined in the BPEL file that are converted to structure activities.

(a) Converting the scope element

The scope element and its lower elements and attributes are converted to the definition contents of the scope activity. After importing the definitions, you can change the definitions in the Scope Activity dialog box.

Furthermore, the variables, correlation sets, fault handling, and transaction control information defined within the scope element can be changed in the List Of Variables And Correlation Sets dialog box and Fault Handler dialog box.

The following table describes the conversion details.

Table E-13 Converting the scope element

Lower element or attribute of the scope elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
--Transaction controlThis item specifies whether to execute transaction control. Commit after each activity is selected by default.
variables elementVariableThis element sets information about the variables used in the scope.
For details about variables, see (1)(b) Converting the variables element.
correlationSets elementCorrelation setThis element sets information about the correlation sets used in the scope.
For details about correlation sets, see (1)(c) Converting the correlationSets element.
faultHandlers elementFault handlingThis item sets information about the fault handling in the scope.
For details about fault handling, see (1)(d) Converting the faultHandlers element.
activity#ActivityThis element is converted to activities that constitute a business process.
Legend:
--: No corresponding element. Definitions are set automatically.
#
In practice, elements such as receive, reply, and invoke are entered in activity.

(b) Converting the while element

The while element and its lower elements and attributes are converted to the definition contents of the while activity. After importing the definitions, you can change the definitions in the While Activity dialog box and Condition Setting dialog box.

The table below shows the conversion details. The names listed in the Item column in the following table are the item names in the While Activity dialog box or Condition Setting dialog box.

Table E-14 Converting the while element

Lower element or attribute of the while elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
condition attributeCondition ExpressionValues are set in the conditional expression in the Condition Setting dialog box.
activity#ActivityThis element is converted to activities that constitute a business process.
--Max Loop CountThis item is automatically set to 100.
Legend:
--: No corresponding element. Definitions are set automatically.
#
In practice, elements such as receive, reply, and invoke are entered in activity.

(c) Converting the switch element

The switch element and its lower elements and attributes are converted to the definition contents of the switch start activity. After importing the definitions, you can change the definitions in the Switch Activity dialog box and Condition Setting dialog box.

Note
A switch end activity is set automatically when the elements below the switch element are converted to a switch start activity. In such a case, _end is added to the name of the switch start activity to assign a name to the switch end activity.

The table below describes the conversion details. The names listed in the Item column in the following table are the item names in the Switch Activity dialog box or Condition Setting dialog box.

Table E-15 Converting the switch element

Lower element or attribute of the switch elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
case elementactivity#ActivityThis element is converted to activities that constitute a business process.
condition attributeCondition ExpressionValues are set in the conditional expression in the Condition Setting dialog box.
--Condition nameThis attribute is an item in the Switch Activity dialog box.
This item is automatically set to condition n. n indicates a unique integer within the switch.
--PriorityThis attribute is an item in the Switch Activity dialog box.
Priorities are assigned according to the occurrence order of the conditions within the switch element.
otherwise elementactivity#ActivityThis element is converted to activities that constitute a business process.
--PriorityThis attribute is an item in the Switch Activity dialog box.
This item is set to the default value.
--Transition destinationThis attribute is an item in the Switch Activity dialog box.
This item is set according to the definitions of the case and otherwise elements.
Legend:
--: No corresponding element. Definitions are set automatically.
#
In practice, elements such as receive, reply, and invoke are entered in activity.

(d) Converting the flow element

The flow element and its lower elements and attributes are converted to the definition contents of the flow start activity. After importing the definitions, you can change the definitions in the Flow Start Activity dialog box.

Note
  • The link definitions (definitions below the links element in the BPEL file) are not converted.
  • A flow end activity is set automatically when the elements below the flow element are converted to a flow start activity. In such a case, _end is added to the name of the flow start activity to assign a name to the flow end activity.

The table below describes the conversion details. The names in the Item column in the following table are the item names in the Flow Activity dialog box.

Table E-16 Converting the flow element

Lower element or attribute of the flow elementBusiness process definitions
ItemExplanation
name attributeActivity nameAn activity name is set. If an activity with the same name is already defined in the business process, n (n is an integer value of 1 or more) is appended at the end of the activity name.
activity#ActivityThis element is converted to activities that constitute a business process.
#
In practice, elements such as receive, reply, and invoke are entered in activity.

(e) Converting the sequence element

The sequence element is converted to the definition contents of the sequence activity. You cannot modify the definition contents.

The sequence element does not have any lower attributes to be converted.

In Service Platform, only the sequence elements specified at the positions described in 5.6.17 Sequence Activity are converted to business process definitions.