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 messages)
No issues specified. Please specify issues, or remove this template. |
Oracle Enterprise Service Bus is a fundamental component of Oracle's Services-Oriented Architecture that provides a loosely-coupled framework for inter-application messaging.
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 Enterprise Service Bus (ESB) should not be confused with Oracle Service Bus (OSB). ESB was developed by Oracle. OSB, formally known as Aqualogic Service Bus, was acquired when Oracle bought BEA. The two products are related and interchangeable.
Components
Oracle Enterprise Service Bus contains the following components:
- ESB Server
- Oracle ESB Control
- ESB Metadata Server
- Oracle JDeveloper
Features
Oracle Enterprise Service Bus application-integration features fall into the following categories:
- Server Capabilities
- Connectivity
- Document Transformation
- 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