Oracle WSM 11g ID Propagation with SAML Token Sender Vouches over SSL WS-Security 1.0

14-2 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

14.1.1 Upgrading Oracle Enterprise Service Bus Routing Rules That Are Not Exposed as Services

If you upgrade an Oracle Enterprise Service Bus 10g project that contains an ESB routing service that is not exposed as a Web service, then the routing service and related composites cannot be invoked after upgrade. To resolve this issue, modify the routing service in Oracle Mediator 11g so it is exposed as a Web service. For more information, see Creating Mediator Routing Rules in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Alternatively, you can ensure that all routing services in your Oracle Enterprise Service Bus 10g projects are exposed as Web services before you begin the upgrade process.

14.1.2 Upgrading Oracle Enterprise Service Bus Domain Value Maps DVMs and Cross References

If you use domain value maps in your and Oracle Enterprise Service Bus 10g projects, then note that while the xPath functions for DVMs and cross-references are upgraded automatically, you must perform a post-upgrade task to upgrade the DVM and cross reference metadata to 11g. For more information, see Section 9.3.7.7, Upgrading Domain Value Maps DVMs and Cross References XREFs in the ESB Repository .

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

If you used XSLT functions to manipulate SOAP headers in Enterprise Service Bus ESB 10g, then after you upgrade your application, those header manipulation will be modeled as assignments in Oracle Mediator 11g. For complex header manipulations, you should manually verify the SOAP headers before deploying the upgraded Oracle Mediator 11g projects. For more information, see Creating Static Routing Rules in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

14.1.4 Upgrading Projects with Multiple Routing Services That Use the Same Namespace

Oracle Enterprise Service Bus 10g supports multiple routing services that have WSDLs that reference the same targetNameSpace within a single ESB project. For example, at least one of the sample 10g applications available on the Oracle Technology Network the samples_102_responseForward sample application supported this scenario. However, Oracle Mediator 11g no longer supports this configuration. During the upgrade of the application in Oracle JDeveloper 11g, whenever a second service is found to have the WSDL pointing to the same targetNameSpace, the namespace is modified by suffixing _service-qname to the namespace. In addition, a warning message is added to the log file. For example, in the Samples_102_ResponseForward sample application, the targetNameSpace of the service DispatchShipmentDetails is: http:oracle.comesbnamespacesSamples_102_ResponseForward Upgrading Other Oracle SOA Suite Technologies 14-3 After the upgrade of the application, it appears as follows: http:oracle.comesbnamespaces Samples_102_ResponseForward_Samples.102_ResponseForward.DispatchShipmentDetails In this example, Samples.102_ResponseForward.DispatchShipmentDetails is the qname of service DispatchShipmentDetails.

14.1.5 Upgrading Routing Services to Use Asynchronous Routing

In Oracle Enterprise Service Bus 10g, there was no support for asynchronous routing services. Instead, when Oracle Enterprise Service Bus called an Oracle BPEL Process Manager asynchronous process, then a OneWay service was created. If you created a project that uses such a OneWay service, then after you open and upgrade the application in Oracle JDeveloper 11g, you can remove the old routing service and recreate the routing service to use an Oracle Mediator 11g asynchronous routing instead of the OneWay invocation.

14.1.6 Upgrading Filtering or Setting Message Headers in Oracle Enterprise Service Bus

Oracle Enterprise Service Bus 10g supports filtering or setting message headers for standard and custom header properties for adapters, such as SOAP, JCA, JMS, and AQ adapters. Filtering in Oracle Enterprise Service Bus is done as part of the filterExpression tag of the routing rule. Many filter expressions are automatically upgraded, but for complex filters, the upgrade might be partial. When you open your Oracle Enterprise Service Bus projects in Oracle JDeveloper 11g, each routing rule is upgraded into case, and the filter expression is converted to condition. These changes can be found in the mplan file of the Routing Service. For example, the following code snippet shows the filter expression in an Oracle Enterprise Service Bus 10g routing rule: filterExpression{ehdr:getRequestHeader fhdr:InboundFileHeaderTypefhdr:fileName = Mobile.xml};{ namespace fhdr=http:xmlns.oracle.compcbpeladapterfile namespace ehdr=http:www.oracle.comXSLTransformjava oracle.tip.esb.server.headers.ESBHeaderFunctions } filterExpression During upgrade, this example is converted to the equivalent condition of the case in the mplan file: condition language=xpath xmlns:ehdr=http:www.oracle.comXSL Transformjavaoracle.tip.esb.server.headers.ESBHeaderFunctions xmlns:fhdr=http:xmlns.oracle.compcbpeladapterfile expressionin.property.jca.file.FileName =Mobile.xmlexpression condition Setting message headers is accomplished as part of the transformation files and these are upgraded to assign statements. The following code snippet shows an example of setting message headers in Oracle Enterprise Service Bus 10g: xsl:variable name=inputCountry select=imp1:CustomerDataCountry select=ehdr:setOutboundHeader