uCosminexus Service Platform, Basic Development Guide
(1) Process
The attribute targetNamespace of the element [process] is not supported and, hence, not applied.
- On the Cosminexus Service Platform, the fixed value reserved for the system is always used as the targetNamespace attribute value. Even if the targetNamespace attribute value is specified, when the BPEL file is imported, the value is replaced by the fixed value reserved for the system.
- Output conditions
- When the targetNamespace attribute is defined
- Action
- Does not affect the execution of the business process. Specific action need not be taken.
The element [process] attribute enableInstanceCompensation is not supported and, hence, not applied.
- On the Cosminexus Service Platform, the enableInstanceCompensation attribute (instance correction) is not supported. Therefore, the operation is always the same as when "no" is specified in the enableInstanceCompensation attribute.
Note that in the case of BPEL 1.1, the default value of the enableInstanceCompensation attribute is "no". In the case of BPEL 2.0, the enableInstanceCompensation attribute cannot be specified.
- Output conditions
- When the enableInstanceCompensation attribute is defined
- Action
- When this message is output, check the specification of the enableInstanceCompensation attribute in the BPEL file and take action from the following viewpoints:
- When "no" is specified in the enableInstanceCompensation attribute
The operation is same as that on the Cosminexus Service Platform. Specific action need not be taken.
- When "yes" is specified in the enableInstanceCompensation attribute
When the BPEL file is imported, the specification of the enableInstanceCompensation attribute is replaced by "no". Therefore, if the flow is designed assuming instance correction, the execution results of the business process might differ. Open the imported business process in a business process editor and review whether the business process is defined for the intended details.
- The details of the instance correction depend on the header. If the business process is created assuming instance correction, sometimes the runtime compatibility cannot be guaranteed.
- Therefore, either do not specify the enableInstanceCompensation attribute from the upper-level design stage, or design the process by specifying "no".
The element [process] attribute abstractProcess is not supported and, hence, not applied.
- On the Cosminexus Service Platform, the abstractProcess attribute is not supported. The Cosminexus Service Platform always targets the business processes with executable implementation level. Therefore, the operation is always the same as when "no" is specified for the abstractProcess attribute.
Note that in the case of BPEL 1.1, the default value of the abstractProcess attribute is "no". In the case of BPEL 2.0, the abstractProcess attribute cannot be specified.
- Output conditions
- When the abstractProcess attribute is defined
- Action
- When this message is output, check the specification of the abstractProcess attribute in the BPEL file and take action from the following viewpoint:
- When "no" is specified for the abstractProcess attribute
The operation is the same as on the Cosminexus Service Platform. Specific action need not be taken.
- When "yes" is specified for the abstractProcess attribute
The business process might be of a non-executable abstract level. Open the imported business process using a business process editor and review the business process definition.
(2) Partner link
The element [partnerLinks] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- On the Cosminexus Service Platform, the partnerLinks attribute is not supported. When the BPEL file is imported, the partnerLinks element indicating the relationship between the business process and the external service is not fetched.
- Output conditions
- When the partnerLinks element is defined
- Action
- Does not affect the execution of the business process. Specific action need not be taken.
- On the Cosminexus Service Platform, the partner link information of the BPEL file corresponds to the user-defined reception and service adapter.
- As and when required, create the user-defined reception and service adapter from the WSDL file that makes a set with the BPEL file.
- See the actions for the following messages as well:
-
(3) Variable or correlation set (variable)
The variable {variable-name} was replaced by the string type. Change the variable type to messageType and register the message format.
- When the BPEL file is imported, a structured message is not fetched as a variable.
In the high level design tools, specify only the name of the message (variable) and define the message structure when you enter the detailed design phase.
- Output conditions
- When the messageType attribute of the variable element is defined
- Action
- After importing the BPEL file, change the variable type into messageType using the business process editor and then specify the schema file.
The variable {variable-name} type {old-variable-type} must belong to the namespace "http://www.w3.org/2001/XMLSchema". The type is applied as the {new-variable-type} type, but check whether there is a problem.
- The types that are not defined in the XML schema namespace are specified in the variable. The variable is fetched after the type is replaced by a type that is presumed to be compatible.
- Output conditions
- When a type that is not defined in the XML schema namespace is specified in the variable
- Action
- Check whether the replaced variable type affects the business process. As and when required, import the BPEL file and then review the variable types using the business process editor.
-
(4) Variable or correlation set (correlation set)
The element [correlationSets] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- When the BPEL file imported, the correlationSets element defining the correlation set is not fetched.
Do not define the correlation set in the high level design tools.
- Output conditions
- When the correlationSets element is defined
- Action
- After importing the BPEL file, redefine the correlation set using the business process editor.
-
(5) Activity (receive)
The attribute partnerLink of the element [receive] is not supported and, hence, not applied.
- When the BPEL file is import, the partnerLink attribute is not fetched.
- Output conditions
- When the partnerLink attribute is defined
- Action
- Need not be a cause for concern within the usage of standard reception.
- The partnerLink attribute of the receive element is equivalent to the user-defined reception on the Cosminexus Service Platform.
- As and when required, import the BPEL file and then create the user-defined reception from the WSDL file of the business process.
The attribute portType of the element [receive] is not supported and, hence, not applied.
- When the BPEL file is imported, the portType attribute is not fetched.
- Output conditions
- When the portType attribute is defined
- Action
- The portType attribute is specified for the readability of the BPEL file and WSDL file. Does not affect the execution of the business process. Specific action need not be taken.
The operation name of the activity [receive] is repeated and, therefore, replaced by {operation-name}.
- The same operation name is specified for multiple receive elements having different portType attribute values. The operation name is replaced such that the name is not repeated when the BPEL file is imported and then fetched.
- Output conditions
- When the same operation name is specified for multiple receive elements having different portType attribute values
- Action
- Does not affect the execution of the business process. Specific action need not be taken. However, the operation name might not match the business process WSDL; therefore, as and when required, change the operation name using the business process editor.
The receive activity [receive] was replaced with an empty activity since an activity with the same portType and operation already exists.
- The same operation name was specified for multiple receive elements having the same portType attribute values. When the BPEL file is imported, the second and subsequent receive elements are replaced by empty activities and then fetched.
- Output conditions
- When the same operation name was specified for multiple receive elements having the same portType attribute values
- Action
- Import the BPEL file and then redefine the empty activity as an appropriate receive activity.
The value "no" specified in the attribute [createInstance] of the element [receive] is replaced with "yes".
- When the BPEL file is imported, the createInstance attribute of the receive element is always fetched as "yes".
- Output conditions
- When the createInstance attribute is not specified
- When "no" is specified for the createInstance attribute
- Action
- Import the BPEL file and then re-specify the instance generation for the receive activity.
The element [correlations] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- When the BPEL file is imported, the correlations element specifying the correlation set is not fetched. Do not specify the correlation set in the high level design tools.
- Output conditions
- When the correlations element is defined
- Action
- Import the BPEL file and then specify the correlation set using the business process editor.
-
(6) Activity (reply)
The attribute partnerLink of the element [reply] is not supported and, hence, not applied.
- When the BPEL file is imported, the partnerLink attribute is not fetched.
- Output conditions
- When the partnerLink attribute is defined
- Action
- On the Cosminexus Service Platform, the partnerLink attribute of the reply element is equivalent to the user-defined reception.
- If necessary, import the BPEL file and then create the user-defined reception from the WSDL file of the business process.
The attribute portType of the element [reply] is not supported and, hence, not applied.
- When the BPEL file is imported, the portType attribute is not fetched.
- Output conditions
- When the portType attribute is defined
- Action
- The portType attribute is specified for the readability of the BPEL file and WSDL file. Does not affect the execution of the business process. Specific action need not be taken.
The value {namespace}:{local-name} specified in the attribute faultName of the element [reply] was replaced by {local-name}.
- On the Cosminexus Service Platform, the fault namespace is not supported by default.
If the fault namespace is specified in the BPEL file, only the local name is fetched.
- Output conditions
- When the namespace is specified in the faultName attribute value
- Action
- When the standard reception is used, the fault message only stores the local name.
- When the user-defined reception is used, the fault message stores both, the namespace and the local name.
- As and when required, create the user-defined reception from the WSDL file of the business process such that the fault message conforms to the business process interface.
The operation name of the activity [reply] is repeated and, therefore, replaced by {operation-name}.
- The same operation name is specified for multiple reply elements having different portType attribute values. The operation name is replaced such that the name is not repeated when the BPEL file is imported and then fetched.
- Output conditions
- When the same operation name is specified for multiple reply elements having different portType attribute values
- Action
- Does not affect the execution of the business process. Specific action need not be taken. However, the operation name might not match the business process WSDL; therefore, as and when required, change the operation name using the business process editor.
The element [correlations] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- When the BPEL file is imported, the correlations element specifying the correlation set is not fetched. Do not specify the correlation set in the high level design tools.
- Output conditions
- When the correlations element is defined
- Action
- Import the BPEL file and then specify the correlation set using the business process editor.
-
(7) Activity (assign)
The attribute part of the element [assign/copy/from] is not supported and, hence, not applied.
- When the BPEL file is imported, the part attribute is not fetched.
In the high level design tools, specify only the name of the message (variable) and define the message structure when you enter the detailed design phase.
- Output conditions
- When the part attribute is defined
- Action
- Import the BPEL file and then define the message structure and specify the parts using the business process editor.
The attribute part of the element [assign/copy/to] is not supported and, hence, not applied.
- When the BPEL file is imported, the part attribute is not fetched.
In the high level design tools, specify only the name of the message (variable) and define the message structure when you enter the detailed design phase.
- Output conditions
- When the part attribute is defined
- Action
- Import the BPEL file and then define the message structure and specify the parts using the business process editor.
The copy element of the assign activity [assign] is not applied because the format of the attributes defined in copy/from is not supported.
- To fetch the copy element of the assign activity, the attributes of the copy/from element must be defined in a fetchable combination.
For details about the fetchable combinations, see Appendix E. Support Range of BPEL Used by Linking with an High Level Design Tool.
- Output conditions
- When the attributes of the copy/from element are defined using an unfetchable combination
- Action
- Import the BPEL file and then redefine the assign settings for the assign activity.
The to element of the assign activity [assign] is not applied because the format of the attributes defined in copy/to is not supported.
- To fetch the to element of the assign activity, the attributes of the copy/to element must be defined in a fetchable combination.
For details about the fetchable combinations, see Appendix E. Support Range of BPEL Used by Linking with an High Level Design Tool.
- Output conditions
- When the attributes of the copy/to element are defined using an unfetchable combination
- Action
- Import the BPEL file and then redefine the assign settings for the assign activity.
-
(8) Activity (invoke)
The attribute partnerLink of the element [invoke] is not supported and, hence, not applied.
- When the BPEL file is imported, the partnerLink attribute is not fetched.
- Output conditions
- When the partnerLink attribute is defined
- Action
- On the Cosminexus Service Platform, the partnerLink attribute of the invoke element is equivalent to the service adapter.
- If a service adapter corresponding to the partnerLink attribute is already created, specific action need not be taken.
The applicable service or operation does not exist in the repository; therefore, the service name {service-name} specified in portType of the invoke activity [invoke] is not applied.
- If the service adapter corresponding to the portType attribute and operation attribute does not exist in the repository, the portType attribute is not fetched.
- Output conditions
- When the service adapter corresponding to the portType attribute does not exist in the repository
- When the service adapter corresponding to the portType attribute does not have an operation corresponding to the operation attribute
- Action
- Create the corresponding service adapter and re-set the service name of the invoke activity.
The applicable service or operation does not exist in the repository; therefore, the operation name {operation-name} specified in operation of the invoke activity [invoke] is not applied.
- If the service adapter corresponding to the portType attribute and operation attribute does not exist in the repository, the operation attribute is not fetched.
- Output conditions
- When the service adapter corresponding to the portType attribute does not exist in the repository
- When the service adapter corresponding to the portType attribute does not have an operation corresponding to the operation attribute
- Action
- Create the corresponding service adapter and re-set the operation name of the invoke activity.
The value {variable-name} of the attribute inputVariable specified in the invoke activity [invoke] is not applied because the corresponding operation {operation-name} does not exist in the repository.
- If the service adapter corresponding to the portType attribute and operation attribute does not exist in the repository, the inputVariable attribute is not fetched.
- Output conditions
- When the service adapter corresponding to the portType attribute does not exist in the repository
- When the service adapter corresponding to the portType attribute does not have an operation corresponding to the operation attribute
- Action
- Create the corresponding service adapter and reset the allocation variable for the request message of the invoke activity.
The value {variable-name} of the attribute outputVariable specified in the invoke activity [invoke] is not applied because the corresponding operation {operation-name} does not exist in the repository.
- If the service adapter corresponding to the portType attribute and operation attribute does not exist in the repository, the outputVariable attribute is not fetched.
- Output conditions
- When the service adapter corresponding to the portType attribute does not exist in the repository
- When the service adapter corresponding to the portType attribute does not have an operation corresponding to the operation attribute
- Action
- Create the corresponding service adapter and reset the allocation variable for the response message of the invoke activity.
The value {variable-name} of the attribute outputVariable specified in the invoke activity [invoke] is not applied because the operation {operation-name} of the service {service-name} in the repository is asynchronous.
- If the communication method of the operation for the invocation destination service is asynchronous, the response message is not required; therefore, the outputVariable attribute is not fetched.
- Output conditions
- When the communication method of the operation for the invocation destination service is asynchronous and the outputVariable attribute is defined
- Action
- The BPEL file and WSDL file used as input might not be consistent. Check whether the asynchronous communication method of operation is acceptable.
The attribute faultName of the element [invoke/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultName attribute.
- Output conditions
- When the faultName attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using a business process editor.
The attribute faultMessageType of the element [invoke/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultMessageType attribute.
- Output conditions
- When the faultMessageType attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using a business process editor.
The attribute faultElement of the element [invoke/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultElement attribute.
- Output conditions
- When the faultElement attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using a business process editor.
The element [correlations] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- When the BPEL file is imported, the correlations element specifying the correlation set is not fetched.
Do not specify the correlation set in the high level design tools.
- Output conditions
- When the correlations element is defined
- Action
- Import the BPEL file and then specify the correlation set using the business process editor.
-
(9) Activity (flow)
The element [flow/links] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- When the BPEL file is imported, the links element specifying the link is not fetched.
Do not specify the link in the high level design tools.
- Output conditions
- When the links element is defined
- Action
- Import the BPEL file and then specify the link using the business process editor.
-
(10) Activity (throw)
The attribute faultName of the element [throw] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault throwing using the faultName attribute.
- Output conditions
- When the faultName attribute is defined
- Action
- Import the BPEL file and then set up fault throwing using the business process editor.
-
(11) Activity (general)
The name of the activity [someElement] is repeated and, therefore, replaced by {new-name}.
- On the Cosminexus Service Platform, the activity name (name attribute) cannot be repeated.
If the activity name is repeated when the BPEL file is imported, a number is added to the end of the activity name and then the activity is fetched. The number is sequentially specified from 1.
- Output conditions
- When the activity name (name attribute) is repeated
- Action
- The activity name is used for the output of the execution log for the operating environment and the execution environment log. As and when required, change the activity name.
The element [someElement] is not supported and, hence, replaced by an empty activity. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- The Cosminexus Service Platform does not support the activities described in [someElement].
When the BPEL file is imported, [someElement] is replaced by an empty activity and then fetched.
- Output conditions
- When an unsupported activity is defined
- Action
- Replace the processing by an activity supported on the Cosminexus Service Platform.
-
(12) Handler (compensation handler)
The element [compensationHandler] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- The Cosminexus Service Platform does not support the compensationHandler element.
- Output conditions
- When the compensationHandler element is defined
- Action
- Replace the processing by an activity supported on the Cosminexus Service Platform.
-
(13) Handler (event handler)
The element [eventHandler] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- The Cosminexus Service Platform does not support the eventHandler element.
- Output conditions
- When the eventHandler element is defined
- Action
- Replace the processing by an activity supported on the Cosminexus Service Platform.
-
(14) Handler (termination handler)
The element [terminationHandler] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- The Cosminexus Service Platform does not support the terminationHandler element.
- Output conditions
- When the terminationHandler element is defined
- Action
- Replace the processing by an activity supported on the Cosminexus Service Platform.
-
(15) Handler (fault handler)
FaultHandlers [faultHandlers] are not applied because catch/catchAll is not defined.
- The fault handlers in which one or more catch or catchAll is not defined are not fetched.
- Output conditions
- When one or more catch element or catchAll element are not defined in the faultHandler element
- Action
- Does not affect the execution of the business process. Specific action need not be taken.
The attribute faultName of the element [faultHandlers/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultName attribute.
- Output conditions
- When the faultName attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using the business process editor.
The attribute faultMessageType of the element [faultHandlers/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultMessageType attribute.
- Output conditions
- When the faultMessageType attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using the business process editor.
The attribute faultElement of the element [faultHandlers/catch] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support fault catching using the faultElement attribute.
- Output conditions
- When the faultElement attribute is defined
- Action
- Import the BPEL file and then re-set fault catching using the business process editor.
-
The value no specified in the attribute suppressJoinFailure of the element [someElement] is replaced by yes.
- The Cosminexus Service Platform does not support the suppressJoinFailure attribute. Therefore, the bpws:joinFailure fault is always controlled and the operation is the same as when "yes" is specified for the suppressJoinFailure attribute.
Note that in the case of BPEL 1.1 and BPEL 2.0, the default value of the suppressJoinFailure attribute is "no".
- Output conditions
- When the suppressJoinFailure attribute is not specified
- When "no" is specified for the suppressJoinFailure attribute
- Action
- When the BPEL file is imported, the specification of the suppressJoinFailure attribute is replaced by "yes". Therefore, the execution results of the business process might differ. Open the BPEL file in the business process editor and review whether the business process is defined for the intended details.
- Note
- The operations of the business process differ depending on the value of the suppressJoinFailure attribute.
- On the Cosminexus Service Platform, operations are always executed with the suppressJoinFailure attribute as "yes"; therefore, if joinCondition of the activity is not fulfilled, the business process goes into an interrupted state that cannot be restarted immediately.
- In an environment where the suppressJoinFailure attribute is operated as "no", if joinCondition is not fulfilled, the bpws:joinFailure fault is thrown, but the processing continues according to the defined business process.
- The following figure shows the relationship between the specification of the suppressJoinFailure attribute and bpws:joinFailure:
Figure C-4 Relationship between the specification of the suppressJoinFailure attribute and bpws:joinFailure
- When the suppressJoinFailure attribute is "no":
- When joinFailure occurs at (1), joinFailure is propagated to the upper scope. In this example, joinFailure is propagated in the order of scope Y scope X process, but error processing of joinFailure is executed in FaultHandler of scope X and the processing continues.
- When joinFailure occurs at (2), an attempt is made to propagate to the upper level of the process, but there is nothing to catch joinFailure; therefore, the business process stops. In this case, the business process goes into a restartable interrupted state.
- When the suppressJoinFailure attribute is "yes":
- When joinFailure occurs at (1), the propagation of joinFailure is controlled and the business process goes into a non-restartable interrupted state.
- When joinFailure occurs at (2) as well, the propagation of joinFailure is controlled and the business process goes into a non-restartable interrupted state.
The attribute queryLanguage of the element [someElement] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support the queryLanguage attribute. XPath1.0 is always used as the query language. XPath1.0 for the Cosminexus Service Platform has a partially unique extension.
Note that in the case of BPEL 1.1 and BPEL 2.0, the default query value is XPath1.0.
- Output conditions
- When the queryLanguage attribute is defined
- Action
- If a query is not used in the high level design tools, specific action need not be taken.
- If a query language other than XPath1.0 is used, import the BPEL file and then correct the query specification using the business process editor.
The attribute expressionLanguage of the element [someElement] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support the expressionLanguage attribute. XPath1.0 is always used as the expression language. XPath1.0 for the Cosminexus Service Platform has a partially unique extension.
Note that in the case of BPEL 1.1 and BPEL 2.0, the default expression value is XPath1.0.
- Output conditions
- When the expressionLanguage attribute is defined
- Action
- If an expression is not used in the high level design tools, specific action need not be taken.
- If a expression other than XPath1.0 is used, import the BPEL file and then correct the specification of the expression using the business process editor.
An empty activity was added because no activity was defined in the element [someElement].
- If one or more child elements are not defined for a BPEL element (such as while activity) that can have a child element, an empty activity is added as a child element when the BPEL file is imported.
- Output conditions
- When the activity element of [someElement] does not have a child element
- Action
- Does not affect the execution of the business process. Specific action need not be taken.
The element [someElement] is not supported and, hence, not applied. Also, if lower attributes and elements exist, these attributes and elements are also not applied.
- The Cosminexus Service Platform does not support the BPEL elements described by [someElement].
- Output conditions
- When unsupported elements are defined
- Action
- Replace the processing by functionality supported on the Cosminexus Service Platform.
The attribute [someAttribute] of the element [someElement] is not supported and, hence, not applied.
- The Cosminexus Service Platform does not support the BPEL attributes described by [someAttribute].
- Output conditions
- When unsupported attributes are defined
- Action
- Replace the processing by functionality supported on the Cosminexus Service Platform.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.