|
|
AquaLogic Service Bus is an Enterprise-class Service Bus designed for connecting, mediating and managing interactions between heterogeneous services. AquaLogic Service Bus helps accelerate service configuration, integration and deployment, and simplifies management of shared services across the SOA.
AquaLogic 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 AquaLogic Service Bus interoperability. It includes the following topics:
The following table summarizes the versions of the platforms, standards, FTP servers, and so on, that are certified to interoperate with AquaLogic Service Bus.
|
||
|
||
|
Supported Database Configurations in Supported Configurations for AquaLogic Service Bus
|
1AquaLogic Service Bus supports the WSDL 1.1 Binding Extension for SOAP 1.2 as specified in http://schemas.xmlsoap.org/wsdl/soap12/WSDL11SOAP12.pdf 2ALSB 2.6 RP1 is installed with WebLogic Server 9.2 MP2, but you can upgrade to WebLogic Server 9.2 MP3. The WebLogic Server upgrade requires additional steps for ALSB domains. See the ALSB Upgrade Guide. |
AquaLogic Service Bus is certified against the following FTP and Email servers:
AquaLogic Service Bus is certified against the following security providers:
For more information about managing and configuring AquaLogic Service Bus security, see AquaLogic Service Bus Security Guide.
| Note: | The defaults for WebLogic Server 9.2 are the XACML Authorization provider and XACML Role Mapping provider. |
AquaLogic Service Bus supports the following Web Service standards:
AquaLogic 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. This release of AquaLogic Service Bus does not incorporate the latest update of the specification (13 July 2005). While the WS-Policy specification defines both security and reliable messaging assertions, AquaLogic Service Bus supports only security assertions. The syntax and usage of AquaLogic Service Bus security assertions differ from the WS-Policy specification, but the assertions are similar in meaning and are fully compatible with security assertions used in WebLogic Server 9.0 and 9.1, and 9.2 Web services.
| Note: | BEA AquaLogic Service Bus does not support the following: |
| Note: | – WS-ReliableMessaging assertions |
| Note: | – WS-policy on SOAP faults |
BEA 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, 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 AquaLogic Service Bus User Guide.
AquaLogic Service Bus is certified against the following HTTP protocols:
AquaLogic Service Bus is certified against the following protocols:
To learn more, see XQuery Implementation in the AquaLogic Service Bus User Guide.
AquaLogic Service Bus is certified against the following JMS implementations:
For information about AquaLogic Service Bus and JMS and MQ interoperability, see AquaLogic Service Bus Interoperability Solutions for JMS and WebSphere MQ.
For complete information about supported databases and drivers, see Supported Database Configurations in Supported Configurations for AquaLogic Service Bus.
AquaLogic Service Bus is certified to interoperate with the platforms described in the following table.
Interoperability1
|
||
For information about AquaLogic Service Bus and JMS interoperability, see AquaLogic Service Bus Interoperability Solutions for JMS and WebSphere MQ.
|
||
For information about AquaLogic Service Bus and WSRP interoperability, see AquaLogic Service Bus Interoperability Solutions for WSRP.
|
||
WebLogic Integration2
|
||
ALSB 2.6 RP1 is installed with WebLogic Server 9.2 MP2, but you can upgrade to WebLogic Server 9.2 MP3. The WebLogic Server upgrade requires additional steps for ALSB domains. See the ALSB
Upgrade Guide.
|
||
To learn about importing and exporting business services from and to UDDI Registries in general, and AquaLogic Service Registry in particular, see UDDI in the AquaLogic Service Bus User Guide.
|
||
AquaLogic Enterprise Security can be used to manage access control to the AquaLogic Service Bus runtime resources, using the ALES WebLogic Server 9.x Security Service Module. For more information, see
Integrating ALES with Application Environments.
|
||
For information about AquaLogic Service Bus and BEA Tuxedo interoperability, see AquaLogic Service Bus Interoperability Solution for Tuxedo.
|
||
The following security configurations in the .NET 1.1 framework are not interoperable with the AquaLogic Service Bus message-level security:
|
||
1See the AquaLogic Service Bus Release Notes for the latest information about patches or updates that may be required to support your interoperability scenarios. 2WebLogic Integration 7.0 is not supported with AquaLogic Service Bus. |
|