Upgrading Oracle Enterprise Service Bus Projects with SOAP Headers to Oracle Mediator 11g

Upgrading Other Oracle SOA Suite Technologies 14-5 ■ Upgrading Database Adapters Used for Stored Procedures

14.2.1 Verifying Adapters with the Oracle JDeveloper 11g Adapter Configuration Wizard

After upgrading your Oracle SOA Suite 10g projects to Oracle SOA Suite 11g, Oracle recommends that you use the adapter configuration wizard to verify the upgrade of your technology adapters. This will ensure that all required fields in your 11g are populated and that the adapter connections to your new Oracle Fusion Middleware 11g environment are valid. For more information, see the information the specific adapters you are using in the Oracle Fusion Middleware Users Guide for Technology Adapters.

14.2.2 Upgrading Adapter Header Variables

After you upgrade an application that uses adapter headers, you will likely receive an error after you open the application in Oracle JDeveloper 11g. The error will indicate that a variable or parameter was not recognized while it was parsing a header function. This is caused by a change in the way adapter header variables are defined in Oracle Fusion Middleware 11g. In Oracle Application Server 10g Release 3 10.1.3, you create adapter header variables in a wsdl file that has a name such as the following, or a similar name for the direction and adapter type you are using: fileAdapterOutboundHeader.wsdl In Oracle Fusion Middleware 11g, adapter header variables are now properties that you set on the Properties tab of the Invoke dialog box in Oracle JDeveloper. For example, the properties you can set for the JCA Adapter for FilesFTP are described in the section, Inbound Headers in the Oracle Fusion Middleware Users Guide for Technology Adapters. After you open your project in Oracle JDeveloper 11g, the wsdl header files you created for Oracle Application Server 10g will no longer be attached to the project. You must define each of the variables in the wsdl files as properties for each adapter type that uses header variables. For more information, refer to the appropriate chapter for each adapter type in the Oracle Fusion Middleware Users Guide for Technology Adapters.

14.2.3 Upgrading Non-Managed Connection Information in the Adapter JCA File

In Oracle Application Server 10g, you can use non-managed connections in the JCA file to point to your development resources. For example, data source definitions can be specified using the non-managed-connection element in the JCA file. In Oracle Application Server 10g, using non-managed connections was reserved for development only. In Oracle Fusion Middleware 11g, non-managed connections are not supported. Ideally, before upgrading your Oracle Application Server 10g projects to Oracle Fusion Middleware 11g, you should already be using JCA files that include only JNDI references to connections that are defined properly in the datasources.xml or oc4j-ra.xml files.