Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Service Bus
11g Release 1 (11.1.1.7)

Part Number E15867-07
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Interoperability Scenarios and Considerations

This chapter lists products, standards, and technologies supported by Oracle Service Bus (OSB), including Oracle and third-party products, protocols, and Web services standards such as SOAP and WS-Security.

This section includes information about Oracle Service Bus interoperability. It includes the following topics:

1.1 Supported Configurations

For support information on vendor operating systems, JDK, hardware, and database support, see Oracle Fusion Middleware Supported System Configurations at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

1.2 Supported Standards and Implementations

Oracle Service Bus supports the following standards and implementations.

Table 1-1 Supported Standards and Implementations

Standard/Implementation Version

Email Servers

  • Microsoft Windows IIS SMTP Server

  • Sol/Apache SMTP Server

FTP Servers

  • Microsoft Windows IIS FTP Server

  • Sol/Apache FTP Server

  • ProFTPD Server

    Note: ProFTPD Server is certified with the SFTP Transport and JCA FTP Adapter, but not with the FTP Transport.

Security Providers

For WebLogic Server 9.2 and later, Oracle Service Bus supports the following security providers:

Oracle WebLogic Server Security Providers

  • WebLogic Server default authentication provider

  • WebLogic Server default credential mapper

  • WebLogic Server PKI credential mapper/provider

  • WebLogic Server Java KeyStores (JKS)

  • WebLogic Server default User Name Token and X509 Token handlers

  • WebLogic Server XACML authorization provider

  • WebLogic Server XACML Role Mapping provider

Oracle Platform Security Providers

  • WebLogic SAML Identity Assertion Provider V2

  • WebLogic SAML Credential Mapping Provider V2

Web Services

  • WSDL 1.1

  • SOAP 1.1 and 1.2

  • SOAP w/ (MIME) Attachments (SwA)

  • SOAP Message Transmission Optimization Mechanism (MTOM) with XML-binary Optimized Packaging (XOP)

  • Universal Description, Discovery, and Integration version 3 (UDDI v3)

  • WS-ReliableMessaging 1.0

  • WS-Addressing 1.0

  • XACML 2.0

  • WS-Inspection

  • Web Services Interoperability Basic Profile (WS-I BP) 1.1

  • Web Services Interoperability Basic Security Profile (WS-I BSP) 1.0

WS-I Basic Security Profile: Oracle Service Bus complies with the Basic Security Profile specifications (see supported versions above) from the Web Services Interoperability Organization (WS-I) and considers it to be the baseline for Web Services interoperability.

However, in some cases, Oracle Service Bus does not reject SOAP/HTTP messages that are not WS-I compliant. This enables you to build implementations with service endpoints which are not strictly WS-I compliant.

When you configure a proxy service or business service, you can use the Oracle Service Bus Administration Console to specify whether you want Oracle Service Bus to enforce WS-I compliance for the service. When you configure WS-I compliance for a proxy service, WS-I compliance checks are performed when the proxy service receives a message as a response from an invoked service with a Service Callout, a route node, or on a proxy service.

For information about the types of messages to which the compliance checks are applied and the nature of those checks, see Section 37.16, "WS-I Compliance."

Web Services Security

Security using Oracle WSM Policies

  • WS-Security 1.0 and 1.1

  • WS-Security: Username Token Profile 1.1

  • WS-Security: X.509 Token Profile 1.1

  • WS-Security: SAML Token Profile 1.1 (with SAML 1.1 in 11.1.1.3), (with SAML 2.0 in 11.1.1.4)

  • WS-Security: Kerberos Token Profile 1.1

  • Policy Advertisement and recognition:

  • WS-Policy 1.2 (11.1.1.3), 1.5 (11.1.1.4)

  • WS-PolicyAttachment 1.2 (11.1.1.3), 1.5 (11.1.1.4)

  • WS-SecurityPolicy 1.1 (11.1.1.3); 1.2 and 1.3 (11.1.1.4)

Java/Oracle Platform Security Providers (Login Modules)

  • SAML Login Module

  • SAML 2 Login Module

  • Kerberos Login Module

  • Digest Authenticator Login Module

  • X509 Certificate Login Module

  • WSS Digest Login Module

  • User Authentication Login Module

  • User Assertion Login Module

Security using WLS 9.x Policies

  • WS-Security 1.0

  • WS-Security: Username Token Profile 1.0

  • WS-Security: X.509 Token Profile 1.0

  • WS-Security: SAML Token Profile 1.0 (with SAML 1.0 and 1.1)

  • Policy Advertisement and recognition:

  • WS-Policy 1.0 and 1.2 only for WS Transport, which supports WS-ReliableMessaging 1.0

  • WS-PolicyAttachment 1.0 and 1.2 only for WS Transport, which supports WS-ReliableMessaging 1.0

  • WS-SecurityPolicy - WebLogic Server-proprietary format that is based on the assertions described in the December 18, 2002 draft version of the Web Services Security Policy Language (WS-SecurityPolicy 1.0) specification; and 1.2 only for WS Transport, which supports WS-ReliableMessaging 1.0, to define Transport-level Security assertions only.

HTTP

1.01.1

EJB

  • 2.1

  • 3.0

SNMP

  • SNMPv1

  • SNMPv2c

WebLogic JMS

WebLogic Server

  • 8.1 SP4-SP6

  • 9.0, 9.1, 9.2

  • 10.0

  • 10.3.x

Third-party JMS

Any JMS provider that implements the JMS specification is supported through Oracle WebLogic Server as a foreign JMS provider.

Microsoft .NET 1.1 with SOAP 1.1

Style-encoding: document-literal, rpc-encoded

  • Oracle Service Bus supports document-literal and interoperates with .NET services.

  • Oracle Service Bus interoperates with .NET rpc-encoded services in cases of inbound and outbound (routing/publish). In these cases, interoperability is possible regardless of parameter types.

  • Oracle Service Bus Service Callouts may fail to interoperate with .NET rpc-encoded services.

Note: DIME attachments is not supported by Oracle Service Bus.

.NET 1.1 Security Configurations Limitations

The following security configurations in the .NET 1.1 framework are not interoperable with the Oracle Service Bus message-level security:

  • Signing the message body from WebLogic to .NET WSE 2.0 (Webservices Security Extension) is interoperable. However, by default, WSE requires additional headers-for example, WS-Addressing and timestamp. Therefore, to make Oracle Service Bus message-level security for .NET Web services interoperable, you must remove all of the message predicate other than the message body from .NET security policy configuration

  • To ensure Oracle Service Bus interoperability with .NET, the replay detection attribute, <replayDetection>, must be set to disabled on the .NET side.

See also Section 1.4.1, ".NET Interoperability Limitations."

Microsoft .NET 2.0 with SOAP 1.1 and SOAP 1.2

See Section 1.4.1, ".NET Interoperability Limitations."

Microsoft .NET 3.0 with SOAP 1.1 and SOAP 1.2

See Section 1.4.1, ".NET Interoperability Limitations."

Microsoft .NET 3.5 with SOAP 1.1 and SOAP 1.2

See Section 1.4.1, ".NET Interoperability Limitations."

WebLogic JMS Client for Microsoft .Net (for .Net C# client applications)

See Oracle Fusion Middleware Using the WebLogic JMS Client for Microsoft .NET for Oracle WebLogic Server.


1.3 Platform Interoperability

See the Oracle Service Bus Release Notes for the latest information about patches or updates that may be required to support your interoperability scenarios.

Oracle Service Bus interoperates with the platforms described in the following tables.

Table 1-2 Oracle WebLogic Family Platforms

Interoperability Version

Oracle WebLogic Server

  • 10.3.5 (runtime only)

  • 10.3.6

Oracle SOA Suite

  • 11.1.1.3 and later

WS-* and JMS interoperability with WebLogic Platform

  • 8.1 SP4-SP6 (except WS-Security

  • 9.0, 9.1, 9.2 (except WS-Security)

  • 10.0 (except WS-Security)

  • 10.3.x

Web Services for Remote Portlets (WSRP) with Oracle WebLogic Portal

  • 9.2

  • 10.0

  • 10.2

  • 10.3.x

Oracle WebLogic Portal

  • 8.1 SP6

  • 9.2

  • 10.0

  • 10.2

  • 10.3

WebLogic Integration

  • 8.1 SP6

  • 9.2

  • 10.2

  • 10.3

MQ event generator and control in WebLogic Integration

  • 8.1 SP4 or later

  • 9.2


Table 1-3 Oracle Family Platforms

Interoperability Version

Oracle Service Bus

  • 2.6

  • 2.6 RP1

  • 3.0

  • 10gR3 (10.3)

  • 10.3.1

  • 11.1.1.3 and later

Oracle Enterprise Pack for Eclipse (OEPE)

11.1.1.8.0 on Eclipse 3.7.1

Oracle Enterprise Repository

  • 2.6

  • 3.0 RP1

  • 10.3

  • 11.1.1.3 and later

Oracle Service Registry

  • 3.0

  • 11.1.1.3

Oracle Enterprise Security

  • 3.0

  • 10.3

Oracle Web Services Manager

  • 10.1.3.x and later

  • 11.1.1

Oracle BPEL Process Manager

  • 10.1.3.4.x and later

Oracle JDeveloper (for developing adapter artifacts)

  • 11.1.1.3 and later

Oracle JCA Adapter for AQFoot 1  Foot 2 

  • 11.1.1.3 and later

Oracle JCA Adapter for DatabaseFootref 1 Footref 2

  • 11.1.1.3 and later

Oracle Adapter for Oracle ApplicationsFootref 1 Footref 2

  • 11.1.1.3 and later

Oracle JCA Adapter for Files/FTPFootref 1 Footref 2

  • 11.1.1.3 and later

Oracle JCA Adapter for SocketsFootref 1 Footref 2

  • 11.1.1.3 and later

Oracle BAM Adapter (Business Activity Monitoring)Footref 1 Footref 2

  • 11.1.1.3 and later

PeopleSoft (Oracle Application Adapters)

  • 11.1.1.4 and later

SAP R/3 (Oracle Application Adapters

  • 11.1.1.4 and later

Siebel (Oracle Application Adapters

  • 11.1.1.4 and later

J.D. Edwards (Oracle Application Adapters

  • 11.1.1.4 and later

Oracle Data Service Integrator

  • 2.5

  • 3.0 (on WebLogic Server 9.2)

  • 3.01 (on WebLogic Server 9.2)

  • 3.2 (on WebLogic Server 10.0.1)

  • 10g Release 3

Oracle Tuxedo/WebLogic Tuxedo Connector

  • 8.1

  • 9.x

  • 10.0


Footnote 1 You must develop these adapters using Oracle JDeveloper 11.1.1.3 or later with Oracle SOA plug-ins installed.

Footnote 2 These adapters are installed by default with Oracle Service Bus. Other adapters must be downloaded and installed separately from Oracle Software Delivery Cloud and require additional licensing.

Table 1-4 Third-Party Platforms

Interoperability Version

IBM WebSphere MQ

  • 7.0

  • 7.0.1.8

Supported with SOAP 1.1, not SOAP 1.2.See Section 1.4.3, "WebSphere Interoperability Limitations."

Note: Versions 5.3 and 6.0 are no longer supported by IBM. These versions are deprecated in Oracle Service Bus.

IBM WebSphere EJB/RMI

6.0

IBM WebSphere WS

6.1 (Fixpack 15)

Supported with SOAP 1.1, not SOAP 1.2.See Section 1.4.3, "WebSphere Interoperability Limitations."

Tibco Enterprise Message Service

All versions that meet the JMS 1.2 specification through Oracle WebLogic Server

Apache Axis

  • 1.2.1

  • 1.4.1

Supported with SOAP 1.1, not SOAP 1.2.See Section 1.4.2, "Apache Axis Interoperability Limitations."

BMC Patrol

http://www.softwareinnovations.co.uk/products/patrol.html


1.4 Platform Interoperability Limitations

This section describes interoperability limitations with different platforms.

1.4.1 .NET Interoperability Limitations

  • .NET clients that need to communicate with Oracle Service Bus using basic authentication must send the authentication information in the first request. Otherwise, the invocation fails because Oracle Service Bus does not challenge the .NET client for credentials.

  • Oracle Service Bus interoperability with .NET using Basic Authentication works successfully when configured with Windows 2003/IIS 6.0; however, interoperability with .NET using Basic Authentication on Windows XP/IIS 5.1 is not supported.

  • Message-level security interoperability for .NET clients works only with SOAP 1.1. The WSE Soap Protocol Factory does not support security with SOAP 1.2. See "Message-Level Security with .Net 2.0" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.

1.4.2 Apache Axis Interoperability Limitations

Unresolved references when you import RPC-encoded Axis-generated WSDLs

When you import an RPC encoded WSDL, generated by Axis, into Oracle Service Bus, you may experience a warning message indicating that the WSDL contains references that must be resolved.

If you open the structural view of the imported WSDL in the View a WSDL page in the Oracle Service Bus Administration Console, unresolved schema imports are displayed in the Imports section.

This issue does not affect your ability to use the WSDL in the Oracle Service Bus environment. You can eliminate the warning by removing unresolved schemas from the WSDL file.

SOAPAction attribute in Axis-generated WSDLs initialized to empty string

The WSDL generated by Axis have the SOAPAction attribute initialized to an empty string. Configuring an Oracle Service Bus business service with this WSDL, causes invocations to this web service to fail generating a "No SOAPAction" fault.

To work around the issue and ensure successful web service invocations from Oracle Service Bus to Axis, you must configure a transport header in the proxy service message flow Specifically, you must add a Set Transport Headers request action in the message flow route and enable the Pass all headers through Pipeline option.

This issue also causes invocations from the Oracle Service Bus Test Console to fail (and generates a "No SOAPAction" fault) even when the workaround is in place. To make Test Console invocations work, you must set the SOAPAction HTTP header in the Set Transport Header request action in the message flow route.

HTTP response and status code for one-way operations

For both document literal and RPC encoded types of web services, on invocation of a one-way operation, Axis is expected to send an empty HTTP response with status code 202 OK to the client. However, Axis sends an non-empty HTTP response with status code 200 OK. The body of this HTTP response contains an empty SOAP envelope.

This causes the Oracle Service Bus proxy or business service to send the same 200 OK response code to their clients violating the expected results.

HTTP response and status code for nne-way operations generating a fault

For both document literal and RPC encoded types of web services, on invocation of a one-way operation generating a fault, Axis is expected to send an empty HTTP response with status code 202 OK to the client. However, Axis sends a non-empty HTTP response with status code 500 Internal Server Error with an empty SOAP envelope as a body.

This causes the Oracle Service Bus proxy or business service to send the same 500 Internal Server Error response to their clients violating the expected results.

1.4.3 WebSphere Interoperability Limitations

HTTP response and status code for one-way operations

For both document literal and RPC encoded types of web services, on invocation of a one-way operation, WebSphere is expected to send an empty HTTP response with status code 202 OK to the client. However, WebSphere sends an non-empty HTTP response with status code 200 OK. The body of this HTTP response contains an empty SOAP envelope.

This causes the Oracle Service Bus proxy or business service to send the same 200 OK response code to their clients violating the expected results.