Document Sample
Leave+Leverage Powered By Docstoc


EAI: Rip and Replace or Leave and Leverage?
Migrating to a Service-Oriented Architecture (SOA)
IONA Technologies May 2007

EAI: Rip and Replace or Leave and Leverage?


Executive Summary
Enterprise Application Integration (EAI) was the industry’s first attempt to consolidate the disparate middleware solutions with a single product suite. EAI suites now present problems because they were created long before Web services standards were invented, and at a time when the demands on integration technology were significantly less than it is today. When looking at ways to meet growing demands, IT executives find themselves torn between the benefits of a service-oriented architecture (SOA) and managing legacy integration technology. Architects immediately consider two choices: 1. Stay with EAI – Continue on the current path. A deployed system is proven and usually paid for, but the costs to integrate new systems or modify existing applications are astronomical and increase over time. Rip and Replace – Remove all EAI components and replace with SOA technology. The result is infrastructure that meets all modern requirements, but the disruption to operations and the upfront costs can be daunting.


But there is a third choice. The infrastructure in place provides much of the functionality required of a SOA including transportation, transformation, security, management and more. Rather than discard technology that is deployed, reliable and proven, it is more cost effective to leverage the services as part of a SOA migration strategy. After examining existing assets, most IT organizations find that they are almost already there. This creates a third option: 3. Leave and Leverage – Leave existing assets in place and use them as part of a SOA. This eliminates the disruption and upfront costs, yet allows organizations to move forward and benefit from the efficiency and agility of a SOA.

IONA has a proven track record of establishing SOAs within large IT organizations. IONA is a leader in integration and SOA technology, and its heritage comes from a history of working with large, complex and heterogeneous enterprises. Artix, IONA’s extensible Enterprise Service Bus (ESB) is an essential component in any SOA. Artix is mature and proven technology, and has created the robust and resilient infrastructure to support mission-critical applications at companies such as BellSouth, Raymond James & Associates, Marconi, and Deutsche Post (DHL).

EAI: Rip and Replace or Leave and Leverage?


The Dilemma of EAI
Architects are constantly faced with the problems of managing legacy systems, and none are as pronounced as the ones associated with EAI. IT integration is a vital part of most business strategies, and the costs of supporting EAI climb non-linearly year after year. Service-oriented architectures (SOAs) are recognized as the architecture of choice for integrating diverse applications and systems because a SOA is inexpensive to maintain – standards make it possible for developers to interact with SOA components without having to learn new and proprietary technology, and without being dependent on the vendor for an adaptor. SOA facilitates service reuse – Because all services have a standard interface and can be accessed from the network, applications and backend systems can be easily reused in new business processes. SOA is agile – In addition to the reduced maintenance overhead, the distributed architect enables development teams to work independently of each other, freeing them from having restrictions imposed by other groups. The dilemma for architects is how to get to a SOA when there is already an EAI installation deployed. The choices are to continue using the EAI tools, replace the EAI system with a new platform, or migrate to a SOA using existing infrastructure components.

Continuing with EAI Tools
It is tempting to continue to use the EAI tools that are currently in place because they are a known entity and so much has already been invested in the system. In addition to satisfying the old adage “if it isn’t broken, don’t fix it,” staying with old technology eliminates the challenge of rearchitecting a complex environment. Unfortunately, those advantages are quickly outweighed by the standard maintenance costs and headaches that come every time a new application has to be integrated, or when an existing application or business process has to be modified. One IONA customer, a global telecommunications giant, estimated the costs incurred when integrating a new application or a change is made to an existing application:

EAI: Rip and Replace or Leave and Leverage?


Indirect Labor Custom development Software support Hardware support Maintenance Custom software Vendor software Hardware Capital Costs Software Hardware TOTAL per application: TOTAL annual costs: TOTAL after 5 years

$22,500 $5,500 $1,500 $2,000 $2,000 $3,000 $25,000 $62,000 $123,500 $741,000 $3,705,000

The Customer estimated that they would be integrating on average six new applications a year at an annual cost of $741,000. Over the course of five years, the price of staying with the EAI system amounts to $3,705,000. And, that assumes that the debilitating bottleneck created by the central server can be overcome. Not included in these calculations are the opportunities lost due to the high costs and difficulties of integrating applications.

EAI: Rip and Replace
As the complications of staying with an EAI system mount, many architects consider the rip-andreplace option: remove all components of the EAI system and replace them with state-of-the art SOA technology. The end result is desirable, but the obstacles speak directly to the bottom line. Architects and line of business managers have to consider and quantify these hurdles: Large upfront investment –Rip and replace requires purchasing new software and potentially new hardware just to bring the new enterprise to parity with the old enterprise. This is difficult to justify when the old system is fully paid for. Cost of disruption – This approach forces organizations to disrupt all processes and business systems connected to the EAI system during the replacement period. This can result in lost sales, irritated customers and reduced overall productivity. Disassembling what works – Perhaps the most daunting consequence of this approach is the risk incurred when eliminating a complex system that has been continuously updated and adjusted for many years.

EAI: Rip and Replace or Leave and Leverage?


The lofty ambitions originally envisioned are quickly dashed when the total cost of ownership is considered. Fortunately, there is another option.

EAI: Leave and Leverage
The third option is to leave existing infrastructure in place, and encapsulate the infrastructure components to interact within a SOA. When architects consider the functionality needed to support a SOA including transportation, transformation, security, management, to name a few, they see that most of what they need to create a SOA is already in place. By leveraging what is deployed and paid for, most of the work to create a SOA is already complete. IONA Artix does just that. IONA Artix advanced SOA infrastructure suite is an incremental SOA solution that noninvasively extends existing systems and applications. Artix streamlines, modernizes and lowers the operating costs of existing middleware investments to maximize the reuse of IT resources. Artix succeeds with an incremental approach by enriching existing components rather than forcing all components to be subservient to a central server. Artix adds integration services, support for Web services standards, and qualities of service (QoS) to existing systems to create service-oriented endpoints. Endpoints can be configured to include only the functionality needed to keep the footprint small, and can be dynamically changed without disrupting other infrastructure components. For more information on Artix, how it incrementally turns existing components into service-oriented endpoints, and its unique extensibility, refer to IONA’s Artix white papers available at The IONA telecommunications customer calculated the cost to add or modify a system with an Artix SOA and found it to be considerably less than with an EAI system:

EAI: Rip and Replace or Leave and Leverage?


Indirect Labor Custom development Software support Hardware support Maintenance Custom software Vendor software Hardware Capital Costs Software Hardware TOTAL: TOTAL annual costs: TOTAL after 5 years

$10,000 $0 $0 $1,000 $0 $0 $2,000 $0 $13,000 $78,000 $390,000

This is less than integration with EAI by an order of magnitude. Assuming 6 applications a year for 5 years, the Artix SOA costs $390,000 for a total savings of more than 89%, or $3,315,000.

Artix: Advanced SOA Infrastructure Suite
Artix comprises a comprehensive suite of products to streamline, modernize and lower the operating costs of complex and heterogeneous IT environments. The Suite includes Artix ESB – connects any service consumer with any service providers using any middleware by deploying, managing and securing a SOA without requiring a centralized hub Artix Registry/Repository – a phonebook-style listing of all available services with automatic provisioning and monitoring of services, to maximize reuse and ensure continued adherence to enterprise policies Artix Orchestration - facilitates the composition of fine-grained functionality into reusable services using BPEL to create business-level services Artix Data Services – a metadata management, data modeling, transformation and integration toolkit to abstract data services from the underlying transport and integration infrastructure

EAI: Rip and Replace or Leave and Leverage?


Artix Mainframe – a service-enablement engine that extends mainframe systems to integrate with off-host systems without the additional expense of running all applications on the mainframe SOA Management provided by AmberPoint - governs and manages a SOA implementation by monitoring the health of Artix ESB endpoint

EAI suites made great strides in integration technology, but they now remain as one of the most expensive legacy systems in enterprise organizations today. Architects, when faced with having to balance line-of-business requirements against maintenance concerns, are faced with the dilemma of what to do with the aging system. The safest and least expensive approach is to extend existing infrastructure components with Artix, and migrate incrementally towards a SOA. For more information on SOA architectures, the Customer’s deployment, or to schedule a Value Assessment to analyze a specific IT installation please contact an IONA representative. IONA customers use the extensible ESB to service-enable existing systems and establish a scalable, adaptable, SOA architecture. Customers including BellSouth, AT&T, Marconi, and Deutsche Post (DHL) chose Artix for its broad platform support, extensibility, and enterprise quality of service, and today they are building new business applications and process flows on common platforms such as Microsoft’s .NET Framework, IBM’s WebSphere, and BEA’s WebLogic.

IONA Technologies PLC The IONA Building Shelbourne Road Dublin 4 Ireland Phone +353 1 637 2000 Fax +353 1 637 2888 Support: WWW: IONA Technologies Inc. 200 West Street Waltham MA 02451 USA Phone +1 781 902 8000 Fax +1 781 902 8001 Training: IONA Technologies Japan Ltd Akasaka Sanchome Building 7/F 3-21-16 Akasaka Minato-ku Tokyo Japan Phone +813 3560 5611 Fax +813 3560 5612 Sales:

IONA, IONA Technologies, the IONA logo, Orbix, High Performance Integration, Artix, Celtix, Celtix Enterprise and Making Software Work Together are trademarks or registered trademarks of IONA Technologies PLC. COPYRIGHT NOTICE. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photo- copying, recording or otherwise, without prior written consent of IONA Technologies PLC. Copyright © 1999-2007 IONA Technologies PLC. All rights reserved. Any trademarks, service marks, or product names that may appear herein are the property of their respective owners.


Shared By:
kristopher mensing kristopher mensing crap