Upgrading AQ Adapter Headers

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 14-10 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF The db: namespace is specified in the definition of the schema, which is the same as the target namespace. ■ In 10g Release 3 10.1.3.4 and later, the XSD generator generates qualified elements, which appear as follows in the InputParameters root element: InputParameters ..InputParameters Note that the db: namespace has been removed. ■ If you were using a version of Oracle JDeveloper 10g Release 3 10.1.3 that was incompatible with the Oracle SOA Suite version, you could also encounter a scenario where the elements are removed: nullsome valuenull The solution is as follows: ■ First, make sure that you are using a version of Oracle JDeveloper that matches the version of your Oracle SOA Suite environment. ■ Second, after you upgrade to Oracle JDeveloper and Oracle SOA Suite10g Release 3 10.1.3.4 or to Oracle SOA Suite and Oracle JDeveloper 11g, regenerate the XSD. After you upgrade and regenerate the XSD, you must then modify any related assign activities and any xPath expressions accordingly.

14.3 Upgrade Tasks Associated with Human Workflow Tasks

The following upgrade tasks should be considered when you are upgrading Oracle SOA Suite applications that use human workflow tasks: ■ Upgrading Task Details for an Associated Human Workflow Task ■ Upgrading Multiple Projects That Share a Common Human Workflow Task ■ Editing Human Workflow Tasks After Upgrade

14.3.1 Upgrading Task Details for an Associated Human Workflow Task

When you are upgrading Oracle SOA Suite 10g applications that include task details for a human task, note the following: ■ In Oracle SOA Suite 10g Release 3 10.1.3, task details were generated inside same composite project and was deployed during composite deployment. ■ In Oracle SOA Suite 11g, task details are generated as a separate project that must be deployed separately. As a result, during the upgrade of Oracle Human Workflow, Oracle JDeveloper 11g automatically creates a new project for the task details UI and upgrades the task detail pages. You must then deploy this project separately, after deploying the associated composite application.

14.3.2 Upgrading Multiple Projects That Share a Common Human Workflow Task

If you are upgrading an application that contains multiple Oracle JDeveloper projects that share a common human workflow task, then be sure to review the upgraded application carefully in Oracle JDeveloper 11g.