Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1.6.0) Part Number E10224-11 |
|
|
PDF · Mobi · ePub |
This appendix describes how to define deployment descriptor configuration and partner link properties for BPEL process service components used at runtime by Oracle WebLogic Server, Oracle Enterprise Manager, or both.
This appendix includes the following sections:
Section C.1, "Introduction to Deployment Descriptor Properties"
Section C.2, "Deprecated 10.1.3 Properties"
Note:
You cannot specify deployment descriptor properties at runtime.Deployment descriptors are BPEL process service component properties used at runtime by Oracle WebLogic Server, Oracle Enterprise Manager, or both. There are two types of properties:
Configuration
Partner link binding
You define configuration properties and values in the BPEL process service component section of the composite.xml
file. Example C-1 shows how to define the inMemoryOptimization
configuration property.
Example C-1 Configuration Property Definition in composite.xml
... <component name="myBPELServiceComponent"> .... <property name="bpel.config.inMemoryOptimization">true</property> </component>
Table C-1 lists the configuration
deployment descriptor properties.
Table C-1 Properties for the configurations Deployment Descriptors
Property Name | Description |
---|---|
This property configures how the instance data is saved. It can only be set at the BPEL service component level. The following values are available:
|
|
This property, when set to |
|
If using outbound adapters in an asynchronous BPEL process, specify the maximum number of retries for a remote fault. |
|
If using outbound adapters in an asynchronous BPEL process, specify the time interval in milliseconds between retries for a remote fault. |
|
Default value is |
|
Specify whether the server can keep global variable values in the instance store when the instance completes:
|
|
This property sets the persistence policy of the process in the delivery layer. The possible values are:
For information about setting this property during BPEL process creation, see Section 4.1.1, "How to Add a BPEL Process Service Component." |
|
This property controls the number of instances to create and use to route messages. The possible values are:
For more information, see Section 9.2, "Routing Messages to the Same Instance." |
|
The location of the sensor action XML file. The sensor action XML file configures the action rule for the events. |
|
The location of the sensor XML file. The sensor XML file defines the list of sensors into which events are logged. |
|
This property configures the transaction behavior of the BPEL instance for initiating calls.
Note: This property does not apply for midprocess receive activities. In those cases, another thread in another transaction is used to process the message. This is because a correlation is needed and it is always done asynchronously. For information about setting this property during BPEL process creation, see Section 4.1.1, "How to Add a BPEL Process Service Component." |
You define partner link binding properties and values in the BPEL process service component section of the composite.xml
file. Example C-2 shows how to define the nonBlockingInvoke
partner link binding property.
Example C-2 Property Definition in composite.xml
...
<component name="myBPELServiceComponent">
....
<property name="bpel.partnerLink.partner_link_name.
nonBlockingInvoke">false</property>
</component>
Table C-2 lists the partnerLinkBinding
deployment descriptor properties.
Table C-2 Properties for the partnerLinkBinding Deployment Descriptors
Property Name | Description |
---|---|
An idempotent activity is an activity that can be retried (for example, an assign activity or an invoke activity). The instance is saved after a nonidempotent activity. This property is applicable to both durable and transient processes.
|
|
Default value is |
|
Enables message boundary validation. When set to <partnerLinkBinding name="StarLoanService"> <property name="wsdlLocation"> http://<hostname>:9700/orabpel/default/StarLoan/Sta rLoan?wsdl</property> <property name="validateXML">true</property> </partnerLinkBinding> |
The value of a property can be read by a BPEL process using the XPath extension function ora:getPreference(myPref)
. This gets the value of bpel.preference.myPref
.
This function can be used as part of a simple assign statement, used in condition expressions, or used as part of a more complex XPath expression.
Table C-3 lists deprecated properties that can no longer be used.
Table C-3 Deprecated Properties
Property | Deployment Descriptor Type | Deprecated for Release... |
---|---|---|
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
10.1.3.4 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
10.1.3 |
|
|
Deprecated by the fault policy feature in 10.1.3.3 |
|
|
Deprecated by the fault policy feature in 10.1.3.3 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |
|
|
11g Release 1 |