• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

The 3 Keys to Extending the Value of Your IT Assets with SOA

  • 472 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
472
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The 3 Keys to Extending the Value of Your IT Assets with SOA
  • 2. Agenda:
    • Understanding SOA –
      • Eric Newcomer, IONA
    • SOA Best Practices –
      • Shankar Kambhampaty, Satyam Computer Services
    • Leveraging IT Assets – An ESB Case Study
      • Ivan Casanova, IONA
  • 3. … at a glance
    • EMEA HQ in Dublin, Ireland
    • US HQ in Massachusetts
    • APAC HQ in Tokyo, Japan
    Worldwide presence
    • Founded in 1991
    • Publicly traded since 1997
    • Solid financials
    NASDAQ:IONA Solid business with a history of profitable growth
      • Deliver high performance integration for mission critical application
      • Make heterogeneity asset not a liability
      • Deliver on the value proposition of standards
    Our Approach: Making Software Work Together ™
    • 80% of Global Telecom
    • 70% of Financial Services in Global 100
    • Blue Chip System Integrator Partners
    Customers include world’s largest firms
  • 4. SOA: A Business Imperative
  • 5. What Customers Tell Us …
    • Customers Tell Us
      • Dissatisfaction with buying experience
      • Increasing technology complexity and exploding data volumes
      • Systems too rigid, not agile to market demands
      • Need to do more and more with less and less
      • Path to agility and ROI not always clear
    • Analysts and the Market Tells Us
      • Software industry is maturing
      • Trend is toward open source and low cost labor
      • Standards are multiplying and fragmenting
      • More than 75% of services will be derived from existing applications
  • 6. SOA – Promises the Answer
    • The evolution of a thirty year drive towards standards-based, distributed computing and component based development
    • Driven by the economics of system re-use and ubiquity of global high speed network connectivity
    • Natural progression towards loosely coupled interacting systems – defined by standard interfaces to “services”
    Host The Web Service Oriented Architecture Client / Server Distributed Computing Era
  • 7. Why is SOA so Important?
    • Reduce IT expenses
      • Reuse existing application functionality
      • Improve developer productivity
    • Increase operational efficiency
      • Share data across departments, divisions
      • Automate common business processes
    • Develop new business opportunities
      • Provide new and better customer service
      • Respond to market changes
    • It’s the “IT assembly line”
  • 8. IONA and its Customers Pioneered SOA
    • 1500 services in production
    • 100,000+ users
    • 1B txns/year, 5M/day
    • 73% cost reduction for systems development and integration
    • Reuse of 70% of services
    • Secure / Reliable
  • 9. SOA Is Technology Neutral
    • Architecting SOA has historically meant trade-offs
      • CORBA – Well defined contracts, Auto-generate proxies/skeletons, Multi-language bindings, Open standard, Enterprise QoS out of the box, CORBA required at both ends
      • MQ – Low coupling, Enterprise QoS, Not designed as a service platform, Proprietary
      • J2EE – No contract language, Uni-lingual, Open standard, Enterprise QoS, Large developer community, Java required at both ends
      • HomeGrown – “Have it your way”, Ranges from Useless to Comprehensive, Always expensive
    MQSeries Home Grown Web services and the ESB have emerged to address these issues
  • 10. WSDL is the Unifying Standard
    • Extensibility
    • Handles Both Internet and Existing Networks
    • Strong Developer Interest / Multi-vendor support
    • Thriving ISV tool market / open source community
    Service Port IIOP (not in IDL) Binding Class/Type XML Data Type Parameter Part in/out/inout Message Method Operation Interface PortType CORBA IDL WSDL Logical Contract Physical Contract MQSeries Home Grown WSDL - Web Services Definition Language
  • 11. Major IT Improvements from SOA
    • Services model human and business functions
      • Brings technology closer to human understanding
      • Request list of customers
      • Update the customer’s order
      • Notify the call center operator
      • Transfer my funds
    • Services are technology independent
      • A “style of design” not a thing
      • Execute them using any combination of CORBA, WebSphere MQ, J2EE, .NET, CICS, etc.
    • Services are best defined by the data they exchange
  • 12. SOA Best Practices
  • 13. SOA Best Practices
    • Assess Need for SOA
      • Look at SOA in the context of the business of Enterprise in addition to the context of specific applications
      • Consider SOA when Reusability and Enterprise Application Integration are Key concerns
      • Establish Benefits and ROI of SOA implementation for the Enterprise
    • “ Don’t do SOA for SOA’s sake”
  • 14. SOA Strategy
    • Develop a SOA Strategy
      • For example –
      • Define a framework so that different applications exposing services know precisely how to define a Service
      • Enable applications to use the services offered by other applications through Web Services.
      • Identify a mechanism for integration (viz: an ESB) and to search and locate services exposed by applications
  • 15. SOA Guidelines
    • Prepare SOA Guidelines
      • Develop a common view across the Enterprise and build consensus
      • Prepare a Architecture “Blue Book” with Architecture principles and Reference Architecture for the enterprise
      • Identify Strategic Technology Stack and model implementations
      • Get buy-in from Key stakeholders
      • Establish Governance Model and identify “Champion” who oversees implementation across the Enterprise
  • 16. SOA Roadmap
    • Define SOA Roadmap
      • Simple: Target less Complex activities
        • Service enable identified applications in one department/unit
        • Develop Proof-of-Concept (PoC) involving an Enterprise Service Bus
      • Medium: Take on Medium Complexity
        • Service Enable applications in multiple departments and implement Service Consumption by Clients in limited manner
      • Go for the Enterprise
  • 17. SOA Implementation
    • Assess the Need for SOA
    • Develop a SOA Strategy
    • Prepare SOA Guidelines
    • Define SOA Roadmap
    • Implement SOA
  • 18. Leveraging Valuable IT Assets – The ESB in Action
  • 19. Traditional EAI and Platform Vendor Server-Centric, Hub-Based Solutions Authorize Proprietary Broker J2EE-based solution Transformation Business Rules MetaData Orchestration Custom Services Routing Security Tools Management Proprietary Protocol Proprietary Protocol Authorize Proprietary Protocol Proprietary Protocol Adapter Order Management Adapter Customer Care Adapter Fulfillment Adapter Provisioning
  • 20. ESB Value Proposition – Eliminates the Expensive Middle Artix End-Point Artix End-Point Artix End-Point Order Management Customer Care Fulfillment Provisioning Proprietary Protocol Network Proprietary Protocol Proprietary Protocol Artix End-Point Proprietary Protocol Includes
  • 21. ESB Endpoint Infrastructure
    • Lower cost of entry
    • Faster time to ROI
    • Adaptable infrastructure
    • Services reside within applications
    • Endpoints are configurable
    • Endpoints are dynamic
    Fully Distributed Architecture Reducing Total Cost of Ownership
  • 22. Artix Extensible ESB
    • Web services-based integration software for enterprise IT organizations with multiple generations of business applications, technologies and architectures
    • Designed for complex, mission-critical integration challenges
  • 23. Requirements for This Transition ….
  • 24. Broad Platform Support
    • Across Operating Systems:
      • Mobile to Mainframe Platform Coverage
    • Runs Across Any Container:
      • Stand Alone Service
      • Embedded in a CORBA Server, Tuxedo Server, J2EE Server, Microsoft .NET
    • Support Native Platform Tools:
      • Native tools
      • QOS
      • Deployment
  • 25. Broad Platform Support J2EE Application Server MQ JMS TIBCO CORBA Existing Enterprise System Microsoft.NET Client MQ JMS TIBCO CORBA Existing Enterprise System OS390 CICS IMS Web Service Consumers SOAP SOAP CORBA Web Service Consumers SOAP SOAP
  • 26. Leave and Layer Approach
    • Leave existing assets in place and include them as part of a SOA
    • Eliminates the disruption and upfront costs
    • Allows organizations to move forward and benefit from the efficiency and agility of a SOA
    Multi-Protocol ESB Distributed ESB Services ESB Endpoints J2EE or .NET Services Celtix Services COTS Services WSDL WSDL WSDL WSDL WSDL WSDL Routing Transformation Security Management Directory Services H/A Services
  • 27. Plug-In Architecture
    • Transports, Protocols, Application Platforms and Value-Added Services
      • Popular messaging middleware & application platforms
      • Plug-Ins extend existing security, management, high availability and transaction capabilities
  • 28. Enterprise Qualities of Service Java Server CORBA Server C++ Server C++ Mainframe .NET Client Java Client Mobile Device Systems Management Security Services Transaction Services H/A Services Directory Services
  • 29. SOA – Key Sources of Value
    • No Hub – distributed solution eliminates the costs of creating and maintaining another major server in the enterprise
    • Reduced Maintenance – simpler architecture and standards-based technology reduces support costs and headcount
    • Agile – systems can be modified or added with minimal cost and without disrupting deployed infrastructure
  • 30. Summary
    • SOA is a Business Imperative
      •  costs,  efficiency, enables new business
      • IONA was a SOA pioneer with Orbix
      • Continues to deliver tech-neutral SOA solutions
    • SOA Best Practices
      • Apply SOA to solve a business problem, not for its own sake
      • Take inventory, get buy-in, establish a Framework
      • Use an incremental approach
    • Artix Leverages Existing Assets for SOA
      • Plug-in architecture, broad platform support, enterprise QoS
      • Enables incremental, leave-and-layer approach
      •  expensive,  disruptive,  agile than server-based solutions
  • 31. Thanks … Questions?
  • 32. For More Information
    • Satyam:
    • www.satyam.com or [email_address]
    • IONA:
    • www.iona.com or [email_address]
    • Upcoming Webcasts:
      • Replays available at www.iona.com/webcasts
    Free Artix download at www.iona.com/artix