www.Magnifictraining.com-oracle oracle soa online training. contact us: info@magnifictraining.com or call us: +919052666559 oracle soa technologies like oracle soa suite,oracle soa bpel online training,oracle soa 11g online training,oracle soa admin online training,oracle soa bpm training,oracle soa developer training,oracle fusion soa training .real time Oracle scm online training by industrail experts for details call:+919052666559 hands on training on oracle online TRAINING.
1. oracle fusion soa
Online Training in
Africa
CONTACT US:
USA:+1-6786933994,+1-6786933475
INDIA:+91-9052666559,040-69990056
Mail:info@magnifictraining.com
2. High Level Reference Architecture
Composite Applications
Process
Portals
Mashups
Docs
Collab
Business Processes
Orchestration
Services & Event Infrastructure
Connectivity
Legacy
Data Access
ERP
Core
Events
SOA Governance
Partners
SOA Security
Messaging
SOA Management
Systems, data & services Integration
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19. Adaptive
Messaging
Adaptive Messaging In a Nutshell…
Enterprise
Services
Oracle Service Bus
Service
Clients
Service Messaging
Application
Client
Application
Client
JMS
Application
Client
FTP
Application
Client
REST
Application
Client
File
WS-RM
HTTP/SOAP
Service
Request / Response
• Any to Any Protocol
• Any to Any Payload
• XML
• non-XML
• Binary
• No WSDL Required
TUX
Service
Synch / Asynch
MQ
Service
Split / Join
EJB
Service
Publish / Subscribe
JCA
Service
•
Multiple communications paradigms
–
–
–
–
–
Request/response
Synchronous and asynchronous
One-to-many, many-to-one
Pub-sub
Mix-and-match (e.g. sync-to-async)
20. Adaptive
Messaging
Applications & Database Integration
Message Enrichment and Chaining
•
Adapter Certifications
– Packaged with OSB install
• AQ
• Database
• EBusiness Suite
– Packaged separately
• SAP
• PeopleSoft
• Siebel
• JD Edwards
21. Connectivity
• Web Service Transports
–
–
–
–
–
HTTP/SOAP
WS-Security
WS-Policy
WS-Addressing
WS-RM
Messaging
Services Transport Layer
Transport SDK
• Traditional Messaging
–
–
–
–
–
–
–
–
JMS
MQ
EJB/RMI
Tuxedo
FTP / SFTP
SMTP
File
Native Database Lookup
Service
Service
Service
Service
• Transport SDK
– Enterprise-specific custom transports
• Interoperability
–
NET, Tibco EMS, IBM MQ, IBM
WebSphere, Apache Axis, B2B
Interchange, iWay 5.5 adapters
.
Reliably connects services by
leveraging standards
22.
23.
24.
25.
26. OSB Solves Brittle Integration
• Costs
– OSB reduces complexity and increases visibility and re-use
• Time to Market
– OSB insulates business logic from “overhead”
• Scalability
– Proven to handle all dimensions of scalability
• Multi-channel Delivery
– Separates service functionality from presentation layers
• Risk
– Allows cached cloud service results to ensure high availability
and retain control
28
27. Value Proposition
Oracle Service Bus
Oracle Service Bus
delivers business agility, scalability, and
performance into the business infrastructure to
allow businesses to rapidly respond to new
business requests
Unlike traditional ESBs…
Oracle Service Bus provides predictable scalability
for reducing risk, automated service pooling for high
availability, and service virtualization for agility
delivered within a single solution for a lower total
cost of ownership
29
30. Oracle Service Bus
Feature Overview
Agile Architecture - Rapidly Respond to Change
Worklist
Process Portal
MS Office
Online Shopping
ORACLE SERVICE BUS
MAINFRAME
32
Mobile Devices
31. Service Virtualization
Feature Overview
Agility within OSB
Worklist
Proxy Services
• Enforces agility by
replacing direct
coupling with a
flexible virtual
endpoint to the
consumer
MS Office
Online
Shopping
Service
Consumer
Proxy
Services
ORACLE SERVICE BUS
Service
Endpoints
33
Portal
MAINFRAME
Mobile
Devices
32. Automated Service Pooling
Agility within OSB
Proxy Services
Worklist
Portal
MS Office
Online
Shopping
• Enforces agility by replacing
direct coupling with a flexible
virtual endpoint to the
consumer
ORACLE SERVICE BUS
Business Services
• Access service from multiple
endpoints
• Automated Service Pooling
ensures high availability when
apps go down and during
maintenance
34
X
MAINFRAME
Application
Instance 1
Application
Instance 2
Application
Instance 3
Mobile
Devices
33. Feature Overview
Business Challenge
Expanding Infrastructure into the Cloud
Increased Risk
Cloud Vendor A
• Less control with increasing
dependence on multiple cloud service
providers
Dependence on
cloud vendor
reliability
Performance Degradation
Higher latency with
Internet vs. LAN &
Firewalls
• Increasing cloud service usage results
in higher latency due to Internet vs.
LAN based communication
Unpredictable Scalability
Cloud Vendor B
ENTERPRISE SERVICE BUS
• Uncertain ability to handle spike in load
X
CRM
35
Business Apps
ERP
Sales
34. Service Result Cache
Feature Overview
Reliability, Performance and Predictable Scalability
Reduced Risk
Cloud Vendor A
Cloud Vendor B
• Service results available even when
application is down
Improved Performance
• Eliminate repeated application requests
for static data
Result accessed from
cache
Predictable Scalability
• Cached results maintained internally
resulting in less dependence on 3rd
party service provider availability
ORACLE SERVICE BUS
Result accessed from
cache
Failure
X
CRM
36
Business Apps
ERP
Sales
35. Service Result Cache
Feature Overview
Leveraging Coherence and Oracle Fusion Middleware
Checkbox
enabled
Cache Results?
Cache Token
Time To Live
37
36. Service Change Center
Rapid Service Enablement with OSB
• Change Center
• Allows for fine-grained tuning of
infrastructure
• No need to redeploy entire project
• Intuitive interface for nondeveloper/administrator
• View & resolve conflicts
• Undo, Re-do tasks
• Audit changes
38
Feature Overview
37. Leverage Existing Infrastructure
Rapid Service Enablement with OSB
• “Embrace & Extend” Strategy
– Reassure customer they don’t have to re-invent the wheel
– E.g. Retain existing services and existing ESB
– OSB will make all existing services (even tightly coupled
ones) and enforce loose coupling to introduce agility to
their existing architecture
• Ease of Use
– “Fit-to-Purpose” interfaces - Available in a Web-based
console and deeper-dive IDE
• Any-to-Any Protocol Support
–
39
Regardless of new business request, OSB is pre-configured to handle the format
38. Feature Overview
Market Leading ESB…
Complete - Single ESB…not three like IBM
Integrated - Seamless onramp to SOA and Governance
Open - Any-to-Any protocol support for open standards
Best of Breed - Forrester ESB Wave “Leader” 2009
Complete
Integrated
Open
Best of Breed
#
#1
1
40
39. Overview
– The goal: Give customers the ability to extend the set of standard
functions used in XQuery expressions and XQuery/XSLT resources
with their own implementations, written in Java.
– The rationale: Certain transformations are too complicated or too
inefficient to be done with XQuery/XSLT language. For example,
reuse utility complex transformation functions already existing in java
or even to do something with a database or some external system.
OSB XQuery
Expression / resource
BEA/Oracle
XQuery 1.0 2004 draft engine
XQ Standard functions
fn:concat
fn:abs
…
OSB built-in extensions
fn-bea:uuid
fn-bea:isUserInRole
…
Custom functions
ns0:myfunc
…
41
OSB XSLT
resource
XSLT Engine
(e.g. Apache Xalan)
40. Feature Highlights – Java Support
• OSB enhanced to support Java Objects
• In the Pipeline, Java Object is represented as
<ctx:java-content ref=”key1”
xmlns:ctx="http://www.bea.com/wli/sb/context”/>
Request
Pipeline
Application
Client
POJOs
Request
Pipeline
Transport Layer
$body
Register to Object
Repository
Key1={obj}
42
<ctx:javacontent
ref=“key1”/>
41. Feature Highlights – Java Support
•
Message Format in the Pipeline
–
–
–
–
The invocation point is the top element
Each argument is listed as a sub-element
Primitives and string arguments are inlined
POJO parameters referred by java-content ref.
<soap:Body>
<tes:some-method xmlns:tes=”default/someURI"
<arg0>99</arg0>
<arg1>true</arg1>
<arg2><con:java-content ref=”key1”
xmlns:con="http://www.bea.com/wli/sb/context”/></arg2>
<arg3><someXML .../></arg3>
</tes:some-method>
</soap:Body>
– XmlObject arguments can be inlined or passed as ref.
•
43
POJOs can only be modified in the pipeline through Java
Callout
42. Feature Highlights – JEJB Inbound
Client Application
Invocation Point =
“Method1”
Args= {Pojo1, …}
Method1
•
•
44
Stateless Session Bean
Method1(Pojo1,…)
Request Pipeline
Result
Method2(Pojo2,…)
Response Pipeline
Inbound EJB Transport exposes the Pipeline as a Stateless Session
Bean
– Communication between the client and proxy service is an EJB
invocation
– Client defines the SLSB interface exposed by the JEJB Proxy
service
– EJB artifacts are generated on the fly at the time of proxy
creation
Transaction and security context is propagated from the client into
the Bus
43. Feature Highlights – JEJB Outbound
• Business Service URI
points to the JNDI
Provider and JNDI name
of the Remote EJB
45
44. Feature Highlights – JEJB Outbound
• User Configurations:
–
–
–
–
–
Dispatch Policy
EJB Spec Version
Pass XMLBeans by value
Security Information
Client Jar
• Client Jar contains the
remote/home or business
interfaces to be accessed
by the Business Service
– User selects the EJB
Interface to be accessed
by the JEJB Business
service
46
45. Feature Highlights – JMS Transport JMS
Register the Object
with Object
Repository
•
•
47
$body
Request
Pipeline
<ctx:java-content
ref=”jcid" />
Object
Message JMS
JMS Business
Service
JMS
Queue
Object
Message
JMS Proxy
Oracle Service Bus
Busine
ss
Queue
Retrieve the Object
from Object
Repository
JMS Services configured with Messaging type ‘Java’ can
receive/send JMS Objects messages
Java Object Support for both JMS inbound and outbound
46. Overview - Message Flow
Transaction
Service
Clients
Application
Client
FTP
Oracle Service Bus
HTTP
HTTP/SOAP
JMS
Prox
y
Busine
ss
JMS
Enterprise
Services
Service
• Atomic Message Flow
– Simple as checking a box
– All transactional work in message flow committed or aborted
•E.g. Publish, Service Callouts (QOS EO), Reporting, Java Callout, Route
• Two settings for Proxy
– Transaction Required ?
– Same Transaction For Response ?
Benefits
Message flow can execute within TX regardless of the Inbound Protocol
48
48. Overview - Service Result Caching
Service
Provider
Process Flow /
Orchestration
50
Oracle Service Bus
Service
Consumer
•
Legacy
Problem
– External service is invoked every time for results
that may be reasonably static
• Eg. Product details, discount info
•
Solution
– Service Result Caching
•
Benefits
– Faster response times to clients/users
– Reduce load on potentially slow (legacy)
backend systems
– Cache data is always consistent and available
– Operational ease in managing cache capacity
49. Overview - Service Result Caching
If results not in cache, invoke
service & cache results
Oracle Service Bus
Service
Consumer
Service
Provider
Side Cache Pattern
Check cache
51
Coherence Data Grid
Primary
Node
Get / Put (Cachekey)
P
OSB
Result
Cache
Process Flow /
Orchestration
Legacy
Service Data
Backup
Node
B
53. Feature Highlights
Dashboard - Service Health
How often the external
service is invoked
How often the cache is hit
How often the cache is hit compa
to the external service
55
54. Should you require any further
information please do not hesitate to
contact us
• http://www.oraclecourseonline.com
• -oracle apps technical training
contact us:
• info@magnifictraining.com or +919052666559
• By Real Time Experts from Hyderabad,
• Bangalore
• ,India,USA,Canada,UK, Australia,South
• Africa.
Editor's Notes
The protocol contains specifications on how integrity and confidentiality can be enforced on Web Services messaging. The WSS protocol includes details on the use of SAML and Kerberos, and certificate formats such as X.509.
WS-Security describes how to attach signature and encryption headers to SOAP messages. In addition, it describes how to attach security tokens, including binary security tokens such as X.509 certificates and Kerberos tickets, to messages.
WS-Security incorporates security features in the header of a SOAP message, working in the application layer. Thus it ensures end-to-end security.
Transport level security is point to point, while Message level security can truly be end to end
WS-Policy is a specification that allows web services to use XML to advertise their policies (on security, Quality of Service, etc.) and for web service consumers to specify their policy requirements.
WS-Policy is now a W3C recommendation since September 2007
WS-Policy represents a set of specifications that describe the capabilities and constraints of the security (and other business) policies on intermediaries and end points (for example, required security tokens, supported encryption algorithms, and privacy rules) and how to associate policies with services and end points.
WS-Addressing is a specification of transport-neutral mechanisms that allow web services to communicate addressing information. It essentially consists of two parts: a structure for communicating a reference to a Web service endpoint, and a set of Message Addressing Properties which associate addressing information with a particular message.
WS-Addressing supports the use of asynchronous (from the point of view of the HTTP protocol) interactions by specifying a common SOAP header (wsa:ReplyTo) that contains the endpoint reference (EPR) to which the response is to be sent. The service provider (the thing doing the responding) transmits the response message over a separate connection to the wsa:ReplyTo endpoint
HTTP
HTTPS
JMS
Tuxedo
EJB/RMI
FTP
File
Email
Custom
WSDL
Untyped SOAP
XML w Schema
Untyped XML
Text
Binary
MFL
Attachments
Custom Java transport/RMI transport. Created custom XQuery functions to instantiate and destroy objects.
Objects are stored in thread local.
Key component of Oracle Applications and Middleware strategy for customers
Pre-integrated solutions & components
Share information across processes & applications
Critical for building custom applications with Oracle tools, middleware, and web application platform
Continue to build best-in-breed standalone ECM product
Leverage Fusion Middleware to enhance ECM
ECM consolidation + federation strategy & tools
Reducing overall ECM cost within an organization
MAIN POINT: SOA provides change insulation through a tiered, loosely coupled architecture to minimize disruption to processes and applications from changes to underlying infrastructure and vice-versa.
SCRIPT: SOA offers a standards based, technology neutral, non-invasive approach to application customization that overcomes the short-comings of conventional point to point integration approaches and proprietary technologies that we see highlighted here with numerous fragile connections and infrastructure brittleness.
The tiered service oriented architecture eliminates architectural chaos, promotes re-use and rapid composition of business processes for faster multi-channel delivery.
MAIN POINT: SOA provides change insulation through a tiered, loosely coupled architecture to minimize disruption to processes and applications from changes to underlying infrastructure and vice-versa.
SCRIPT: SOA offers a standards based, technology neutral, non-invasive approach to application customization that overcomes the short-comings of conventional point to point integration approaches and proprietary technologies that we see highlighted here with numerous fragile connections and infrastructure brittleness.
The tiered service oriented architecture eliminates architectural chaos, promotes re-use and rapid composition of business processes for faster multi-channel delivery.
MAIN POINT: SOA provides change insulation through a tiered, loosely coupled architecture to minimize disruption to processes and applications from changes to underlying infrastructure and vice-versa.
SCRIPT: SOA offers a standards based, technology neutral, non-invasive approach to application customization that overcomes the short-comings of conventional point to point integration approaches and proprietary technologies that we see highlighted here with numerous fragile connections and infrastructure brittleness.
The tiered service oriented architecture eliminates architectural chaos, promotes re-use and rapid composition of business processes for faster multi-channel delivery.
URI is non-responsive
Automatically removed from pool
Automatically returned when responsive
Alerts generated when endpoint status changes
MAIN POINT: SOA provides change insulation through a tiered, loosely coupled architecture to minimize disruption to processes and applications from changes to underlying infrastructure and vice-versa.
SCRIPT: SOA offers a standards based, technology neutral, non-invasive approach to application customization that overcomes the short-comings of conventional point to point integration approaches and proprietary technologies that we see highlighted here with numerous fragile connections and infrastructure brittleness.
The tiered service oriented architecture eliminates architectural chaos, promotes re-use and rapid composition of business processes for faster multi-channel delivery.
Overview – Give high level description of the new feature.
- What problem does it solve ?
- What is the benefit of this feature ?
Talking points if this does not fit nicely on slide. Use slide as backdrop for your discussion.
Slide only needs to include high-level bullet points since you are presenting all the content through your presentation.
(Shoot me an email if you want ideas about the benefits of particular feature)
Previous model:
Some transport endpoints can start transactions
Some transport endpoints can propagate transactions
Some do not support transactions all together
Today the transactional model in OSB message flow is completely dependent upon the transactional semantics of the inbound transport.
Service Result Caching allows us to cache the response from a Business Service.
This can dramatically improve performance if the response from the Business Service is relatively static.
This slide shows how it currently works - we always invoke the external service.
This slide shows how it works when Service Result Caching is enabled and configured.
The business service must be updated to “support” service result caching.
It is important to note that pipelines are not impacted if service result caching is enabled on the business service. This means you can enable service result caching on a business without having to update any pipelines.
This allows us to globally enable/disable service result caching for ALL business services.
This (along with the “supported” flag) turns on service result caching for a business service.
Hit Ratio can be used to:
- Determine the performance improvement from hitting the cache vs invoking the external service
- Fine-tune the caching strategy for best performance
- eg. Increasing or decreasing Cache TTL