Вы находитесь на странице: 1из 14

Oracle SOA Suite

11g Components
Agenda
Introduction to Oracle SOA Suite 11g
Oracle SOA Suite Standards
SCA Service Infrastructure
SOA Composite
Message Exchange Pattern
Jdeveloper 11g (Integrated Development Environment)
Application Server and Database Connections Setup
Hello World Example
Enterprise Manager Console
Introduction to Oracle SOA Suite 11g

Oracle SOA Suite 11g benefit from common capabilities, including a single deployment,
management, and tooling model, end-to-end security, and unified metadata management.
Oracle SOA Suite is unique in that it provides the following set of integrated capabilities:

Messaging
Service discovery
Orchestration
Web services management and security
Business rules
Events framework
Business activity monitoring



Oracle SOA Suite Standards

Oracle SOA Suite puts a strong emphasis on standards and interoperability. SOA utilizes
technology and vendor neutral standards like XML, HTTP, and Web Services (WS) that
are heavily backed by all leading software vendors.

Among the standards it leverages are:
Service Component Architecture (SCA) assembly model
Business Process Execution Language (BPEL)
XSL Transformations (XSLT)
Java Connector Architecture (JCA)
Java Messaging Service (JMS)
Web Services Description Language (WSDL) file
Simple Object Access Protocol (SOAP)
Web services management and security


SCA Service Infrastructure

SCA is the executable model for the assembly of service components into composite
applications.
One unified infrastructure to manage.
Aims to provide a model for the creation of service components in a wide range of
languages and a model for assembling service components into a business solution.


SOA Composite

A composite is an assembly of services, service components, wires, and references
designed and deployed together in a single application. The composite processes the
information described in the messages

SOA composite is a standards-based deployment unit
Leverages the SCA assembly model
Can mix variety of components: Mediator, BPEL, Human Workflow, etc.



Message Exchange Patterns
File Transfer Pattern
In this pattern the source application (e.g. Legacy) extracts the data and places the file in the
specified directory as per the requirements in the File Zone. The integration layer will be polling for the
file in regular intervals, once the file is found the integration layer reads the file and does the necessary
transformations as per the business requirements and sends to the target application.
Message Exchange Patterns
Publish-Subscribe Integration Pattern
The Message Based pattern is primarily focused on loose coupling of source and target applications
using publish-subscribe mechanism. The coupling is removed by the publisher of information supporting
a generic interface for subscribers. With this interface, the publisher code does not need to be modified
every time a subscriber is introduced.

Message Exchange Patterns
Request-Reply Integration Pattern
In this pattern the source application in an interface requests data from a provider. The provider can
either be an integration process layer or another system such as Oracle EBS where the integration
process implements the web service interface and invokes the service of the target application.
Requestor (Service Consumer) Sends a request message and waits for a reply message.
Replier/Provider (Service Provider) Receives the request message and responds with a reply
message.



Jdeveloper 11g (IDE)
Wizard based, Drag and Drop development style without writing single line of code.
Tools for all stages of project (Design,Coding,Debugging,Testing and Deployment)
Supports more than 200 adaptors to integrate with various application.

Application Server and DB Connections
Create Application Server connection from Jdeveloper for SOA Composite deployment
deployment.
Create connection to database for importing database objects at design time.


The Attached document provides step by step
instructions to establish connection to application
Server and database from Jdeveloper 11g.


Hello World Example
Case: Create SOA Composite application containing BPEL component to orchestrate simple business
case.
User will enter input and submit the request
BPEL component read the input message and concatenate Hello to the input data.
The result should returned back to the user as response message.




Enterprise Manager Console
Composite Lifecycle : Deploy / Un-deploy / Re-deploy, On / Off, Active / Retired
Instance Tracking : Monitor instance state, track message flow, view payloads
Fault Recovery : Retry / Resubmit faulted instances that are resubmitable.





Thank You!
Q & A

Вам также может понравиться