Interoperability Solutions Guide
|
 |
 |
|
 |
 |
Introduction
AquaLogic Service Bus provides a unified software product for implementing and deploying your Service-Oriented Architecture (SOA).
AquaLogic Service Bus supports broad compliance with messaging standards including SOAP 1.1, HTTP, JMS, SMTP/POP/IMAP, FTP, SSL, XML 1.0, XML Schema, WSDL 1.1, WSRP 1.0, and WS-Security.
This section contains information about AquaLogic Service Bus interoperability. It includes the following topics:
- Summary of Interoperability
- FTP and Email Servers
- Security Providers
- Web Service Standards
- HTTP Standards
- XPath and XQuery
- JMS
- Databases
- Platform Interoperability
Summary of Interoperability
The following table summarizes the versions of the platforms, standards, FTP servers, and so on, that are certified to interoperate with AquaLogic Service Bus.
Table 1-1 AquaLogic Service Bus Interoperability Matrix
|
. . about databases and drivers, see Supported Database Configurations in Supported Configurations for AquaLogic Service Bus |
||
FTP and Email Servers
AquaLogic Service Bus is certified against the following FTP and Email servers:
Security Providers
AquaLogic Service Bus is certified against the following security providers:
- WebLogic Server 9.x default authentication provider
- WebLogic Server 9.x default authorization provider
- WebLogic Server 9.x default credential mapper
- WebLogic Server 9.x PKI credential mapper
- WebLogic Server 9.x PKI credential provider
- WebLogic Server 9.x Java KeyStores (JKS)
- WebLogic Server 9.x default User Name Token and X509 Token handlers
- WebLogic Server 9.1 XACML authorization provider
- WebLogic Server 9.1 XACML Role Mapping provider
- WebLogic SAML Identity Assertion Provider V2
- WebLogic SAML Credential Mapping Provider V2
For more information about managing and configuring AquaLogic Service Bus security, see in Securing Inbound and Outbound Messages in the BEA AquaLogic Service Bus User Guide.
Note: The defaults for WebLogic Server 9.1 are the XACML Authorization provider and XACML Role Mapping provider.
Web Service Standards
AquaLogic Service Bus is certified against the following Web Service standards:
- SOAP 1.1
- WSDL 1.1
- WS-Addressing
- WS-Security using WebLogic Server 9.x WS client or WebLogic Server 9.x business services.
- WSDL attached WS-Policies as supported by WebLogic Server 9.x.
- WebLogic Server 9.x WS-Policy—identity, integrity, confidentiality and timestamp assertions.
WS-I
AquaLogic Service Bus includes WS-I compliance. However, in some cases, AquaLogic 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 AquaLogic Service Bus Console to specify whether you want AquaLogic 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 AquaLogic Service Bus in the BEA AquaLogic Service Bus User Guide.
HTTP Standards
AquaLogic Service Bus is certified against the following HTTP protocols:
- HTTP 1.0
- Transport-Layer Security (TLS) Secure Sockets Layer (/SSL) protocols
Note: TLS/SSL support is the same as for WebLogic Server 9.x
XPath and XQuery
AquaLogic Service Bus is certified against the following protocols:
- BEA's implementation of XQuery 1.0
To learn more, see XQuery Implementation in BEA AquaLogic Service Bus User Guide.
- BEA's implementation of XPath 2.0
JMS
AquaLogic Service Bus is certified against the following JMS implementations:
- WebLogic Server 9.x JMS
For information about JMS interoperability, see Interoperability with JMS.
- IBM WebSphere MQ/JMS 5.3
For information about AquaLogic Service Bus and MQ/JMS interoperability, see Interoperability with WebSphere MQ.
Databases
For complete information about supported databases and drivers, see Supported Database Configurations in Supported Configurations for AquaLogic Service Bus.
Platform Interoperability
AquaLogic Service Bus is certified to interoperate with the following platforms:
- WS-* and JMS interoperability with WebLogic Platform 8.1 SP4 or later (except for WS-Security)
For information about AquaLogic Service Bus and JMS interoperability, see Interoperability with JMS and Interoperability with WebSphere MQ.
- Web Services for Remote Portlets (WSRP) with BEA WebLogic Portal
For information about AquaLogic Service Bus and WSRP interoperability, see Interoperability with Web Services for Remote Portlets (WSRP).
- MQ event generator and control in WebLogic Integration 8.1 SP4 or later
- BEA Tuxedo
For information about AquaLogic Service Bus and BEA Tuxedo interoperability, see Interoperability with BEA Tuxedo.
- BEA AquaLogic Service Registry 2.0
To learn about using AquaLogic Service Registry with AquaLogic Service Bus, see UDDI in the BEA AquaLogic Service Bus User Guide. To learn about AquaLogic Service Registry, see the product documentation at the following URL:
http://download.oracle.com/docs/cd/E13173_01/alsr/docs20/- Microsoft .NET 1.1
- AquaLogic Service Bus supports document-literal and interoperates with .NET services.
- AquaLogic 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.
- AquaLogic Service Bus Service Callouts may fail to interoperate with .NET rpc-encoded services.
- Apache Axis 1.2.1
- IBM WebSphere MQ 6.0
Note: DIME attachments is not supported by AquaLogic Service Bus.
AquaLogic Service Bus is not certified to interoperate with the following platforms:
See the BEA AquaLogic Service Bus Release Notes for the latest information about patches or updates that may be required to support your interoperability scenarios.
