Overriding WSDL Files of Dynamic Partner Links

You may need to override the default WSDL file used by dynamic partner links for the following reasons:

You must integrate with services that use message protection security policies.
The WSDL may contain important information such as the certificate used for message encryption.

The normalized message property endpointWSDL enables you to specify the WSDL file of the dynamic partner link. You must specify the entire WSDL dynamically instead of just the endpoint. This enables it to be passed to Oracle Web Services Manager (OWSM), which can then retrieve the correct service certificate from the specified WSDL.

The certificate in the WSDL file is ignored in the following cases:

The recipient.key.alias property name described in Overriding Security Certificates when Invoking Dynamic Partner Links is present.
The endpointWSDL property is not present.

Otherwise, the certificate is retrieved from the WSDL file.

To override WSDL files of dynamic partner links:

Define a variable of type string (for this example, the_wsdl_var is defined).
In the Copy Rules tab of an assign activity, assign the WSDL to the_wsdl_var.
In the invoke activity that invokes the partner link, click the Properties tab.
Click the endpointWSDL property.

Note:

In BPEL 2.0 processes, the properties are not automatically displayed in the Properties column. You must click the Add icon to select the property and its content (either a variable or an XPath expression).
Double-click the Value column to display the Browse (...) icon.
Click the Browse (...) icon to display the Adapter Property Value dialog.
Click the Browse icon to display the Variable XPath Builder dialog.

Select the_wsdl_var as the variable, and click OK. This value specifies the WSDL of the dynamic partner link.

Note:

In BPEL 2.0, there are only Name and Value columns in the Properties table. The Type column is not included.

Figure 8-8 endpointWSDL Normalized Message Property of Invoke Activity

Description of "Figure 8-8 endpointWSDL Normalized Message Property of Invoke Activity"

When complete, the BPEL file is defined as follows:

<variables>
  <variable name="the_wsdl_var" type="xsd:string"/>
</variables>
 
<assign name="myAssignWsdl">
  <copy>
    <from
expression='"http://localhost:8001/soa-infra/services/default/ServiceWithNewCer
tificate!1.0/service_ep?WSDL"'/>
    <to variable="the_wsdl_var"/>
  </copy>
</assign>
 
<invoke name="Invoke"
        inputVariable="Invoke_InputVariable" 
        partnerLink="Service"
        portType="ns1:ServiceBPELProcess" 
        operation="process"
        bpelx:invokeAsDetail="no"> 
                   
            <bpelx:inputProperty name="endpointWSDL" 
                                 variable="the_wsdl_var"/>
 
</invoke>

For more information about normalized message properties, see Propagating Normalized Message Properties Through Message Headers.