Скачать презентацию introduction to soarchitect agenda Скачать презентацию introduction to soarchitect agenda

5232a2260e29451a1ff594dbc227f869.ppt

  • Количество слайдов: 35

introduction to soarchitect introduction to soarchitect

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

developer suite • integrated, on-the-fly environment – – • modular architecture – • reuse developer suite • integrated, on-the-fly environment – – • modular architecture – • reuse existing applications rapidly extend and integrate 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

looksoftware dynamic environment looksoftware dynamic environment

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

web services and SOA • the vision – “by 2006, 60% of organizations will 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 i. Series market – – it’s early days for web services, let alone SOA selective service enablement provides reuse benefits • without redevelopment or invasive restructuring

web services and SOA • • any language (RPG, COBOL) can support SOA service 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 DB 2, ADO for SQL Server Oracle…) important questions – – be practical, where is the ROI? what is the “right” level of granularity?

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

web services and SOA • consumption versus provision – consumption (calling) a web service 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

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

questions for SOA products • our solution: – – – no need to change 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

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

soarchitect Transaction Recorder for packaging existing 5250 applications script access for • • – soarchitect Transaction Recorder for packaging existing 5250 applications script access for • • – – – DDM database access ADO database access RPC for execution of i. Series programs and commands execution of external Web Services execution of COM/Active. X components

case study - Vic. Roads • background – – – • statutory authority for case study - Vic. Roads • background – – – • statutory authority for vehicle registration responsible for 4 million vehicles stable, robust i. Series and z. Series applications call center issues – 3. 8 minutes per call • – – operators switch between 3 different systems potential for data entry errors • – 400, 000 calls per annum re-keying of data potential legal liabilities

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

Vic. Roads i. Series screen flow sign on main menu enquiry menu input vehicle Vic. Roads i. Series screen flow sign on main menu enquiry menu input vehicle identifier confirm prompt output encumbrance type

create a reusable service module sign on main menu enquiry menu input vehicle identifier create a reusable service module sign on main menu enquiry menu input vehicle identifier confirm prompt output encumbrance type transaction

transaction recorder transaction recorder

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

transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component 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

transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component 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

transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component 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

transaction recorder • records 5250/3270 screen flows • creates a transaction • reusable component 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

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

Vic. Roads Step 1 smart client Vic. Roads Step 1 smart client

Vic. Roads results • • reduced average call duration by 40 -50% automated workflow Vic. Roads 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

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

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

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

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

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

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

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

summary • • soarchitect can SOA enable your existing applications you can interface at 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