Architecture, Jargon and Resources

Oracle Service Bus

Service Bus IDE UI OEPE/Eclipse OSB

Service Bus console Lightweight Portal Framework OSB Runtime Message Action Engine Split-Join Flow Engine
Data Services

Development
Services Common Services Monitoring & Alert Security Framework Resources Test Console

Transport SDK Config Framework User, Credential Access ctrl

Report

WLS

XQuery XBeans

WLS

MDBs JMS

Light Weight Web App

Work Deployment Web Svc Stack Manager Framework

Binding Layer packs and unpacks messages as necessary handles security for messages hands messages off to start the message flows (request and response) Transport Layer (Inbound) communication layer between client services (or service consumers) and Oracle Service Bus deals with raw bytes of message data in the form of input/output streams support for compatible transport protocols, including HTTP(S), JMS, FTP, File, and E-mail Transport Layer (Outbound) communication between business services (or service producers) and Oracle Service Bus not involved in data processing but handles meta-data for messages, including endpoint URIs, transport headers

Proxy Services

Proxy services are a fundamental concept in the architecture of Oracle Service Bus. Proxy services are definitions of intermediary Web services that the Service Bus implements locally. Oracle Service Bus allows configuration of a proxy service by defining its interface in terms WSDLs and the type of transport it uses. Message processing logic is specified in message flow definitions when defining a proxy service

Service Service

Service Service

Messaging / Protocols Multiple transports with transport bridging End-to-end guaranteed delivery SOAP, Non-SOAP, ReST, Non-XML support Sync/Async Request/Response, one-to-many publish Endpoint management Priority based Throttling Load balancing and HA Service Bus Security Transport (SSL) & Message (WS-Security) Security Authentication & Authorization Message Integrity & Message Confidentiality Message Brokering Content-based routing SOAP, JMS, MQ - Headers & Content Integrated data transformation XQuery and XSLT transformation support Schema driven console tools to create routing rules Support for non-XML content through MFL Stateless orchestration Configuration Framework Services mediated & proxies exposed by Service Bus Service metadata store Complete validation before deployment Cluster deployment Service Management Monitor system operations with alerts and key monitoring points Service Level Agreements Performance thresholds Error thresholds Pipeline Alert generation Service Management Dashboard Programmatic access to monitoring metrics

Service Management
Monitoring SLA Alerts Reporting JMX

Message Brokering
Content Routing Transformation Stateless Orchestration

Config Framework
Change Center Validation Import/Export UDDI Discovery Repository

Service Bus Security

Authentication Authorization Identity Policy Message Security

Messaging / Protocols
HTTP/S SOAP JMS EJB/RMI MQ SMTP FTP File Tux

Service Service

Service Service

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. The core of the context contains the variables $header, $body, and $attachments. These wrapper variables contain the Simple Object Access Protocol (SOAP) header elements, SOAP body element, and Multipurpose Internet Mail Extensions (MIME) attachments, respectively. The context gives the impression that all messages are SOAP messages, and non-SOAP messages are mapped to this paradigm. The context can be read and modified by XQuery expressions and updated by transformation and inplace update actions

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: A pipeline pair, one for the request and one for the response. The pipelines consist of a sequence of stages that specify actions to perform during request or response processing. A branch node to branch based on the values in designated parts of the message or message context or to branch based on the operation invoked. A route node used to define the message destination. The default route node is an echo node that reflects the request as the response. A start node.

 Synchronous request/reply
Oracle Service Bus

Asynchronous request/reply
Oracle Service Bus
SOAP /HTTP Native MQ Native MQ

SOAP /HTTP

SOAP /HTTP

SOAP /HTTP

JMS Queue

Subscribe Push
Oracle Service Bus
Native MQ Native MQ

Pub-Sub/Broadcast or Fan-out
Oracle Service Bus
Native MQ Native MQ

JMS Queue

JMS Topic

Native MQ

Synchronous Request/reply Asynchronous Request/reply Fan Out Pub-Sub Aggregator and Split-Join
8

Oracle Service Bus 11g Components

Service Clients Application Client transport

Oracle Service Bus Proxy Service Business Service transport

Enterprise Services Service

Inbound interface Service Brokering

Outbound interface

10

Service Clients
Application Client Application Client Application Client Application Client Application Client HTTP/SOAP JMS FTP REST File

Oracle Service Bus

Service Messaging
WS-RM TUX

Enterprise Services
Service Service Service Service Service

Request / Response Synch / Asynch Split / Join Publish / Subscribe

MQ EJB JCA

Any to Any Protocol Any to Any Payload XML non-XML Binary No WSDL Required

Multiple communications paradigms Request/response Synchronous and asynchronous One-to-many, many-to-one Pub-sub Mix-and-match (e.g. sync-to-async)

11

Adapter Certifications Packaged with OSB install AQ Database EBusiness Suite Packaged separately SAP PeopleSoft Siebel JD Edwards

12

13

Dynamic publish Publish Publish table Routing options Service callout Transport headers

Publish a message to a service specified by an XQuery expression. Identify a statically specified target service for a message and to configure how the message is packaged and sent to that service. Publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publish. Modify any or all of the following properties in the outbound request: URI, Quality of Service, Mode, Retry parameters, Message Priority. Configure a synchronous (blocking) callout to an Oracle Service Bus-registered proxy or business service. Set the header values in messages

14

For each If Then Raise error Reply Resume Skip

Iterate over a sequence of values and execute a block of actions Perform an action or set of actions conditionally, based on the Boolean result of an XQuery expression. Raise an exception with a specified error code (a string) and description. Specify that an immediate reply be sent to the invoker. Resume message flow after an error is handled by an error handler. This action has no parameters and can only be used in error handlers. Specify that at run time, the execution of this stage is skipped and the processing proceeds to the next stage in the message flow

15

Assign Delete Insert Java callout MFL transform Rename Replace Validate

Assign the result of an XQuery expression to a context variable. Delete a context variable or a set of nodes specified by an XPath expression. Insert the result of an XQuery expression at an identified place relative to nodes selected by an XPath expression. Invoke a Java method, or EJB business service, from within the message flow. Convert message content from XML to non-XML, or vice versa, in the message pipeline Rename elements selected by an XPath expression without modifying the contents of the element. Replace a node or the contents of a node specified by an XPath expression. The node or its contents are replaced with the value returned by an XQuery expression Validate elements selected by an XPath expression against an XML schema element or a WSDL resource

16

Service Clients Application Client

HTTP/SOAP

Oracle Service Bus Proxy Validate Error Code Business

Enterprise Services Service

Error-handling Features Technology Errors/Faults Validation Errors Security Errors: authentication, authorization, signing, decryption Process SOAP Faults Raise Error on Custom-Defined Conditions Enrich Custom Error Messages for invoking services Search/Report by Error Conditions

Error-handlers at Service, Pipeline and Stage level

17

18

19