1 / 35

introduction to soa rchitect

introduction to soa rchitect. agenda. SOA background and overview transaction recorder summary. developer suite. integrated, on-the-fly environment reuse existing applications rapidly extend and integrate modular architecture add modules as required broad functionality

hazelwood
Télécharger la présentation

introduction to soa rchitect

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. introduction to soarchitect

  2. agenda • SOA background and overview • transaction recorder • summary

  3. developer suite • integrated, on-the-fly environment • reuse existing applications • rapidly extend and integrate • modular architecture • add modules as required • broad functionality • rapid ROI from UI frameworks • supports non-invasive and invasive modernization • deliver new solutions with composite applications • service-enable existing assets for web services and SOA

  4. looksoftware dynamic environment

  5. web services and SOA • SOA is an architecture • goal is to increase reuse • the concept is not new • web services standards • have industry-wide support • SOAP, UDDI, WSDL • continue to evolve • this presentation focuses on practical web service enablement of iSeries applications

  6. web services and SOA • the vision • “by 2006, 60% of organizations will be using SOA” • “composite applications are entering maturity on the hype cycle” • “Software As A Service will be THE business model of choice by 2008” Source: Gartner • the reality for the iSeries market • it’s early days for web services, let alone SOA • selective service enablement provides reuse benefits • without redevelopment or invasive restructuring

  7. web services and SOA • any language (RPG, COBOL) can support SOA • service enablement of existing applications • changing the application is typically not required • may span part of a program or multiple programs • access available at all layers • presentation (5250, 3270) • application (RPG, COBOL, Java, C#...) • data (DDM for DB2, ADO for SQL Server Oracle…) • important questions • be practical, where is the ROI? • what is the “right” level of granularity?

  8. web services and SOA • service enablement benefits • wrap once, access from anywhere • improved interoperability • component level access to existing applications • increased reuse, flexibility, productivity • eg multi-channel delivery • non-invasive • reduced risk, timeframes, costs • rapid ROI

  9. web services and SOA • consumption versus provision • consumption (calling) a web service • eg third party Address Validation service • provision (creating, exposing) a web service • eg external entity accesses your application • the focus of this session

  10. questions for SOA products • How does soarchitect support SOA? • What are the benefits of soarchitect to your business?

  11. questions for SOA products • our solution: • no need to change your applications • Transaction Recorder to simplify Web Service definition • no new languages need to be learnt • requires lookserver and your current infrastructure • does not impact your use of RPG/COBOL • can work with your existing applications

  12. soarchitect primary capabilities • create a web service from an existing iSeries application • transform a monolithic iSeries program to a number of services • service-enable existing applications to provide the benefits of SOA

  13. soarchitect • Transaction Recorder for packaging existing 5250 applications • script access for • DDM database access • ADO database access • RPC for execution of iSeries programs and commands • execution of external Web Services • execution of COM/ActiveX components

  14. case study - VicRoads • background • statutory authority for vehicle registration • responsible for 4 million vehicles • stable, robust iSeries and zSeries applications • call center issues • 3.8 minutes per call • 400,000 calls per annum • operators switch between 3 different systems • potential for data entry errors • re-keying of data • potential legal liabilities

  15. VicRoads existing system • 3 separate core applications • green screen user interface • re-keying, Alt/Tab process

  16. VicRoads iSeries screen flow sign on mainmenu enquiry menu inputvehicleidentifier confirm prompt outputencumbrance type

  17. create a reusable service module sign on mainmenu enquiry menu inputvehicleidentifier confirm prompt outputencumbrance type transaction

  18. transaction recorder

  19. transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component • enables work offline • exposed as a web service

  20. transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component • - enables work offline • - exposed as a web service • transaction consists of • - a collection of steps

  21. transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component • - enables work offline • - exposed as a web service • transaction consists of • a collection of steps • navigation

  22. transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component • - enables work offline • - exposed as a web service • transaction consists of • a collection of steps • navigation • - input/output parameters • - literals

  23. transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component • - enables work offline • - exposed as a web service • transaction consists of • - a collection of steps • - navigation • - input/output parameters • literals • events • - trigger additional processing

  24. VicRoads existing system • 3 core applications • green screen user interface • rekeying, Alt/Tab process

  25. VicRoads Step 1 smart client

  26. VicRoads results • reduced average call duration by 40-50% • automated workflow • 25 host green screen transactions across 3 applications • modules can be reused as web services • eliminated re-keying of data and switching between applications reducing errors • no changes to host applications • ROI in 4 months

  27. VicRoads existing system • 3 core applications • green screen user interface • rekeying, Alt/Tab process

  28. VicRoads Step 1 smart client • defined reusable service modules • smart/rich client provides unified view • automate business process • no changes to host applications

  29. VicRoads Step 2 IVR • reuse same service modules • integrate with Interactive Voice Response (IVR) • bypass call center • further cost savings, improve customer service

  30. VicRoads Step 3 XML documents • reuse same service modules • trading partner collaboration • batches of vehicles require same checks • further reduce costs, improve partner service

  31. VicRoads summary • reuse same service modules • deliver “new” solutions through multiple channels • no changes to existing applications • practical path to SOA

  32. VicRoads summary • build SOA, create more services modules • improved productivity and flexibility • capability to deliver composite applications • refining, streamlining business processes

  33. VicRoads summary • services layer provides insulation against change • change the backend, minimal impact on business • practical path to SOA

  34. summary • soarchitect can SOA enable your existing applications • you can interface at the presentation, program or database levels • you do not need to change the way you develop your applications • creates componentized applications which are better for modernization and integration

More Related