Upgrading Filtering or Setting Message Headers in Oracle Enterprise Service Bus

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. Upgrading Other Oracle SOA Suite Technologies 14-7 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 jca.aq.HeaderDocument value from inbound to outbound in the .mplan file of the Oracle Mediator file. ■ After upgrading to Oracle BPEL Process Manager 11g: 1. Define a new variable vInboundHeaders of type string. For example: variable name=vInboundHeaders type=xsd:string 2. In the receive activity, make sure that the jca.aq.HeaderDocument property gets written to the above variable. For example: bpelx:property name=jca.aq.HeaderDocument variable=vInboundHeaders 3. At the time of invocation, make sure that the vInboundHeaders value is copied back to the jca.aq.HeaderDocument property: invoke name=Invoke_1 inputVariable=Invoke_1_Enqueue_InputVariable partnerLink=EnqueueClobPayload portType=ns2:Enqueue_ptt operation=Enqueue bpelx:inputProperty name=jca.aq.HeaderDocument variable=vInboundHeaders invoke

14.2.8 Additional Steps When Upgrading Technology Adapter Headers

Use the following procedure when you are not using an AQ adapter, and as a result you are not obtaining the value of the jca.aq.HeaderDocument property. In this scenario, you must populate the property manually. This involves two steps. Perform one step after you upgrade Oracle Enterprise Service Bus to Oracle Mediator 11g, and perform the second step after you upgrade to Oracle BPEL Process Manager 11g. Note that these examples show how you might invoke Oracle B2B from the adapter header. Example Steps to Perform After Upgrading to Oracle Mediator After upgrading to Oracle Mediator, assign the jca.aq.HeaderDocument value from inbound to outbound in the .mplan file of the Oracle Mediator file. For example: copy target=out.property.jca.aq.HeaderDocument expression=lt;?xml version = quot;1.0quot; standalone= quot;yesquot;?lt;tns:Header xmlns:tns=quot;http:xmlns.oracle.compcbpeladapteraqoutbound tns:PayloadHeaderlt;MSG_IDlt; MSG_IDlt;INREPLYTO_MSG_IDlt; INREPLYTO_MSG_IDlt;FROM_PARTYGlobalChipslt; FROM_PARTYlt;TOPARTYAcmelt; TO_PARTYlt;ACTION_NAMElt;ACTION_NAMElt;DOCTYPE_NAMEORDERSlt; DOCTYPE_NAMElt;DOCTYPE_REVISIOND98Alt;