• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Enterprise Service Bus Differentiators
 

Enterprise Service Bus Differentiators

on

  • 3,675 views

Oracle Service Bus 11g vs. IBM

Oracle Service Bus 11g vs. IBM

Statistics

Views

Total Views
3,675
Views on SlideShare
3,675
Embed Views
0

Actions

Likes
6
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi, These slides are very informative and I need badly to download these slides. How can i?
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Note: DB2 is provided under a restricted enterprise use clause. Please refer to the product documentation for more details.
  • Reference1 Oracle Technical Support Policies page 22 Oracle Technical Support Policies page 33 Oracle Technical Support Polices page 2 (11 August 2009)
  • Consider the implications and liabilities for a $1 vs. $1,000,000 transferThe implementation of the transaction can be done as a set of SQL statements in a stored procedure, JDBC code in Java, EJB code, BPEL flow, MS .NET, JMS, Web Services, etc. Implementations details do not matter a long as ACID properties of the transaction are maintained even during the events of hardware or power failures of all of the systems involved.There are patterns that allow to break one large transaction into many asynchronous steps, but eventually there must be a mechanism to ensure the reliable delivery and avoid duplication of messages in a long running asynchronous system.

Enterprise Service Bus Differentiators Enterprise Service Bus Differentiators Presentation Transcript

  • Enterprise Service Bus DifferentiatorsOracle Service Bus 11g vs. IBM
    Richard Naszcyniec
    Executive Architect
  • Initial Points To Consider
    Agenda Item
    2
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Common WebSphere Portfolio Competitive Strengths
    WebSphere products can be purchased individually when you need them
    Why buy any product before you need it or have the skills to apply it?
    Compare to Oracle Suite purchases.
    Each WebSphere product is purchased and licensed separately, so you can install each product on separate servers at no extra cost.
    You can also mix combinations of WebSphere products on the same server if you want.
    IBM provides superior SOA & BPM depth and breadth than what Oracle offers
    SOA appliances such as DataPower, Workload Deployer, and CastIron are unique IBM offerings
    IBM can match Oracles functionality while the opposite is not true
    IBM supports clients who want to use virtualization technologies such as VMWare and PowerVM
    Sub-capacity licenses are available providing significant cost savings for virtualization environments.
    IBM fully supports products running on VMWare (and others) while Oracle does not.
    IBM includes all pre-requisite software with purchase
    For example, the WebSphere Enterprise Service Bus include the WebSphere Application Server to run on.
    3
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • More Reasons To Buy WebSphere
    Market Leadership
    Gartner in 2010 ranks IBM with nearly twice the middleware market share of Oracle
    IBM is chosen more than twice as often as Oracle by companies looking to acquire BPM technology for the past seven years
    Gartner puts IBM middleware above Oracle on most “quadrants”
    Do more with less and promote green computing
    Strong support for virtualization including products written specifically for those environments.
    SOA appliances
    Ability to dynamically alter the infrastructure and giving more resources to applications when they need it and then releasing resources when they are no longer needed.
    Ability to manage (and track) dynamic infrastructures using SLA’s
    Well integrated SOA tools that increase productivity
    Use productivity to handle more project scope or reduce costs
    Planning and design based on currently available WebSphere tools reduces uncertainty and thus risk
    Support for System z
    Intellectual Investment
    IBM is has been the U.S patent leader for the past 18 years
    IBM received
    5,896 U.S. patents in 2010
    4,914 U.S. patents in 2009
    4,186 U.S. patents in 2008,
    IBM became the first company to be granted as many as 5,000 U.S. patents in a single year.
    IBM’s 2010 patent total nearly quadrupled Hewlett-Packard’s and exceeded the combined issuances of Microsoft, Hewlett-Packard, Oracle, EMC, and Google.
    4
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Enterprise Service Bus CompetitionPrimary Competitive Points To Consider
    IBM provides choice of the ESB to meet your needs. Oracle offers a one size must fit all needs ESB.
    IBM DataPower offers capabilities and security Oracle is unable to match
    Licensing for IBM’s ESB offerings includes everything you need to get installed and running. Oracle always has at least one pre-requisite license requirement. (sometimes more)
    IBM development tools provide everything you need to develop, test, and debug locally
    IBM development tools provide a simpler and more productive environment
    Interaction with governance infrastructure is important both at design and run time. Oracle run time governance is highly fragmented and inconsistent.
    Reliable messaging is important many ESB mediations. MQ is a product offering a range of reliable messaging options that Oracle can’t match.
    5
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Enterprise Service Bus CompetitionAre You Aware Of These Oracle Service Bus Weaknesses?
    Oracle Enterprise Service Bus 10g implementations can’t be upgraded to Oracle Service Bus 11. What will happen with OS B 11g/c?
    Dynamic endpoints are limited to UDDI lookups, static text file list lookups, manipulation of context variables
    Oracle lacks any native or adapter capability for socket level communication.
    Developers must use a separate tool (Format Builder) to configure maps for non-XML data that will be transformed using XQuery
    Developers tasks can be laborious with IDE features like cut/paste and remediation
    Oracle does not support the SCA programming model as they do in their SOA Suite
    Oracle does not have a way to decouple data modeling from implementation
    Oracle does not offer the fine grain transaction control that IBM provides.
    Using JCA adapters requires multiple steps using multiple tools
    Impossible to embed Java in mediations without deploying JAR files (added administration)
    Oracle lags IBM capabilities in out of the box capabilities to recover from systems that are unexpectedly offline
    6
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Additional Oracle red flags we hear about
    Oracle Support
    Clients may not run any Oracle software without a support contract
    Clients may not support a subset of licenses within a “license set” and all licenses must be at the same support level1
    In the event that a subset of licenses on a single order is terminated or if the level of support is reduced, support for the remaining licenses on that license order may be priced at Oracle's list price for support in effect at the time of termination or reduction minus the applicable standard discount2
    Additionally, customers have to terminate use of the software that was part of license set even if paid for in full. Cannot be run unsupported.3
    Fusion Middleware
    Fusion middleware 11g has limited production references.
    Oracle BPM 11g has even fewer production references
    Oracle Fusion middleware and BPM 10g production references are not valid given the dramatic technology differences in the 11g version.
    Fusion middleware 11g is not support by Oracle applications
    Very few Oracle Application Integration Architecture (AIA) Process Integration Packs (PIPs) support Fusion middleware 11g
    Transaction control in Oracle middleware products is limited and should be well exercised by potential clients prior to use
    7
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Oracle Service Bus Fundamentals
    Agenda Item
    8
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle Service Bus (OSB)
    Oracle Service Bus is the only ESB that Oracle currently sells
    Oracle Enterprise Gateway is not an ESB. It is a way to secure SOA deployments. (Vordel OEM)
    Oracle Mediator which is part of SOA Suite (and runs old Oracle Service Bus mediations) is not considered a public ESB
    Old Oracle ESB 10g is no longer sold and existing deployments may only be automatically migrated to the Oracle Mediator in the SOA Suite.
    The current version as of July 2011 is 11.1.1.5
    Third 11g release based on the former BEA Aqualogic Service Bus (ALSB)
    OSB does not include the WebLogic server required to run the product
    Separate licensing of WebLogic Suite is required
    9
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • What Do Oracle Clients Need To License To Run OSB?
    Oracle WebLogic Suite
    WebLogic Server required to run the Oracle Service Bus
    Coherence to optionally cache data that changes infrequently (limited use cases)
    Supported Database
    When you want to use reporting and/or Web Services Manager
    SOA Suite
    If you want to use the Web Services Manager for Security Policies
    10
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • When Do Clients Need To License Oracle Service Bus?
    Anywhere it is installed!
    Development, Production, Testing, Disaster Recovery, Warm Standby, Cold Standby, etc…
    Development Cost Notes
    Oracle developers must perform their work against a full OSB installation accessed via browser and eclipse plug-in
    Oracle offers pricing based on named user as well tradition “per core”.
    Named user license is prices at $365 per license including pre-requisite software and 1st year S&S.
    Named user pricing is very common for pricing out development shop
    11
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Choice
    WebSphere Competitive Advantage
    12
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle Service Bus competes here
    Because one size does not fit all for an ESB
    DataPower
    • specialized
    • ultra fast for specific functions
    • ultra secure
    all three interoperate and exploit a common federating infrastructure
    • Common management tool
    • Common Registry
    • Common Identity Management
    • Common transformation tool
    WebSphere ESB
    • standards based (if you got “rails”, we will get you there)
    • simple to operate (uses widely adopted WAS runtime)
    WebSphere Message Broker
    • can get “anything” “anywhere”
    • widely adopted and hugely popular
    SEP 2011
    13
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • WebSphere DataPower
    Hardened, specialized product for helping integrate, secure & accelerate SOA
    Many functions integrated into a single device
    Higher performance with hardware acceleration
    Simplified deployment and ongoing management
    Multiple deployment patterns
    B2B Gateway, Secure Gateway (Web Services, Web Applications), Low Latency Gateway, ESB, SOA Governance, Internal Security, Legacy Integration, XML Acceleration
    DataPower Appliance Value
    Reduce Time-to-market through Simplification
    Improve IT agility through Service Enrichment
    Protect corporate assets through improved Security
    Improve Quality of Service through Service Governance
    Lower Operational Costs with Speed and Scalability
    14
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • SIX DataPower Appliances For Different Needs
    15
    WebSphere DataPower Integration Appliance XI50, XI52, XI50B (blade), XI50 for zEnterprise
    IBM’s hardware ESB, the XI50 line devices are purpose-built for simplified deployment and hardened security, bridging multiple protocols and performing conversions at wire speed.
    WebSphere DataPower XML Security Gateway XS40
    Designed by some of the world’s top XML and Web services security experts, the XS40 delivers a comprehensive set of configurable security and policy enforcement functions.
    WebSphere DataPower B2B Appliance XB60
    The XB60 extends your ESB with purpose-built B2B hardware providing AS1/AS2/AS3 messaging and trading partner profile management in a high-performance DMZ-ready appliance.
    WebSphere DataPower XML Accelerator XA35
    Capable of offloading overtaxed Web and application servers by processing XML, XSD, XPath and XSLT at wire speed, the XA35 enables faster results from application investments.
    WebSphere DataPower Low Latency Appliance XM70
    The XM70 delivers predictive, low latency messaging and routing for data distribution in a purpose-built, hardware appliance.
    WebSphere DataPower XC10 Appliance
    Delivers exceptional performance and hardened security at the caching tier of your enterprise application infrastructure.
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Cast Iron
    Complete, flexible solution platform
    Integration effort measured in days!
    100’s of preconfigured integration templates
    Oracle: E-Business Suite, Siebel, CRM OnDemand, PeopleSoft, JDE, and others!
    Many others like SAP, Salesforce.com, NETSUITE
    Cloud/SaaS, Appliance, VM Image deployment options
    Flexible terms and purchase pricing including low monthly subscription
    Up to 80% lower maintenance costs vs. software-based alternatives
    Agnostic: based on open standards
    Does not tie you to any proprietary standards
    16
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Cast Iron High Level Oracle Connectivity
    17
    Complete application integrations using a “configuration, not coding” approach that frees up expert programmers.
    Integrate their applications in days and for 80% less than the cost of other alternatives.
    Template Integration Processes (TIPs) – Thousands of pre-built integration scenarios to choose from and avoid building integrations from scratch.
    TIPS are supported and certified as well!
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Cast Iron – Oracle ERP Specifics
    18
    Integration Problems Solved
    Systems Connected
    Data migration from legacy to new applications
    360º view of customer and product across ERP, CRM and call center applications
    •Opportunity to Order integration between marketing automation, CRM and ERP systems
    Order to Cash integration between CRM, ERP, warehousing and financial systems
    Billings, Bookings and Backlog visibility from ERP to CRM
    Pricing and product catalog information between ERP and customer portals
    POs, shipping notices and payments with suppliers
    Customer support integration between ERP and customer support systems
    Repair and warranty information between call centers and customer portals
    Data extraction from ERP/CRM to reporting and BI systems
    Mergers, acquisitions & divestitures integration
    Enabling Service Oriented Architectures
    ERP including SAP, Oracle, JD Edwards, PeopleSoft, BAAN, QAD, Lawson, Great Plains, etc.
    CRM including Siebel, Clarify, Remedy, Oracle, Kana, Vantive, etc.
    All major SaaS applications including salesforce.com, RightNow, NetSuite, Oracle CRM On Demand, etc.
    All major databases including Oracle, DB2, SQL Server, mySQL, Sybase, Informix, etc.
    Flat-!les using FTP, HTTP(S), e-mail
    XML and Web Services
    EDI
    Middleware and all major EAI platforms
    Project management applications including Clarity
    And many more…
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Extended ESB offerings from IBM WebSphereAn ESB without limits to enable complete SOA and BPM solutions
    Service Orchestrationand BPM
    Service Registry
    Service Monitoring
    WebSphere Process Server
    WebSphere Services Registry and Repository
    Publish
    Govern
    Manage
    Enrich
    Find
    Tivoli CAM for SOA
    Universal Transformation
    MQI
    Java JMS
    XMS for .NET C#
    XMS for C/C++
    WebSphere Transformation Extender
    Service Enablement
    Enterprise Messaging Backbone
    WebSphere MQ messaging backbone
    WebSphere Adapters
    WebSphere MQ
    Event Processing
    WebSphere Business Events
    SEP 2011
    19
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Govern
    Publish
    Find
    Publish
    Govern
    Manage
    Enrich
    Find
    Manage
    Enrich
    WebSphere Service Registry and Repository provides value throughout the SOA lifecycle
    WebSphere Service Registry and Repository
    Encourage Reuse
    Find and reuse services for building blocks for new composite applications.
    Enhance Connectivity
    Enable dynamic and efficient interactions between services at runtime.
    Enable Governance
    Govern services throughout the service lifecycle
    Help optimizeservice performance
    Enable enforcement of policies. Impact analysis
    SEP 2011
    20
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • 21
    Messaging Technologies are evolving rapidlyCustomer demand increasing, closely aligned with Smarter Planet
    IBM UNIVERSAL MESSAGING
    Business
    Transactions
    Sense and Respond
    MQ
    MQ Telemetry
    Leveraging System z
    Web applications
    MQ for z/OS
    MQ HTTP Bridge
    Managed File Transfer
    Real-time Awareness
    MQ File Transfer Edition
    MQ Low Latency Messaging
    Extra Data Protection
    Cloud Platform-as-a-Service
    MQ Advanced Message Security
    MQ Hypervisor Edition
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Developer Environment Simplicity
    Competitive Advantage
    22
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Single Development Environment
    All WESB development, testing, and debugging can be done in IBM Integration Designer
    All WMB development, testing, and debugging, can be done using Message Broker Toolkit
    Oracle Service Bus development is split over multiple tools
    Web Browser – used for development, testing, debugging, deployment, administration
    Eclipse Plug-in
    alternate mediation design environment that must be used with browser
    Must be used for XQueryMapper work
    Format Builder Tool – used for non-XML data formats (description and transformation to/from XML)
    JDeveloper
    Commonly used to author artifacts used by OSB such as WSDL, XSD’s, XSLT, and others
    Used to obtain WSDL used by SOA Suite Transport (SOA-DIRECT)
    Used to obtain WSDL & JCA file for JCA transport
    • Oracle JCA adapters certified with OSB: Oracle Adapter for Oracle Applications, Oracle JCA Adapter for AQ, Oracle JCA Adapter for Database, Oracle JCA Adapter for Files/FTP, Oracle BAM Adapter (Business Activity Monitoring), PeopleSoft (Oracle Application Adapters 10g), SAP R/3 (Oracle Application Adapters 10g), Siebel (Oracle Application Adapters 10g), J.D. Edwards (Oracle Application Adapters 10g)
    23
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Integrated Development Environment (IDE) Competitive Checklist
    24
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle Service Bus IDE Installation Complexity
    25
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Mediation Simplicity – Hello World Example
    26
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
    Which mediation looks easier at first glance?
    Oracle Service Bus IDE
    IBM Integration Designer
  • Integration Designer - Artifact evolution and refactoring
    SEP 2011
    27
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Using JCA adapters with OSB is not straight forward
    Oracle leverages JCA for multiple adapters
    To use a JCA adapter in OSB there is a multi-step process
    In Oracle JDeveloper, create a JCA file, its associated abstract WSDL, and any other required resources, such as a TopLink mapping file.
    Import the JCA resource files into an Oracle Service Bus project so that all references to dependencies are maintained.
    In Eclipse, right-click the outbound JCA file and choose Oracle Service Bus > Generate Service.
    In the JCA Generate Business Service window, select the folder location for the new service, and, if desired, change the default service name.
    Click OK. Oracle Service Bus generates the business service and the concrete WSDL that is used by the business service.
    28
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Programming Model
    Competitive Advantage
    29
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • SOA programming model in WESB
    Composition
    Mediation Flow
    proprietary, visual, not an API
    Data
    Business Objects (SDO)standard, visual + API
    Invocation
    Service Component Architecture (SCA)standard, visual + API
    SEP 2011
    30
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Programming model in OSB
    Composition
    Visual Proxy service
    proprietary, not an API
    Oracle is going to rewrite its product to support SCA at some point
    Data
    XQuery standard
    MFL proprietary
    Invocation
    Business Service
    proprietary, not an API
    SEP 2011
    31
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • SCA: Why do you care?
    Best of both worlds: (1) Visual drag & drop, (2) API for programmers
    Oracle only offers visual approach, but not the API
    Ability to decouple programming model from the implementation
    For OSB everything looks like a Web service and there is no way to call it programmatically (since there are no APIs available)
    Ability to add QoS qualifiers to WSDL without proprietary vendor lock-in
    Investment protection
    With Oracle you will have to migrate your applications when they start supporting SCA
    Ability to leverage 3rd party SCA components (in the future)
    Just like Eclipse offers choice of plug-ins, SCA will offer choice of components
    SEP 2011
    32
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Data Object And Interface Definition
    Competitive Advantage
    33
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Data Object And Interface Definition
    The data that flows between consumers and subscribers often must be modeled and implemented by developers
    The interfaces for services exposed to consumers by the ESB must be modeled and implemented by developers
    Questions To Ask
    How are data objects and interfaces designed and implemented in IBM and Oracle products?
    Is one vendors approach easier than the other?
    How do I manage the artifacts that are created in this process?
    Does the implementation of the provider or consumer of data have an impact on my data model(s)?
    Can the artifacts I create be used by other components of my SOA and BPM stack?
    34
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle’s Approach
    Manual creation of XML Schema Documents (XSD)
    Manual process for describing non-XML data
    Manual creation of WSDL documents which may included embedded schemas
    35
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • IBM Approach - Common
    Define data in a way that is independent of physical implementation promoting loose coupling
    Allow data defined to be used as needed via standards like WSDL and XSD
    Work with data at run time in a common fashion regardless of how it is received or will be transmitted
    Provide tools that allow for remediation of data
    Strong support for interaction with governance at design time
    36
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Business Objects: Why do you care?
    Easier modeling of business data with inheritance and nesting
    Intuitive Business Object editor vs. Oracle’s more complicated XSD
    With Oracle one has to be XSD and XML expert to do even medium complexity objects
    Ability to decouple programming model from the data representation
    Developer only has to know one way of dealing with data
    Business graphs provide additional capabilities
    Can carry Change Summary and Event Summary information related to the business object in the business graph and make it available in the runtime to provide supporting metadata to adapters connecting to backend systems
    Oracle does not have this capability
    Investment protection
    With Oracle you will have to migrate your applications when they start supporting SDO
    SEP 2011
    37
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • IBM Approach – WebSphere Enterprise Service Bus
    Model data as business objects which are then stored as XSD
    Similar to entity modeling for databases
    Model interfaces via a tailored user interface that can then be used to generate various artifacts like a WSDL document
    Support for flat and hierarchical business objects
    Support for data that enhances data objects
    Carrying change summary and event summary information related to the business objects in the business graph. A business graph is a direct corollary of the SDO DataGraph concept, except that it provides more than just the single change summary header.
    Metadata that can be added to business object definitions to enhance their value in the runtime
    Business object services (APIs) are a set of capabilities provided on top of the basic capabilities provided by Service Data Objects. Examples are services such as create, copy, equality, and serialization.
    38
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • WebSphere Message Broker – A Framework For Messages
    39
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
    • Support for importing data definitions from a variety of sources
    • XML DTD, XML Schema, WSDL files, C structures, COBOL structures, or EIS systems
    • Importing can create and populate message definition files.
    • Alternatively, you can create an empty message definition file and create your messages using just the editor.
    • When your message definition files are complete, you can then generate the message set in a form that can be used by a broker, parser, or application. This might be in one of the following forms:
    • A message dictionary for deployment to a broker
    • An XML Schema for use by an application to validate XML messages, or for deployment to a broker
    • Web Services Description Language (WSDL) for a Web services client, or for deployment to a broker
    • Documentation to give to programmers or business analysts
  • Dynamic Endpoints
    Competitive Advantage
    40
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Dynamic Endpoints
    Allows developers to dynamically determine what services at what locations and under what conditions should be used at runtime
    Increases flexibility in mediations and promotes a loosely coupled architecture
    Oracle supports simple UDDI lookups, lookups of static XML files, and programmatic setting of endpoints
    IBM offers runtime integration with WSRR in addition to UDDI to maximize choice and increase flexibility with prebuilt mediation primitives. Programmatic setting of endpoints is also supported
    Usage Examples
    You need to use different endpoint addresses for development, testing, and production
    You want to route messages from consumers to different endpoints based on service level agreements
    You need to use a particular endpoint address assigned to you only after logging in to a known address (Salesforce.com)
    41
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Dynamic Endpoints Competitive Checklist
    42
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • WESB – Dynamic Endpoints Mediation Primitives
    43
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • WMB – Dynamic Endpoints Mediation Primitives
    44
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Impact Of Governance
    Agenda Item
    45
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Governance in an ESB context
    Governance applies to the design and run time control of services
    Design time governance applies to designing, implementing, and managing services that are exposed to consumers
    Run time governance applies to resolving endpoints dynamically, securing access to endpoints, and applying policies to endpoints
    Both IBM and Oracle ESB’s required additional product to provide these capabilities.
    Oracle: Service Registry, Oracle Enterprise Manager Fusion Middleware Control (OWSM), Enterprise Registry
    IBM: WSRR, RAM
    46
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle Governance Challenges
    Developers must use either Oracle Web Services Manager policies or WLS 9.2 policies, but not both for a given service
    In future releases of Oracle Service Bus, Oracle Web Services Manager policies will replace and enhance the functionality of WLS 9.2 security policies. WLS 9.2 security policies will be deprecated.
    Oracle Web Services Manager policies add costs since they are only available as part of the SOA Suite bundle
    Oracle Web Services Manager policies are part of the Enterprise Manager Fusion Middleware Control which can only be purchased as part of the SOA Suite.
    You can attach Oracle Web Services Manager policies only at the service level, and you cannot embed them in service WSDLs.
    Oracle policy scope is limited to: Reliable Messaging, Management, WS-Addressing, Security, and MTOM
    47
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Oracle Policy Capabilities
    FIXED set of capabilities
    Web Services Standard
    WS-Security 1.0 or WS-Security 1.1
    Authentication Token
    HTTP, Kerberos, SAML, Username and password, X.509
    Transport Security
    SSL, no-SSL
    Policy Type
    Service, Client
    48
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • WMB Design Patterns
    Competitive Advantage
    49
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • 50
    Patterns for Simplified Development
    WSDL
    MQ
    File
    From:
    To:
    • Creates top-down, parameterized connectivity solutions
    • Web Service façades, message oriented processing, queue-to-file
    • Reduces common problems in flow development
    • Communicates best practices to the Broker community
    • Complements existing bottom-up construction for bespoke connectivity
    • Reduces time-to-value for solution development
    • Patterns are a first class citizen in Message Broker
    • Patterns have bubbled right to the top in the navigator view!
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Message Broker Navigator
    51
    • User is directed towards a new entry point for development
    • First class development mechanism
    • Augments other starting points:
    • WSDL, SCA, Adapter
    • Does not replace the existing bottom up development approach
    • Still completely valid to start from flows, message sets etc!
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Patterns Explorer
    52
    • Patterns Explorer contains built-in and user-defined patterns
    • Pattern categories
    • Groups similar solutions together
    • Message-based integration, service enablement, service virtualization…
    • Extensive help is available through a pattern specification
    • Provides selection and implementation guidance for the patterns
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Pattern Parameters
    53
    • Customize a pattern using pattern parameters
    • Instance name identifies pattern; duplicate names will optionally be overwritten
    • Parameters are logically grouped into sections
    • Mandatory parameters are indicated via *, missing parameters are indicated via x
    • Fields are watermarked and pre-populated, for example: available message sets
    • Detailed help is available for each pattern parameter
    • Click the Generate button to create the generated artefacts: message flows, scripts…
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Generation
    54
    • A working set is created, it includes only the current pattern instance
    • The Projects view contains the generated projects
    • The Patterns Instances view contains the pattern instance projects
    • Includes the configuration XML and summary page
    • Patterns does not attempt to provide life cycle management!
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • You can design your own patterns as well
    55
    SEP 2011
    55
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Transactions
    Competitive Advantage
    56
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Remote cloud (future)
    Why Transactions?The saga of a one million dollars
    Failure
    Account 1 balance = $1M
    Account 1 balance = $1M
    Failure
    Credit Card System
    Failure
    Failure
    Failure
    Account 1 balance = $1M
    Account 1 balance = $1M
    Audit Log
    Account 1 balance = $1M
    Internet Banking System
    Failure
    Failure
    Failure
    Types of failures:
    Power outage
    Network error or outage
    Software failure (OS, DBMS, etc.)
    Hardware failure
    Human error
    Application error
    DoS or other attack
    Combination of any of the above
    Transaction: Transfer $1M
    Check funds availability in Account1
    Withdraw funds from the Account1
    Debit funds to the Account2
    Update related systems with the right information
    Write into the audit log for security and compliance reasons
    Failure
    Failure
    Failure
    Failure
    Failure
    Account 1 balance = $1M
    Account 2
    balance = $0
    Initial state:
    Account 1 balance = $0M
    Account 2
    balance = $0M
    Possible outcome 1:
    Account 1 balance = $1M
    Account 2
    balance = $1M
    Possible outcome 2:
    Account 1 balance = $0M
    Account 2
    balance = $1M
    Desired outcome 3:
    SEP 2011
    57
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Oracle Service Bus Transactional Deficiencies
    Internal testing shows Oracle failing tests that IBM ESB’s passed. We encourage you to include transactions in your evaluation testing and any POCs
    Lack of visual cues aiding developer understanding of transaction scope
    Must know where to find transaction properties
    Even modest 5% development productivity increase may yield savings of $40,000 per year for a team of 10 developers
    Transaction control for mediations is tied to the programming model. You may only start new or indicate participation in an existing global transaction in Proxy Services.
    OSB does not allow for transaction management of individual steps in the flow
    No support for uncoordinated auxiliary transactions
    Are there cases when you need sub-transactions?
    Oracle Service Bus does not support XA transactions for the MQ transport. If XA is required you must use the JMS transport with WebSphere MQ JMS interface.
    There are nuances to Oracle’s transaction support that change by adapter
    Oracle MQ transport supports local transactions but not remote transactions
    Lack of z/OS support can limit globally coordinate transactions
    58
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • WESB Transactions
    Visual cues in mediation designer make understanding transaction boundaries easy
    Support for local and global transactions
    Developers can also configure mediations to decide at run time whether to join a global transaction or to establish a local transaction environment.
    Can participate in client initiated transactions
    Any part of a mediation can be a single transaction
    WebSphere Adapters are transaction capable, including CICS adapter
    59
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Transaction boundaries between services, processes and mediations are shown in green color on assembly diagram
    Right-click, select “Show Transaction Highlighting”
    Change transaction properties in a single consolidated view
    SEP 2011
    60
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • WMB Transactions
    Can participate in client initiated transactions.
    Every piece of data processed by a message flow has an associated transaction.
    A message flow transaction is started when input data is received at an input node in the flow; it is committed when the flow has finished with that message, or rolled back if an error occurs.
    If an external system, such as a database, supports that concept of commit and rollback, and it can take part in a broker transaction, you can configure the node so that the work it does is included in the flow transaction.
    Depending on the node, you can specify if the work done in an external system that supports transactions is committed immediately, or when the message flow transaction completes.
    Transaction Types
    broker-coordinated transactions or partially coordinated transactions
    On distributed systems, message flow transactions are managed by the broker, by default. These transactions are known as
    globally coordinated transactions
    Coordination is provided by an external transaction manager which uses XA protocols to interact with resource managers. The transaction manager is called by the input node when the message flow has concluded (successfully or with errors). The transaction manager, rather than the input node and the broker, interacts with the relevant resource managers to initiate the correct actions for each resource.
    On z/OS®, transactions are always globally coordinated
    On distributed systems, transactions can be coordinated by WebSphere MQ
    Support for uncoordinated auxiliary transactions
    61
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    SEP 2011
  • Failed event management
    Competitive Advantage
    SEP 2011
    62
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • What if the back-end service is temporarily not available?
    Real world example
    It may take a week to handle loan application. After all initial reviews and credit verification the next step in the flow is to submit the application to the actual loan origination system. The system is only available via Web Service or JCA interfaces and there is no messaging. However the system has been unexpectedly shutdown because of the earthquake. Hundreds of good loan applications are about to be rejected because service calls failed and retry logic ran out. If architecture of the system was built around reliable messaging this would not be a problem, but developers chose to use SOAP/HTTP (or other non-reliable protocol)
    How WebSphere does it
    WebSphere Process Server and WebSphere ESB provide failed event management facility and automatic message store-and-forward for this and other kinds of unexpected situations. Administrative tooling is provided to browse and edit message content and perform group operations on such failed events, eliminating the need to reject perfectly good loan applications and not lose revenue
    What about competitors?
    With most competitive offerings loan applications will be lost, unless the system was built using JMS (assuming their JMS implementation could handle outages correctly)
    Implications for the business if using competitive products
    Lost business cost: Additional level of reliability in message delivery could help to avoid lost business and revenue even when JMS was not part of the design
    SEP 2011
    63
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Development time configuration step
    During development phase of the project it is possible to configure automatic “Store and forward” properties for services over multiple different protocols
    Oracle can only do this for JMS based services. Other protocols limited to retry count/interval
    SEP 2011
    64
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Runtime GUI for browsing, editing and resubmitting failed events
    WebSphere ESB and Process Server runtime provide browser based GUI to search, browse and resubmit failed events individually or as a group (with filtering)
    If certain backend system was not available for some time, then all requests can be resubmitted at once and this is transparent to the client
    Services do not need to be JMS based to participate in this service
    SEP 2011
    65
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Failed event management
    Administrator can edit business data in the event
    Example: Customer name, address, amount of order, etc.
    Event can be deleted or resubmitted to the service it was originally intended for
    SEP 2011
    66
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Questions?
    67
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
  • Thank You! ibm.com/smartersystems
    SEP 2011
    Comparing Oracle Service Bus To IBM ESB's ** IBM NonDiscolsure Agreement Protected Material **
    68