Upgrading Non-Managed Connection Information in the Adapter JCA File

14-8 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF DOCTYPE_REVISIONlt;MSG_TYPE1lt; MSG_TYPElt;PAYLOADlt; PAYLOADlt;tns:PayloadHeaderlt;tns:Header Example Steps to Perform After Upgrading to Oracle BPEL Process Manager After upgrading to Oracle BPEL Process Manager 11g: 1. Define a new variable headerVariable of type string. For example: variable name=headerVariable type=xsd:string 2. Create an assign block, such as the one shown in Example 14–1 . 3. At the time of invocation, make sure that the headerVariable value is copied back to the jca.aq.HeaderDocument property: invoke name=Send_PO partnerLink=X12_4010_850_ENQ_Service portType=ns2:Enqueue_ptt operation=Enqueue inputVariable=Send_PO_Enqueue_InputVariable bpelx:inputProperty name=jca.aq.HeaderDocument variable=headerVariable invoke Example 14–1 Assign Block When Upgrading Adapter Headings assign name=assign header copy from expression=lt;?xml version = quot;1.0quot;standalone = quot;yesquot; standalone = quot;yesquot;?lt;tns:Header xmlns:tns=quot;http:xmlns.oracle.compcbpeladapteraqInbound tns:PayloadHeaderlt;MSG_ID12345lt; MSG_IDlt;INREPLYTO_MSG_ID54321lt; INREPLYTO_MSG_IDlt;FROM_PARTYAcmelt; FROM_PARTYlt;TO_PARTYGlobalChipslt; TO_PARTYlt;ACTION_NAMEcontentType:applicationoctet-stream;filename:abc.xmllt; ACTION_NAMElt;DOCTYPE_NAME850lt; DOCTYPE_NAMElt;DOCTYPE_REVISION4010lt; DOCTYPE_REVISIONlt;MSG_TYPE1lt;MSG_TYPElt;PAYLOADlt; PAYLOADlt;tns:PayloadHeaderlt;tns:Header to variable=headerVariable copy assign

14.2.9 Upgrading Composite Applications That Rely on Payload Header Functionality

Section 14.2.7, Upgrading AQ Adapter Headers describes how to use the jca.aq.HeaderDocument property that is required in Oracle Fusion Middleware 11g when your application needs to access Payload Headers. The procedure described in that section must be performed for all Oracle Application Server 10g BPEL and ESB processes that access the payload headers functionality. Note that in addition to the information in Section 14.2.7 , the target namespace of Header and PayloadHeader elements have changed Oracle Fusion Middleware11g Release 1 11.1.1.3.0. As a result, for any BPEL and ESB processes that involve accessing payload headers and that were designed using Oracle SOA Suite 10g, you must use the adapter wizard to regenerate its service and reference artifacts, also known as partner links in Oracle Application Server 10g. Upgrading Other Oracle SOA Suite Technologies 14-9 You must regenerate the artifacts so the correct target namespace is used for the definition of the Header element. This step is required in addition to the steps covered in Section 14.2.7 to access payload headers. In addition, you must change any Assign and Transformations that use the Header element. If you do not perform this step, then a namespace mismatch between design time and runtime results in XPath failures, as well as message enqueue failures.

14.2.10 Upgrading an AQ Outbound Request-Reply Scenario

In Oracle Fusion Middleware 11g, the procedure you use to create AQ outbound request-reply scenarios for Oracle BPEL Process Manager projects has changed. As a result, when you upgrade an Oracle SOA Suite 10g application that uses this scenario, the WSDL file that is created during the upgrade does not contain the required binding information. To correct this problem, do the following after you open and upgrade the application in Oracle JDeveloper 11g: 1. Add the JCA entry to the WSDL file created by the upgrade, as follows: ?binding.jca CombinedRequestReply_aq.jca? wsdl:definitions name=CombinedRequestReply ... . . . wsdl:definitions 2. Add the binding entry in the composite.xml file: reference ui:wsdlLocation=CombinedRequestReply.wsdl name=CombineRequestReply interface.wsdl interface=http:xmlns.oracle.compcbpel adapteraqEnqueueRequestwsdl.interfaceEnqueue_ptt callbackInterface=http:xmlns.oracle.compcbpel adapteraqDequeueReplywsdl.interfaceDequeue_ptt xmlns:ns=http:xmlns.oracle.comsca1.0 binding.jca config=CombinedRequestReply_aq.jca reference 3. Remove any unused WSDL references from the .bpel file.

14.2.11 Upgrading Database Adapters Used for Stored Procedures

As described in Section 9.1, About Using the Oracle JDeveloper 11g Migration Wizard for Oracle SOA Suite Applications , Oracle recommends that you apply the latest patch sets to your Oracle SOA Suite environment and use the latest 10g Release 3 10.1.3 Oracle JDeveloper before upgrading to 11g. However, if you are upgrading from 10g Release 3 10.1.3.3 or earlier, note the following if you are using a database adapter for stored procedures. ■ In Oracle SOA Suite 10g Release 3 10.1.3.3 and earlier, the XSD generator of the adapter generated an XSD that contained unqualified elements. You can identify unqualified elements by viewing the InputParameters root element in the XSD file. The unqualified element appears as follows: db:InputParameters ... db:InputParameters