Upgrading Projects with Multiple Routing Services That Use the Same Namespace

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. 14-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF If you attempt to upgrade applications that use non-managed connections for adapter connections, you must modify the projects after upgrade to use proper connections defined by using supported administration tools, such as the Oracle WebLogic Server Administration Console.

14.2.4 Description Lost After Upgrade of Technology Adapter

If you created an 10g Release 3 10.1.3 technology adapter using the Adapter Configuration Wizard, and you entered a description for the adapter in the Description field of the wizard, the description will be lost when you open and migrate the project in Oracle JDeveloper 11g. This is because the documentation element in removed from the WSDL file during the upgrade. If the adapter is important, you can use the Oracle JDeveloper 11g Adapter Configuration Wizard to add the description after you have upgraded the project.

14.2.5 Upgrading an Inbound Synchronous Request-Reply Use Case

In Oracle SOA Suite 10g, if you used the MQSeries Adapter inbound synchronous request-reply use case, you will notice that there is only one message type, which is REQUEST. In Oracle SOA Suite 11g, the MQAdapter supports two message types: REQUEST and NORMAL. The REQEUST MQ message type always has replyToQueue set on its header so there is no need for FallbackQueueName and FallbackQueueManagerName. On the other hand, a NORMAL Message may or may not have FallbackQueueName and FallbackQueueManagerName. So, when a 10g inbound synchronous request-reply scenario is upgraded to 11g, then the Message Type remains as REQUEST type. Therefore, at runtime, there is no need for FallbackQueueName and FallbackQueueManagerName, even though these properties would resides in the .jca file. If you want to use these properties, you must set the message type to NORMAL. For more information about the inbound synchronous request-reply use case, see Oracle MQ Series Adapter Use Cases in the Oracle Fusion Middleware Users Guide for Technology Adapters.

14.2.6 Upgrading Projects That Use Outbound Dequeue

If you used the MQSeries Adapter outbound dequeue use case, which was a documented use case scenario in 10g Release 3 10.1.3, then note that these types of projects cannot be upgraded by Oracle JDeveloper 11g. Instead, you must recreate these types of projects after the upgrade to Oracle JDeveloper 11g. While recreating the project you must ensure that you set the value for UITransmissionPrimitive to SynchronousDequeue. For more information, see Outbound Dequeue Scenario in the Oracle Fusion Middleware Users Guide for Technology Adapters.

14.2.7 Upgrading AQ Adapter Headers

If you are upgrading an application that uses the Oracle Application Server Adapter for Advanced Queuing AQ adapter, then note that the AQ Adapter header is accessed differently in Oracle Fusion Middleware 11g.