SOA and ESB advantage

SOA  advantage
1.industry adoption of Web services as a way to rapidly expose and enable new and legacy services, and the creation of toolkits and infrastructure that support loosely coupled service interactions.

2 .Rather than incur the cost and complexity of replacing an existing infrastructure, enterprises choose to extend existing business applications as services so they can be used in other business processes and applications.

AquaLogic Service Bus Core Feature Set

For this feature...	AquaLogic Service Bus...
Routing	Supports the following: Routes messages according to XQuery-based policies or callouts to external services Routing policies apply to both point-to-point and one-to-many routing scenarios (publish). For publish, routing policies serve as subscription filters Routing table abstracted from proxy services enables you to modify routes without having to re-configure proxy service definitions. Identity-based routing allows you to classify clients into user-defined groups and apply routing policies based on these groups.
Routing Transport Protocols	Supports the following: File FTP HTTP(S) JMS (including MQ using JMS, and JMS/XA) E-mail (POP/SMTP/IMAP) EJB/RMI Tuxedo Local (BEA Proprietary for inter-ESB communication) Transport SDK provided enables you to add your own, native custom connectivity options to AquaLogic Service Bus.
Messaging	Supports the following models: Synchronous Asynchronous Publish Subscribe
Message Types	Supports the following message formats: E-mail with or without attachments JMS with headers MFL (Message Format Language) Raw Data. Raw data is opaque data—that is, non-XML data for which there is no MFL file and therefore no known schema Text SOAP and SOAP with attachments (SOAP that is or is not described by a WSDL) XML and XML with attachments ((XML that is or is not described by a WSDL or a schema)
Transformations	Supports the following functionality for the transformation or processing of messages: Validates incoming messages against schemas Selects a target service or services, based on the message content or message headers Transforms messages based on the target service Transforms messages based on XQuery or XSLT Supports transformations on both XML and MFL messages Message enrichment Supports call outs to Web services to gather additional data for transformation (for example, country code, full customer records, and so on)
Testing	Provides a built-in test console in the development environment: Allows you to test resources and inline XQuery expressions used in the message flow Allows you to test business services and proxy services Provides tracing of the message flow when you test a service using the test console
Logging and Monitoring	Provides a rich set of functionality to audit and monitor services: You can gather statistics about message invocations, errors, performance characteristics, messages passed, SLA violations, and so on You can send SLA-based alerts as SNMP traps. This enables integration with third-party ESM solutions. The system supports logging selected parts of messages for both systems operations and business auditing purposes, search capabilities, and so on. You can extract key information from a message and use as it as a search index. The AquaLogic Service Bus Console provides a cluster-wide view of service status and statistics Both business services and AquaLogic Service Bus proxy services are monitored, as are response times, message counts, and error counts Statistics are gathered locally, then aggregated centrally SLA rules run against aggregated data. The system raises alerts, and you can enable or disable services. JMX Monitoring API provided as a polling interface for the retrieval of metrics. 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.
Versioning	Provides the ability to deploy new versions of services and allow 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, and the security parameters.
Service Level Agreements	Administrators can set service level agreements (SLAs) on the following attributes of proxy services: Average processing time of a service Processing volume Number of errors, security violations, and schema validation errors Administrators can configure alerts for SLA rule violations
Security	Includes the following: Supports authentication, encryption and decryption, and digital signatures as defined in the Web Services Security (WS-Security) specification Uses SSL to support traditional transport-level security for HTTP and JMS transport protocols Supports one-way and two-way certificate based authentication Supports HTTP basic authentication allows you to encrypt and export resources (such as service accounts, proxy service providers, UDDI registries, SMTP providers, and JNDI providers) that contain username and passwords. Allows you to create service accounts and proxy service providers within a session, and add the user name, password, and credential alias binding within the same session. Allows you to configure a service account to pass through user ID and password credentials or map the user to a new user ID and password supplied to a business service.
Error Handling	Supports the following: Allows you to configure your system to format and send error messages, and return messages for consumers of services who expect a synchronous response Allows you to configure error handling for stages in the pipeline, for pipelines, and for proxy services Allows you to generate alerts based on message context in a pipeline, to send to an alert destination.
Resource Cache	Supports the following: Stores information about services, schemas, transformations, WSDLs (Web Service Definition Language), and WS Policies Provides centralized management and distributed access to resources and services Allows you to browse the services registered in AquaLogic Service Bus and import resources from WebLogic Workshop or other applications Allows the propagation of configuration data from environment to environment (for example, from a development domain to a test domain to a production domain). The system allows environment specific settings to be overridden during import. Allows for better synchronization and notification capabilities. Services can be auto-published to UDDI after you create or change them within AquaLogic Service Bus. Any changes to a UDDI service within the UDDI registry (that was originally synchronized with AquaLogic Service Bus) results in notification within AquaLogic Service Bus, prompting you to re-synchronize if you want to absorb the changes within ALSB.For more information about UDDI registries, see UDDI.