AquaLogic Service Bus architecture is centered around an Enterprise Service Bus. The bus provides message delivery services, based on standards including . BEA Systems, Inc. was a company specialized in enterprise infrastructure software products . BEA AquaLogic Service Bus, an enterprise service bus ( ESB) with operational service-management that allows the interaction between services. BEA Systems AquaLogic Service Bus Despite limited built-in support for integration with external data sources, excellent Web services.
|Published (Last):||6 September 2012|
|PDF File Size:||16.37 Mb|
|ePub File Size:||6.17 Mb|
|Price:||Free* [*Free Regsitration Required]|
This section provides an architectural overview of AquaLogic Service Bus and highlights operational features that enable rapid service integration, provisioning, and management across a heterogeneous IT infrastructure. It is intended for integration-focused IT architects responsible for messaging and service oriented architectures SOA.
It includes the following sections:. It is typically designed for high-throughput, guaranteed message delivery to a variety of service producers and consumers. It supports XML wervice a native data type, while also offering alternatives for handling other data types.
AquaLogic Service Bus is policy driven and enables you to establish loose coupling between service clients and business serviceswhile maintaining a centralized point of security control and monitoring. It stores persistent policy, proxy service, and related resource configurations in metadata, that can be customized and propagated from development through staging to production aervice required.
The message-brokering engine accesses this configuration information from its metadata cache. AquaLogic Service Bus is an intermediary that segvice incoming service request messages, determines routing logic, and transforms these messages for compatibility with other service consumers.
Service response messages follow the inverse path. The message processing by AquaLogic Service Bus is driven by metadata, specified in the message flow definition of a proxy service.
Aqualoogic following high-level architecture diagram illustrates AquaLogic Service Bus and zqualogic functional subsystems: Messages can contain data or status information about application processes, or instructions for the recipient, or both.
AquaLogic Service Bus enables you to route messages based on their contents and to perform transformations on that content. The processing happens through the transport and binding layers of AquaLogic Service Bus. The processing of messages aqulogic in the following sequence of events:.
After a message is sent to an endpoint either a business service or another proxy serviceAquaLogic Service Bus processes the response message in a similar model as that described in the preceding sequence of events. The following figure illustrates a high-level message flow process through the AquaLogic Service Bus, from inbound endpoint proxy service to outbound endpoint service transport URL – a business service or another proxy service.
The following sections describe each layer involved in this message processing. The inbound transport layer is the communication layer between client services or service consumers and AquaLogic Service Bus. It is responsible for handling communication with the service client endpoint and acts as the entry point for messages into AquaLogic Service Bus.
It is not involved in data processing but is responsible for returning response messages to service consumers and handles meta-data for messages, including endpoint URIs, transport headers, etc. The outbound transport layer is responsible for the communication between business services or service producers and AquaLogic Service Bus. It is responsible for moving messages from AquaLogic Service Bus to the business service or proxy service and for receiving the response from the services.
It is not involved in data processing but handles meta-data for messages, including endpoint URIs, transport headers, etc. They are the interface that service consumers use to connect with managed back-end services.
Proxy services are definitions of intermediary Web services that the Service Bus implements locally. Message processing logic is specified in message flow definitions when defining a proxy service.
For more information on proxy services, see Proxy Services. The context of a proxy service is a set of XML variables that are shared across the request flow and response flow. New variables can be dynamically added or deleted to the context.
Predefined context variables contain information about the message, transport headers, security principles, metadata for the current proxy service, and metadata for the primary routing and publishing services invoked by the proxy service.
Aqualogic Service Bus – How is Aqualogic Service Bus abbreviated?
The context can be read and modified by XQuery expressions and updated by transformation and in-place update actions. Since a proxy service can route messages to multiple business services, a proxy service can be configured with an interface that is independent of the business services it communicates with. Using generic proxy templates, the proxy service can be a configured as a message-flow definition that dynamically routes messages to appropriate business services based on content-based routing logic.
A proxy service can also map message data into appropriate protocol formats required by the end-point business service, allowing for dynamic run-time protocol switching. For more information on proxy templates, see Service Composition in the Concepts and Architecture Guide. The implementation of a proxy service is specified by a message flow definition.
The message flow defines the flow of request and response messages through the proxy service. The following four elements are used to construct a message flow:. Message flow elements can be combined in arbitrary ways to form a tree structure with the start node always and only occurring as the root of the tree and the route nodes. The last nodes in a branch leaf nodes may be route nodes or echo nodes. The request message starts at the start node and follows a path to a leaf node, executing actions in the request pipelines.
If the leaf is a route node, a response is generated could be empty if the service is a one way service. If the leaf is an echo node, the request is also considered to be the response.
The response follows the inverse path in the tree skipping actions in the branch nodes, but executing actions in response pipelines. A set of transformations that affects context variables can be defined before the message is sent to the selected endpoint or after the response is received. WS-Security processing as well as authorization is transparently performed at the Start node, when invoking a business service with a WS-policy.
By fusing the concepts of the ESB, message brokering, and operational services management into a single product, BEA AquaLogic Service Bus allows management and integration of messages and services across a services network. Its core functional features are separated into the following categories:. To support heterogeneous environments, AquaLogic Service Bus accommodates multiple messaging paradigms.
It supports the following types of communication:. A high performance message broker is a core component of AquaLogic Service Bus. It enables content-based routing of messages and data transformation. AquaLogic Service Bus message brokering capabilities are implemented with the following operational features:. All routing logic pertaining to communications with a service end point is handled via the configured proxies.
This frees service consumers from having to understand any of the complexities of communicating with back-end services. Decoupling the routing, transformation, security, and transport details from the service consumers and providers and placing them within configurable proxy services, provides for more flexible service integration.
AquaLogic Service Bus supports dynamic content-based routing of messages and run-time protocol selection. It facilitates these capabilities by allowing the configuration of proxy services with interfaces that are independent of the end-point business services.
Using generic proxy templates, proxy services can be configured as message-flow definitions with routing logic that dynamically route messages to appropriate business services, based on message content. AquaLogic Service Bus supports the following capabilities for the transformation or processing of messages:. AquaLogic Service Bus provides a service callout action that offers greater flexibility for more sophisticated message flows for complex dynamic-routing processing, or to perform message enrichment.
BEA AquaLogic Service Bus™
The service callout action is used inside a message flow routing stage, to call on the destination service to perform some action on the message. This can be used for message enrichment, for routing decisions or dervice customizing the behavior of a proxy service.
Read-access to databases from proxy services is supported without requiring writing of a custom EJB or custom Java code and without the need for a separate database product like AquaLogic Data Services Platform. It is implemented using the execute-sql function to make a JDBC call to a database to perform simple database reads. This allows a more efficient and flexible approach to accessing data services than exposing them as Web services via WebLogic Workshop and Java Web Services JWSand it supports security and identity propagation.
An EJB can be exposed as a Web service, without the need for tools or the modification of the legacy code on the application server that nus the EJB. The EJB transport provides the following capabilities:.
AquaLogic Service Bus supports open industry standards for ensuring the integrity and privacy of communications and to ensure that only authorized users can access resources in an AquaLogic Service Bus domain. It uses the underlying WebLogic security framework as building blocks for its security services. The WebLogic security framework divides the work of securing a domain into several components providerssuch as authentication, authorization, credential mapping, and auditing.
AquaLogic Service Bus provides the following security features:. The Aqyalogic Service Bus security model includes the following:. The Change Center has the unique ability to lock its current configuration while changes are being made, letting the service bus continue to receive and process requests for services while configuration changes are being made in the console.
The service bus uses the new service and resource configuration when changes are activated. This way, ongoing changes can be made without disrupting services. AquaLogic Service Bus built-in test console is a browser-based test environment used to validate resources and inline XQuery expressions used in the message flow. Using the test console, it is possible to configure the test object proxy service, business service, XQuery, XSLT, MFL resourceexecute the test, and view test results.
It allows message flow tracing when testing a service, to examine the state of the message at specific trace points. Design time testing helps isolate design problems before deploying a configuration to a production environment. The test console can test specific parts of a system in isolation and it can test a system as a unit. AquaLogic Service Bus provides the following resource management capabilities:. The supporting APIs allow loading ZIP files containing resources, in addition to moving, renaming, cloning, or deleting resources, folders and projects.
AquaLogic Service Bus supports the following error handling capabilities:. AquaLogic Service Bus allows the following capabilities for auditing and monitoring services:. Both business services and AquaLogic Service Bus proxy services are monitored, as are response times, message counts, and error counts.
This API enables integration with management partners and enables customers who have their own monitoring consoles to display metrics that can be used for performance analysis. It provides operational functions and settings that allow users to easily search for resources using the new SMart Search functionality, monitor SLA alerts, pipeline alerts, logs, reports, turn tracing on and off, and to enable and disable services.
Operators have privileges to edit operational settings, create new SLA alert rules, and create and edit alert destination resources.
AquaLogic Service Bus provides the ability to deploy new versions of services and allows you to have multiple versions of message resources such as WSDLs and schemas. Versions can include changes to the WSDL, the message schema, the headers, aquallgic the security parameters.
In AquaLogic Service Bus, monitoring statistics are gathered locally and aggregated centrally. SLA rules are run against aggregated data and the system raises buw, following which services can be enabled or disabled.
BEA Systems – Wikipedia
Administrators can set service level agreements SLAs on the following attributes of proxy services:. AquaLogic Service Bus is designed to centrally manage and control many distributed service endpoints.
These bhs have their own sets of configuration artifacts such as services and transformations. Such deployments typically map to various IT departments within an organization.