C Deployment Descriptor Properties

This appendix describes how to define deployment descriptor properties for BPEL process service components.

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.

C.1 Introduction to Deployment Descriptor Properties

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

C.1.1 How to Define Deployment Descriptor Properties

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
`completionPersistPolicy`	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: `on` (default): The completed instance is saved normally. `deferred`: The completed instance is saved, but with a different thread and in another transaction. `faulted`: Only the faulted instances are saved. `off`: No instances of this process are saved.
`disableAsserts`	This property, when set to `true`, disables assertions in BPEL 1.1 projects.
`globalTxMaxRetry`	If using outbound adapters in an asynchronous BPEL process, specify the maximum number of retries for a remote fault.
`globalTxRetryInterval`	If using outbound adapters in an asynchronous BPEL process, specify the time interval in milliseconds between retries for a remote fault.
`inMemoryOptimization`	Default value is `false`. This property can only be set to `true` if it does not have dehydration points. Activities like wait, receive, onMessage, and onAlarm create dehydration points in the process. If this property is set to `true`, in-memory optimization is attempted on the instances of this process on `to-spec` queries.
`keepGlobalVariables`	Specify whether the server can keep global variable values in the instance store when the instance completes: `false` (default): Global variable values are deleted when the instance completes. `true`: Global variable values are not deleted.
`oneWayDeliveryPolicy`	This property sets the persistence policy of the process in the delivery layer. The possible values are: `async.persist`: Messages into the system are saved in the delivery store before being picked up by the engine. `async.cache`: Messages into the system are saved in memory before being picked up by the engine. `sync`: The instance-initiating message is not temporarily saved in the delivery layer. The engine uses the save thread to initiate the message.
`sensorActionLocation`	The location of the sensor action XML file. The sensor action XML file configures the action rule for the events.
`sensorLocation`	The location of the sensor XML file. The sensor XML file defines the list of sensors into which events are logged.
`transaction`	This property configures the transaction behavior of the BPEL instance for initiating calls. `requiresNew`: A new transaction is created for the execution, and the existing transaction (if there is one) is suspended. This behavior is true for both request/response (initiating) environments and one-way, initiating environments in which `bpel.config.oneWayDeliveryPolicy` is set to `sync`. `required`: In request/response (initiating) environments, this setting joins a caller's transaction (if there is one) or creates a new transaction (if there is no transaction). In one-way, initiating environments in which `bpel.config.oneWayDeliveryPolicy` is set to `sync`, the invoke message is processed using the same thread in the same transaction. 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 correlation is needed and it is always done asynchronously.

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

Property Name	Description
`idempotent`	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. `true` (default): If the server fails, it performs the activity again after restarting. This is because the server does not dehydrate immediately after the invoke and no record exists that the activity executed. `false`: Activity is dehydrated immediately after execution and recorded in the dehydration store. When idempotent is set to `false`, it provides better failover protection, but may impact performance if the BPEL process accesses the dehydration store frequently.
`nonBlockingInvoke`	Default value is `false`. When this is set to `true`, a separate thread is spawned to do the invocation so that the invoke activity does not block the instance.
`validateXML`	Enables message boundary validation. When set to `true`, the XML message is validated against the XML schema during a receive activity and an invoke activity for this partner link. If the XML message is invalid, then a `bpelx:invalidVariables` runtime fault is thrown. This overrides the domain level `validateXML` property. The following example enables validation for only the `StarLoanService` partner: <partnerLinkBinding name="StarLoanService"> <property name="wsdlLocation"> http://<hostname>:9700/orabpel/default/StarLoan/Sta rLoan?wsdl</property> <property name="validateXML">true</property> </partnerLinkBinding>

idempotent

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.

true (default): If the server fails, it performs the activity again after restarting. This is because the server does not dehydrate immediately after the invoke and no record exists that the activity executed.
false: Activity is dehydrated immediately after execution and recorded in the dehydration store. When idempotent is set to false, it provides better failover protection, but may impact performance if the BPEL process accesses the dehydration store frequently.

nonBlockingInvoke

Default value is false. When this is set to true, a separate thread is spawned to do the invocation so that the invoke activity does not block the instance.

validateXML

Enables message boundary validation. When set to true, the XML message is validated against the XML schema during a receive activity and an invoke activity for this partner link. If the XML message is invalid, then a bpelx:invalidVariables runtime fault is thrown. This overrides the domain level validateXML property. The following example enables validation for only the StarLoanService partner:

<partnerLinkBinding name="StarLoanService"> 
<property name="wsdlLocation">
http://<hostname>:9700/orabpel/default/StarLoan/Sta
rLoan?wsdl</property> 
<property name="validateXML">true</property> 
</partnerLinkBinding>

C.1.2 How to Get the Value of a Preference within a BPEL Process

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.

C.2 Deprecated 10.1.3 Properties

Table C-3 lists deprecated properties that can no longer be used.

Table C-3 Deprecated Properties

Property	Deployment Descriptor Type	Deprecated for Release...
`completionPersistLevel`	`configurations`	11g Release 1
`defaultInput`	`configurations`	11g Release 1
`initializeVariables`	`configurations`	11g Release 1
`loadSchema`	`configurations`	11g Release 1
`noAlterWSDL`	`configurations`	11g Release 1
`optimizeVariableCopy`	`configurations`	11g Release 1
`relaxTypeChecking`	`configurations`	11g Release 1
`relaxXPathQName`	`configurations`	11g Release 1
`transaction`	`configurations`	10.1.3.4
`SLACompletionTime`	`configurations`	11g Release 1
`xpathValidation`	`configurations`	11g Release 1
`user`	`configurations`	11g Release 1
`pw`	`configurations`	11g Release 1
`role`	`configurations`	11g Release 1
`correlation`	`partnerLinkBinding`	11g Release 1
`contentType`	`partnerLinkBinding`	10.1.3
`retryInterval`	`partnerLinkBinding`	Deprecated by the fault policy feature in 10.1.3.3
`retryMaxCount`	`partnerLinkBinding`	Deprecated by the fault policy feature in 10.1.3.3
`wsdlLocation`	`partnerLinkBinding`	11g Release 1
`wsdlRuntimeLocation`	`partnerLinkBinding`	11g Release 1
`wsseHeaders`	`partnerLinkBinding`	11g Release 1
`wsseUsername`	`partnerLinkBinding`	11g Release 1
`wssePassword`	`partnerLinkBinding`	11g Release 1
`preferredPort`	`partnerLinkBinding`	11g Release 1
`fullWSAddressing`	`partnerLinkBinding`	11g Release 1