Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1.7) Part Number E10224-16 |
|
|
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.
For more information about deployment descriptor properties, see Chapter "Oracle BPEL Process Manager Performance Tuning" of Oracle Fusion Middleware Performance and Tuning Guide.
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:
Table C-1 lists the configuration deployment descriptor properties.
When you define configuration properties, you must add a prefix of bpel.config
to the property name. For example, the property inMemoryOptimization
must be defined as bpel.config.inMemoryOptimization
. For information on defining properties in the Property Inspector in Oracle JDeveloper, see Section C.1.1, "How to Define Deployment Descriptor Properties in the Property Inspector."
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." For more information, see Section "Tuning Database Persistence for BPEL" of Oracle Fusion Middleware Performance and Tuning Guide. |
|
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." |
Table C-2 lists the partner link binding deployment descriptor properties.
When you define partner link binding properties, you must add a prefix of bpel.partnerLink.
partner_link_name
to the property name. For example, the property nonBlockingInvoke
must be defined as bpel.partnerLink.
partner_link_name
.nonBlockingInvoke
. For information on defining properties in the Property Inspector in Oracle JDeveloper, see Section C.1.1, "How to Define Deployment Descriptor Properties in the Property Inspector."
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.
For more information about the |
|
Default value is For more information, see Section 10.1.1, "What You May Need to Know About the Execution of Parallel Flow Branches in a Single Thread." |
|
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> |
You define configuration and partner link binding deployment descriptor properties and values in the Property Inspector of Oracle JDeveloper. When complete, the properties are displayed in the BPEL process service component section of the composite.xml
file.
In the SOA Composite Editor, select the BPEL process service component, as shown in Figure C-1.
Figure C-1 Selected BPEL Process Service Component
Go to the Property Inspector in the lower right corner of Oracle JDeveloper. If the Property Inspector is not displayed, select Property Inspector from the View main menu.
In the Properties section, click the Add icon, as shown in Figure C-2.
For this example, the oneWayDeliveryPolicy property is already defined because the Delivery option was selected in the Create BPEL Process dialog during BPEL process creation. For more information about setting this property during BPEL process creation, see Section 4.1.1, "How to Add a BPEL Process Service Component."
The Create Property dialog is displayed.
In the Name field, enter the deployment descriptor property. For this example, the configuration deployment descriptor property inMemoryOptimization
is defined. Therefore, a prefix of bpel.config
is required. For more information about configuration deployment descriptor properties, see Table C-1.
If you instead add a partner link binding property, a prefix of bpel.partnerLink.
partner_link_name
is required, where partner_link_name
is the name of the partner link (for example, LoanService
). For more information about partner link binding deployment descriptor properties, see Table C-2.
In the Value field, enter an applicable value for this property (for example, true
).
Figure C-3 shows the completed Create Property dialog.
Click OK.
The Property Inspector displays the added deployment descriptor property.
Figure C-4 Property Inspector with Deployment Descriptor Property
Click Source in the SOA Composite Editor.
The inMemoryOptimization
configuration property with the bpel.config
prefix is displayed in the composite.xml
file, as shown in Example C-1.
Example C-1 Configuration Property Definition in composite.xml
<component name="LoanApproval" version="1.1">
<implementation.bpel src="LoanApproval.bpel"/>
<property name="bpel.config.oneWayDeliveryPolicy" type="xs:string"
many="false">async.persist</property>
<property name="bpel.config.inMemoryOptimization" type="xs:string"
many="false" override="may">true</property>
</component>
If you instead define a partner link binding deployment descriptor property in the Property Inspector (for example, the nonBlockingInvoke
partner link binding property), it is displayed in the composite.xml
file, as shown in Example C-2. Note the prefix of bpel.partnerLink.
partner_link_name
, which is required for this type of property.
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 |