Oracle Enterprise Service Bus
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
Oracle Enterprise Service Bus (Oracle ESB), a fundamental component of Oracle's Services-Oriented Architecture suite of products, provides seamless integration of data and enterprise applications within an organisation and their connected ( "extended" or “virtual”) enterprises.
This release of Oracle Retail Integration Bus (RIB) Essentials includes changes in architecture, technology stack, and deployment Oracle ESB is technically an 'enterprise service bus' designed and implemented in an Oracle Fusion Architecture's SOA environment; to simplify the interaction and communication between existing Oracle products, third-party applications, or any combination of these.
As a software architecture model for distributed computing it is a specialty variant of the more general client server software architecture model and promotes strictly asynchronous message oriented design for communication and interaction between applications. Its primary use is in Enterprise Application Integration of heterogeneous and complex landscapes of an organisation, and thus enabling its easy management.
An ESB service is designed and configured with Oracle JDeveloper and Oracle ESB Control user interfaces. It is then registered to an ESB Server. The ESB Server supports multiple protocol bindings for message delivery, including HTTP/SOAP, JMS, JCA, WSIF and Java, using synchronous/asynchronous, request/reply or publish/subscribe models. Currently, the ESB Server does not support Remote Method Invocation.
Oracle Retail Integration Bus (RIB) Essentials should not be confused with Oracle Service Bus (OSB). ESB was developed by Oracle. OSB, formerly known as Aqualogic Service Bus, was acquired when Oracle bought BEA Systems. The two products are related and interchangeable.
Oracle Enterprise Service Bus contains the following components:
- ESB Server
- Oracle ESB Control
- ESB Metadata Server
- Oracle JDeveloper
Oracle Enterprise Service Bus application-integration features fall into the following categories:
- Server Capabilities
- Document Transformation : XSLT and MFL
- Content-Based and Header-Based Routing
- Tight integration with Oracle BPEL Process Manager
- Management and Monitoring Capabilities
- ESB Control, the central point for metadata and configuration changes that take effect immediately
- Visual representation of end-to-end service relationships
- Minimal overhead end-to-end message instance tracking and monitoring
- Error Hospital - automated and manual means for individual and bulk message replays
- "Oracle Fusion Middleware and Oracle Fusion Applications : Overview". oracleappshub.com. Retrieved 10 March 2012.
- "Enterprise Service Bus/Service Oriented Architecture". middleware.org. Retrieved 10 March 2012.