The following sections describe interoperability scenarios to consider when you are using Oracle Fusion Middleware 11g components with other Oracle Fusion Middleware 11g components.
This chapter contains the following sections:
Web services are Web-based applications that use open, XML-based standards and transport protocols to exchange data with clients. Web services are developed using Java Technology APIs and tools provided by an integrated Web services category.
Oracle supports the following Web services categories, which are associated with specific Oracle Fusion Middleware products and components:
JAX-WS Web Services for Oracle WebLogic Serve
Web Services for ADF Business Components
Web Services for Oracle SOA Suite
Web Services for Oracle Service Bus 11g
These Oracle Web services categories support a variety of Web services message formats, capabilities, and security features. While this support varies from one category to another, all the Oracle Web services categories support the following standard features in the communication messages they send and receive:
Plain SOAP
WS-Security, With SSL
WS-Security, No SSL
As a result, if you develop Web services applications that support these types of Web services messages, then the services you create can be used interoperably with any of the Oracle Web services security categories.
For a more information about the supported WS-Security scenarios between the categories and information on how to configure Web services endpoints, refer to the Oracle Fusion Middleware Interoperability Guide for Oracle Web Services Manager.
For more information about each of the Oracle Web services categories, see the following sections:
JAX-WS is designed to take the place of JAX-RPC in Web services and Web applications. To compare the features that are supported for JAX-WS and JAX-RPC, see "How Do I Choose Between JAX-WS and JAX-RPC?" in Oracle Fusion Middleware Introducing WebLogic Web Services for Oracle WebLogic Server. For information about migrating a JAX-RPC Web service to JAX-WS, "Migrating JAX-RPC Web Services and Clients to JAX-WS."
ADF Business Components simplify the development, delivery, and customization of business applications for the Java EE platform by providing a library of reusable components and supporting design time facilities in Oracle JDeveloper.
For more information, see "Integrating Service-Enabled Application Modules" in Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
Oracle SOA composite applications include the SOA service components. SOA service components are the basic building blocks of SOA applications, implementing a part of the overall business logic functionality.
Note that you can deploy SOA service components to the Oracle Fusion Middleware environment. For more information about developing SOA service components, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
Oracle Service Bus uses the underlying WebLogic security framework as building blocks for its security services. Specifically, the Oracle Service Bus uses the WebLogic Server JAX-RPC stack to implement its web services and that the WebLogic Server security framework is used for protecting these services.
For information about configuring and attaching policies, see "Using WS-Policy in Oracle Service Bus Proxy and Business Services" in Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
This section describes Oracle Identity Management interoperability considerations.
Note:
Interoperability between the Oracle Identity Management Suite and the other Oracle Fusion Middleware 11g components is documented in the Oracle Fusion Middleware Supported System Configurations page at:]http://www.oracle.com/technetwork/middleware/downloads/fmw-11gr1certmatrix.xls
Oracle HTTP Server WebGates integrate with Oracle Fusion Middleware 11g through the following:
Weblogic
Weblogic Identity Assertion Provider that will reside in Weblogic Server
Oracle HTTP Server 11g webtier
Oracle HTTP Server 11g Webgates
For more information, see "Configuring Single Sign-On in Oracle Fusion Middleware" in the Oracle Fusion Middleware Application Security Guide.
Websphere
Websphere connector that will reside in Websphere
IBM HTTP Server 11g webtier
IBM HTTP Server 11g Webgates
For more information, see Oracle Fusion Middleware Configuration Guide for IBM WebSphere Application Server.
Review the following Oracle Access Management (OAM) integration considerations:
If you are using a OAM 10gR3 (10.1.4.3) backend or server, then use OAM 10.1.4.3 versions of OHS 11g WebGates for integration with Oracle Fusion Middleware components.
If you are using a OAM 11gR1 (11.1.1.3) version of the product, then use OAM 11gR1 (11.1.1.3) versions of OHS 11gR1 webgates.
Note:
For more information about individual Oracle Fusion Middleware product details integrating with OAM, see the product-specific documentation.For more information about certified versions, see the Oracle Identity Management certification matrix at: http://www.oracle.com/technetwork/middleware/id-mgmt/identity-accessmgmt-11gr1certmatrix-161244.xls.
In general, you can extend an existing Oracle Fusion Middleware product domain to support another Oracle Fusion Middleware product, as long as they are the same version number or patch set. For example, if you have an existing SOA Suite 11.1.1.3.0 domain, do not attempt to extend or patch that domain using Oracle WebCenter 11.1.1.3.1. To avoid potential interoperability issues, wait until both suites are available at equivalent versions.
Table 3-1 describes scenarios when two different products from different Oracle Fusion Middleware suites are collocated within the same domain. In these particular scenarios you will not be able to extend, upgrade, or patch one of the products before the other is available at the same version.
Note:
Oracle Identity Management domains should not be extended with any other Oracle Fusion Middleware components except for those in the SOA Suite. Oracle Identity Management does not currently support sharing a domain with any of the other products.Table 3-1 Domain Extension Interoperability Considerations