Upgrading Composite Applications That Rely on Payload Header Functionality

Upgrading Other Oracle SOA Suite Technologies 14-11 In some cases, because the projects are moved into a common directory during the upgrade, data associated with the workflow task in one project may overwrite data from another project if the workflow task in the second project uses the same name.

14.3.3 Editing Human Workflow Tasks After Upgrade

If you use Oracle JDeveloper 11g to upgrade an application with human workflow tasks, and then use the Task Editor to edit the task file, Oracle JDeveloper automatically generates a new payload XSD file. However, the existing WorkflowTask XSD file contains references to the payload XSD file used in the 10g version of the application. To fix this problem, edit the WorkflowTask XSD file to be sure it references the new payload XSD file. For example: ■ Change the following entry from: include schemaLocation=_payload.xsd xmlns= To: include schemaLocation=Payload.xsd xmlns= ■ Change the following entry from: element name=payload type=tns:payloadType minOccurs=0 maxOccurs=1 To: element name=payload type=tns:PayloadType minOccurs=0 maxOccurs=1 In these examples, replace the asterisk with the appropriate name and type defined in the payload XSD file.

14.4 Upgrade Tasks Associated with Oracle Business Rules

When you upgrade projects that use Oracle Business Rules, refer to the following documentation resources: ■ Section 9.3.1.1, Upgrading to the Oracle Fusion Middleware Java API for Oracle Business Rules ■ Appendix B, Upgrading Oracle Business Rules Dictionaries and Projects

14.5 Upgrading Oracle SOA Suite Client Applications

While you are in the process of upgrading your Oracle SOA Suite applications to 11g, and while your Oracle SOA Suite 10g environment is still up and running, you should begin to review, upgrade, and test the client applications that depend upon your Oracle SOA Suite environment. Use the following list to analyze your client applications for required updates that will allow them to work with your newly upgraded 11g Oracle SOA Suite environment: ■ Review the client applications to understand which remote Oracle SOA Suite APIs they are using. 14-12 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF For more information, refer to Section 9.3.1, Understanding Oracle SOA Suite API Changes for Oracle Fusion Middleware 11g . ■ Search your client applications for any references to Oracle SOA Suite HTTP URLs. The syntax of the Oracle SOA Suite 11g HTTP URLs has changed from 10g. To obtain the new URL that a client can use to access a deployed Oracle SOA Suite 11g application, use the home page of the application deployment in Oracle Enterprise Manager Fusion Middleware Control. For more information, see Monitoring SOA Composite Applications in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite. ■ If any of your client applications are using Web Services Addressing WS-Addressing, then you must modify the client. Oracle SOA Suite 11g supports WS-Addressing 1.0 for clients. As a result, you must either use a SOAP processor that understands WS-Addressing 1.0, or if you are using a SOAP processor that does not support WS-Addressing 1.0, then you must manually modify the 11g WSDL and change the client to get or set the WS-Addressing 1.0 headers. Refer to Example 14–2 and Example 14–3 for a before and after example of how to modify a WSDL so it can be invoked by a SOAP processor that does not support WS-Addressing 1.0. ■ If the clients using WS-Addressing are running on a Oracle SOA Suite 10g environment that you do not plan to upgrade at the same time, then you must apply a patch to the Oracle SOA Suite environment before the client applications running on the 10g server can invoke 11g BPEL processes. For more information, see the Upgrade chapter of the Release Notes for your platform. For example, if you are using a Linux operating system, refer to Patches Required to Address Specific Upgrade and Compatibility Requirements in the Oracle Fusion Middleware Release Notes for Linux x86. ■ Review your client applications for references to message targets, such as JMS queues and data source. Any references to these resources must be updated to point to the upgraded, Oracle SOA Suite 11g environment. ■ If a client application is using Oracle Service Bus OSB to invoke an Oracle BPEL Process Manager process with the optimized transport, you must modify the client application so it uses SOAPHTML to invoke the Oracle BPEL Process Manager process. For more information, see the Oracle Service Bus 10g Release 3 10.3 documentation, which is available on the Oracle Technology Network OTN: http:www.oracle.comtechnologydocumentationbea.html Example 14–2 Example of WSDL Code That Can Be Used by a SOAP Processor that Supports WS-Addressing 1.0 ?xml version=1.0 encoding=UTF-8 ? definitions name=UnitedLoan targetNamespace=http:services.otn.com xmlns=http:schemas.xmlsoap.orgwsdl xmlns:plnk=http:schemas.xmlsoap.orgws200305partner-link xmlns:s1=http:www.autoloan.comnsautoloan xmlns:soap=http:schemas.xmlsoap.orgwsdlsoap xmlns:wsdl=http:schemas.xmlsoap.orgwsdl