Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite
11g Release 1 (11.1.1.6.3)

Part Number E10224-15
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C Deployment Descriptor Properties

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:

For more information about deployment descriptor properties, see Chapter "Oracle BPEL Process Manager Performance Tuning" of Oracle Fusion Middleware Performance and Tuning Guide.

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:

C.1.1 How to Define Deployment Descriptor Properties in the Property Inspector

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.

  1. 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

    Description of Figure C-1 follows
    Description of "Figure C-1 Selected BPEL Process Service Component"

  2. 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.

  3. 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."

    Figure C-2 Property Inspector

    Description of Figure C-2 follows
    Description of "Figure C-2 Property Inspector"

    The Create Property dialog is displayed.

  4. 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.

  5. In the Value field, enter an applicable value for this property (for example, true).

    Figure C-3 shows the completed Create Property dialog.

    Figure C-3 Create Property Dialog

    Description of Figure C-3 follows
    Description of "Figure C-3 Create Property Dialog"

  6. Click OK.

    The Property Inspector displays the added deployment descriptor property.

    Figure C-4 Property Inspector with Deployment Descriptor Property

    Description of Figure C-4 follows
    Description of "Figure C-4 Property Inspector with Deployment Descriptor Property"

  7. 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.

Example C-2 Partner Link Binding Property Definition in composite.xml

...
  <component name="myBPELServiceComponent">
 ....
  <property name="bpel.partnerLink.partner_link_name.
   nonBlockingInvoke">false</property>
</component>

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