1. Developing SOA Applications with Oracle SOA Suite
  2. Deployment Descriptor Properties
  3. Introduction to Deployment Descriptor Properties
  4. How to Define Deployment Descriptor Properties in the Property Inspector

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.
  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 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 oneWayDeliveryPolicy 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, async.persist).
  6. Click OK.

    The Property Inspector displays the added deployment descriptor property.

  7. Click Source in the SOA Composite Editor.

    The oneWayDeliveryPolicy configuration property with the bpel.config prefix is displayed in the composite.xml file, as shown in the following example: 

<component name="LoanApproval" version="2.0">
. . .
  <componentType>
  . . .
  . . .
  <property name="bpel.config.oneWayDeliveryPolicy" type="xs:string"
  many="false">async.persist</property>
	</componentType>
</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 the example that follows. Note the prefix of bpel.partnerLink.partner_link_name, which is required for this type of property. 

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