|
|
BEA AquaLogic Service Bus and BEA Tuxedo can interoperate to use the services that each product offers. The Tuxedo transport allows secure, guaranteed, high performance, bi-directional access to a Tuxedo domain from BEA AquaLogic Service Bus. The Tuxedo transport allows Tuxedo domains to call services as well as have services called in a Tuxedo domain.
You configure the Tuxedo transport using the AquaLogic Service Bus Console. Specific parameters provide definitions for both proxy and business services. A basic WebLogic Tuxedo Connector (WTC) configuration with one local access point and one remote access point is required to enable configuration of the Tuxedo transport. Support for transactional and security contexts are available as well.
The following diagram summarizes this message handling processes.
The following capabilities are available in the native Tuxedo transport in BEA AquaLogic Service Bus.
The native Tuxedo transport is fully integrated into the BEA AquaLogic Service Bus configuration, management, and monitoring console. You can configure, manage, and monitor both Tuxedo proxy services and Tuxedo businesses services.
AquaLogic Service Bus is an intermediary between SOAP, JMS, or other services and Tuxedo. The Tuxedo transport enables access to Tuxedo ATMI services as business services in AquaLogic Service Bus and allows AquaLogic Service Bus proxy services to be seen by Tuxedo as another ATMI service.
You can transform XML messages to Tuxedo buffer types and Tuxedo buffer types to XML. All standard Tuxedo buffer types are supported; transformation is automatic and transparent. For more information, see Tuxedo Transport Buffer Transformation.
Tuxedo transport provides transactional integrity for inbound and outbound messages. You can call Tuxedo services in the context of a global transaction allowing Exactly Once quality of service (QoS). A Tuxedo application can start a transaction, call an AquaLogic Service Bus-based service and the XA transaction context is carried through to AquaLogic Service Bus, through the pipeline, and finally to the destination transport. For more information, see Tuxedo Transport Transaction Processing.
The security context established at the beginning of the message flow, from either a Tuxedo client or an AquaLogic Service Bus client, is propagated to the other system. This means that an incoming SOAP over HTTP request to AquaLogic Service Bus that requires authentication is authenticated by AquaLogic Service Bus. As with transactions, this support is fully bi-directional, so a client authenticated to Tuxedo can make requests to AquaLogic Service Bus services without requiring authentication a second time.
You can encrypt the connections between AquaLogic Service Bus and Tuxedo through WTC configuration to ensure the security and privacy of communications between the two systems.
A single network connection is the only requirement to connect AquaLogic Service Bus to a Tuxedo domain. However, it might be necessary to support multiple connections in case of a machine or network failure. You can make multiple connections to a single domain or multiple domains for purposes of load balancing.
See the following sections for detailed information on configurations for the following scenarios:
You can use the following related documentation to learn more about this environment:
|