OC4J 10g 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