An Oracle SOA Suite - Team Blog

The Difference Between Oracle and IBM Integration

Bruce Tierney
Director of Oracle Cloud Integration

Oracle and IBM are the only two Integration Platform vendors
in the Leadership quadrant of all three Gartner Schneider White PaperMagic Quadrants for
Application Infrastructure
related to service integration (SOA). You may wonder “what’s the difference between
Oracle and IBM integration offerings?” …they both provide application connectivity,
have an Enterprise Service Bus (ESB), Business Activity Monitoring (BAM), event
processing, process orchestration, business rules, management, governance and
more. There are however several key
differentiators between Oracle and IBM integration often referenced by industry
analysts and end users that strongly impact complexity and total cost of ownership.

What sparked the creation of this blog was a
customer case study on Schneider National, which transitioned from IBM Sterling
Gentran B2B, IBM InterChange Server, and IBM MQ Series to Oracle SOA Suite and
other Oracle Fusion Middleware. The case
study highlights:

one of the key differentiators of Oracle integration over IBM
integration…a unified approach to middleware to simplify integration and lower

Much has been written on the IBM
side of the unified discussion including cautions by industry analysts referring to the significant amount of ongoing professional services to support and
deploy the collection of often overlapping IBM components. One example of the overlapping components is
described on IBM’s website (page has since been removed but similar content is referenced on this site) which gives the 27 considerations to decipher
when deciding when to use which of the 3 IBM ESBs for each different
ESB-related scenario. For Oracle, there is one consideration...if you want application infrastructure agility, then the solution is all built into one Oracle Service Bus.

The complete Schneider National Customer Transformation story is
available for download. Here is a quick
summary of the background and key take-aways that highlight the unified
difference in Oracle’s approach to integration:

Prior to the Transformation

  • Complex applications and data environment at Schneider
  • Expensive and time-consuming to maintain and evolve
    application integration
  • Multiple order entry systems, multiple rating engines,
    several sources of customer information, no “single version of the truth”
  • Launched a 5-year business transformation program – “Quest”


  • Rationalize, simplify, and modernize enterprise IT applications
    and infrastructure
  • Create a modular, flexible, expandable and scalable IT
    architecture for long-term strategic growth
  • Core tenets: Common development environment, common runtime
    environment, and common management environment to standardize processes and


  • Consolidated to a single core set of unified tools,
    providing a consistent programming model for developers
  • Lower development and maintenance costs
  • Over 200 application integrations
  • Introduced re-usable enterprise web services such as TranportationOrder,
    Claims, Shipment, Account, AccountProfile, Location, Driver, Supplier and more.
  • Real time tuning of data flow using 40 business rules
  • Proven scalability to over 20 million messages per day
  • Oracle B2B for EDI, part of Oracle SOA Suite, with over 900
    trading partners and over 100 types of B2B documents

The end result for Schneider’s use of Oracle SOA Suite and
all the major components of Oracle Fusion Middleware is a simplified solution for
applications design, development, and maintenance, lower costs, improved
productivity providing scalability, performance, and reliability to “power it’s
growth in the next decade”

Schneider Stack Diagram

Image from the White Paper showing Schneider National's Application Infrastructure

Download the Schneider National Case Study

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.