Custom Search SOABYTE here

Tuesday, June 29, 2010

Technology adaters 10g to 11g migration

Upgrade Tasks associated with Technology Adapters

Ø  Verifying Adapters with the Oracle JDeveloper 11g Adapter Configuration Wizard
After upgrading Oracle SOA Suite 10g projects to Oracle SOA Suite 11g, Oracle recommends to use the adapter configuration wizard to verify the upgrade of your technology adapters. This will ensure that all required fields in 11g are populated and that the adapter connections to new Oracle Fusion Middleware SOA Suite 11g environment are valid.

Ø  Upgrading Adapter Header variables
Issue: After upgrading 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 SOA Suite 11g.  In Oracle Application Server 10g Release 3 (10.1.3), you create adapter header variables in a wsdl file that has a name like, or a similar name for the direction and adapter type you are using: fileAdapterOutboundHeader.wsdl
In Oracle Fusion Middleware SOA Suite 11g, adapter header variables are now properties that you set on the Properties tab of the Invoke dialog box in Oracle JDeveloper.
Action: 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.

Ø  Upgrading Non-Managed Connection Information in the Adapter JCA File
Issue: In Oracle Application Server 10g, using non-managed connections was reserved for development only. In Oracle Fusion Middleware SOA Suite 11g, non-managed connections are not supported.
Action: Before upgrading your Oracle Application Server 10g projects to Oracle Fusion Middleware SOA Suite 11g, check whether the adapters are using JCA files that include only JNDI references to connections that are defined properly in the datasources.xml or oc4j-ra.xml files. 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.

Ø Description Lost After Upgrade of Technology Adapter
Issue: If you created a 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.
Action: 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.

Ø  Upgrading an MQ Adapter Inbound Synchronous Request-Reply Use Case
Issue: 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 reside in the .jca file.
Action: If you want to use these properties, you must set the message type to NORMAL.

Ø  Upgrading Projects That Use MQ Adapter 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.

Ø  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 SOA Suite 11g.
Specifically, you must perform the following post-upgrade steps for AQ adapter headers after you upgrade to Oracle SOA Suite 11g. This procedure is required for both Oracle BPEL Process Manager and for Oracle Enterprise Service Bus projects that are upgraded to Oracle Mediator.
After upgrading to Oracle Mediator, assign the "" value from inbound to outbound in the .mplan file of the Oracle Mediator file.
After upgrading to Oracle BPEL Process Manager 11g:
·         Define a new variable 'vInboundHeaders' of type string. For example:
·         In the receive activity, make sure that the property gets written to the above variable. For example: 
·         At the time of invocation, make sure that the "vInboundHeaders" value is copied back to the property:
<invoke name="Invoke_1"
partnerLink="EnqueueClobPayload" portType="ns2:Enqueue_ptt"

Ø  Upgrading an AQ Outbound Request-Reply Scenario
Issue: In Oracle Fusion Middleware SOA Suite 11g, the procedure used to create AQ outbound request-reply scenarios for Oracle BPEL Process Manager projects has changed. As a result, when upgrading 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.
Action: To correct this problem, do the following after you open and upgrade the application in Oracle JDeveloper 11g:
·         Add the JCA entry to the WSDL file created by the upgrade, as follows:
·         Add the binding entry in the composite.xml file:
·         Remove any unused WSDL references from the .bpel file.


Post a Comment

Blogger Profile