Transitioning from TIBCO to Oracle SOA - Part 1
By Bruce Tierney-Oracle on Jul 24, 2013
At the last Oracle OpenWorld, EA (Electronic Arts) presented "Winning at Digital: Build the World's Best Digital Playground, with fun for EVERYONE, ANYTIME, ANYWHERE." To achieve their required level of scalability for over 220 million registered users, EA transitioned from TIBCO middleware into an Oracle Fusion Middleware platform based on Oracle SOA Suite 11g. As shown in the left-to-right project timeline below, their transition successfully went live on May 21 2012 in 30 countries and 14 languages across North America, Europe, and Asia:
The previous implementation (shown in the middle) used a combination of file uploads, SQL scripts, TIBCO and according to EA resulted in a platform that was not scalable to meet their future requirements.
The current Oracle Fusion Middleware implementation (indicated on the right side of the image above) now handles the following transaction volumes, business process, formats and message sizes:
Prior to their transition from a collection of disparate platforms and tools, regions of EA would sometimes independently update or change applications without synchronizing with other geographies which seriously impacted the enterprise. The standardization on Oracle SOA Suite addressed this issue and also met their current and future scalability requirements.
In the Profit Magazine cover story, EA describes their transition to a "Future-Proof" solution to support their 30% growth in digital revenue, led by direct-to-consumer channels. The article describes how "in the spring of 2011, EA management engaged Oracle staff to design and build the iHub, EA’s data integration solution, based on Oracle Fusion Middleware. The joint team reviewed the mission, desired outcomes, and target key performance indicators (KPIs) of the project. Then they reverse-engineered those outcomes to come up with a project plan. Meanwhile, millions of transactions kept rolling in daily, so there was urgency behind the initiative."
“Generally, when you’re on a project, it takes three months to build a team, set everything up, and start delivering these integration services,” Deepak Advani, VP of enterprise services says. “We basically took two weeks to set the project up, and we were delivering in four weeks. We were adjusting and building as we went.”
This blog focusing on Oracle SOA Suite scalability is a first in a series of upcoming blogs on "Transitioning to Oracle SOA Suite". Stay tuned for more updates on how and why customers are migrating to Oracle SOA Suite.
To assess your scalability and other aspects of your integration platform, take the SOA Assessment by Oracle or for some cool gaming pictures, click on the image below: