Oracle Service Bus

Oracle Service Bus, available as a separate download with an Oracle SOA Suite license, is an intermediary that processes incoming service request messages, determines routing logic, and transforms these messages for compatibility with other service consumers. It receives messages through a transport protocol such as HTTP(S), JMS, File, and
FTP, and sends messages through the same or a different transport protocol. Service response
messages follow the inverse path.

Oracle Service Bus connects, mediates, and manages interactions between heterogeneous services, not just Web services, but also Java and .Net, messaging services and legacy endpoints. It uniquely delivers the integration capabilities of an Enterprise Service Bus (ESB) with operational service management in a single product with an efficient, seamless user experience. With its flexible deployment options and automated integration with Oracle SOA Governance Suite, Oracle Service Bus handles the deployment, management and governance challenges of implementing SOA from department to enterprise scale.

Specifically, Oracle Service provides the following functional areas:

• Management: Provides embedded service management capabilities that provide optimized governance of all messaging. Its preemptive support ensures that mission-critical business processes continue to serve customer needs, even as business demands, requirements, and workloads change.
• Mediation: Provides a rich environment for content-based routing, message transformations, and lightweight orchestrations.
• Adaptive Messaging: Reliably connects any service by leveraging standards Web service transports, traditional messaging protocols and configuration of enterprise-specific custom transports.
• Security: Provides a rapid service configuration and integration environment that abstracts policies associated with routing rules, security, and service end-point access.

Comparing Oracle Mediator with Oracle Service Bus

Oracle Mediator is an intra-composite mediation component that is deployed within a composite, keeping the composite on a canonical model. Its primary function is to provide the transformation of legacy formats to a common format. It is responsible for brokering communications between components that make up a composite, enabling transformation, routing, event delivery, and payload validation inside the composite.