|
|
Oracle Service Bus is an Enterprise-class Service Bus designed for connecting, mediating and managing interactions between heterogeneous services. Oracle Service Bus helps accelerate service configuration, integration and deployment, and simplifies management of shared services across the SOA.
Oracle Service Bus supports broad compliance with messaging standards including SOAP 1.1 and 1.2, HTTP, JMS, SMTP/POP/IMAP, FTP, SSL, XML 1.0, XML Schema, WSDL 1.1, WSRP 1.0, and WS-Security.
This section includes information about Oracle Service Bus interoperability. It includes the following topics:
For support information on vendor operating systems, JDK, hardware, and database support, see Supported Configurations for Oracle Service Bus.
Oracle Service Bus supports the following standards and implementations.
|
|
Oracle Service Bus supports a WebLogic Server-proprietary format that is based on the assertions described in the December 18, 2002 version of the Web Services Security Policy Language (WS-SecurityPolicy) specification. For information about supported Web Services Security Policy Assertions and Reliable Messaging Assertions, see the Oracle Service Bus Security Guide. For more information, see Securing Oracle Service Bus with Oracle Web Services Manager in the Oracle Service Bus Security Guide. |
|
Oracle complies with the
Basic Security Profile Version 1.0 specifications from the Web Services Interoperability Organization a (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 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 “WS-I Compliance” in
Modeling Message Flow in Oracle Service Bus in the Oracle Service Bus User Guide.
|
|
The following security configurations in the .NET 1.1 framework are not interoperable with the Oracle Service Bus message-level security:
|
|
| Note: | 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 table.
For information about Oracle Service Bus and JMS interoperability, see Oracle Service Bus Interoperability Solutions for JMS.
|
||
For information about Oracle Service Bus and WSRP interoperability, see Oracle Service Bus Interoperability Solutions for WSRP.
|
||
To learn about importing and exporting business services from and to UDDI Registries in general, and Oracle Service Registry in particular, see UDDI in the Oracle Service Bus User Guide.
|
||
Oracle Enterprise Security can be used to manage access control to the Oracle Service Bus runtime resources, using the Oracle Enterprise Security WebLogic Server 9.x Security Service Module. For more information, see
Integrating Oracle Enterprise Security with Application Environments.
|
||
For information about Oracle Service Bus and Oracle Tuxedo interoperability, see Oracle Service Bus Interoperability Solution for Tuxedo.
|
||
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 Console, unresolved schema imports are displayed in the Imports section.
Note that 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.
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 workaround 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.
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.
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.
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.
|