Additional Steps When Upgrading Technology Adapter Headers

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. 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.