A Mashup-Based Strategy for Migration to Web 2.0

Transcription

1 A Mashup-Based Strategy for Migration to Web 2.0 Dr. Semih Çetin A Mashup-Based Strategy for Migration to Web 2.0 1

2 Content Statement of the problem and motivation Existing technologies and approaches A proposal for Web 2.0 migration strategy Closing remarks A Mashup-Based Strategy for Migration to Web 2.0 2

3 Statement of The Problem A Mashup-Based Strategy for Migration to Web 2.0 3

4 Service-Oriented Computing (SOC) is a fact today Service-Oriented Computing is multi-faceted fact with: Architecture (SOA Service-Oriented Architecture) Computing platform (ESB Enterprise Service Bus) Business model (BPM Business Process Management) SOC is somehow The Next Big Thing (Gartner): 80% of all software efforts will be based on SOA by % of the $527 billion IT professional service industry will be based on exploiting Web Services. Next generation Web (Web 2.0) will be the global SOA platform for applications. Web itself will be the global ESB containing several sub-esbs. Service-Oriented Computing is not easy to achieve. A Mashup-Based Strategy for Migration to Web 2.0 4

5 Difficulties of Service-Oriented Computing No common understanding A fundamental architectural style? A phenomenon to separate building blocks? A composite scheme for business process management? A holistic view covering all of the above? Narrow drivers, broad ambition Will it cut off the future costs? Do we know to define the impact? Skepticism a need for cultural change The technology doesn t work all the time. It is not for us. What about the millions of $ cost for existing investment? Maybe, the most challenging issue is migration. A Mashup-Based Strategy for Migration to Web 2.0 5

6 What business wants... Back Office Systems The Business Web Portal SAP Adapter Order Entry Peoplesoft Adapter Pay Bill Oracle Adapter Send Goods Swift Adapter A MashupMashup-Based Strategy for Migration to Web 2.0 6

7 How many adapters do you need? (250+) Adapter Classes Data Adapters: Provide a relational view of proprietary databases and file systems Application Adapters: e.g. SAP, Siebel, PeopleSoft, JDE ebusiness Adapters: e.g. EDI, SWIFT, cxml, HIPAA Transaction Adapters: e.g. CICS, IMS, Tuxedo Emulation Adapters: e.g. 3270, 5250 Touchpoint Adapters: e.g. Bill of Materials, Chart of Accounts, Purchase Order, Sales Order, Work Order & more Program Adapters: e.g. 3GL, 4GL, etc. A D A P T E R S Data Application ebusiness Transaction Emulation Touchpoint Program A Mashup-Based Strategy for Migration to Web 2.0 7

8 Barriers: Moving to Service-Oriented Computing B2C Integration Web 2.0 AJAX Rich Internet Applications (RIA) Representational State Transfer (REST)? B2B Integration Enterprise Internet Applications (EIA) Web Services (SOAP) or something else? Non-Functional Requirements (NFRs) Quality of Services (security, performance, robustness, etc.) Architectural modeling? Frameworks, Enterprise Service Busses, Infrastructures? Service enablement of today s legacy applications? A Mashup-Based Strategy for Migration to Web 2.0 8

9 Existing Technologies and Approaches A Mashup-Based Strategy for Migration to Web 2.0 9

10 Cybersoft Research on Web 2.0 Migration A Mashup-Based Strategy for Migration to Web

11 Moving to Web 2.0: Critical points for success... Web 2.0 does not have generic roadmap as a silver bullet Different legacy assets Different technologies Varying requirements (both functional and non-functional) Web 2.0 is technology-based Requires better infrastructures Necessitates better tools Web 2.0 is business-oriented Needs better models Requires business people involvement Should be enriched by declarative environments Web 2.0 is a strategy Should have strategic and tactical plans Should have a reuse strategy even in migration Return of investment should be crystal clear A Mashup-Based Strategy for Migration to Web

12 Migration Approaches to SOC by Early 2007 A Mashup-Based Strategy for Migration to Web

13 A Proposal for Web 2.0 Migration Strategy: MigrAtion to Service Harmonization computing Platform (MASHUP( MASHUP) A Mashup-Based Strategy for Migration to Web

14 What is MASHUP? Provides harmonization of Different legacy service enablement assets Different software technologies Varying requirements (both functional and non-functional) With Domain specific wrappers A common Choreography Engine Using Domain Specific Languages (DSLs) Domain Specific Engines (DSEs) Domain Specific Tools (DSTs) Based on Software Factory Automation (SFA) Service Asset Meta-Modeling (SAMM) Model-Driven Development (MDD) A Mashup-Based Strategy for Migration to Web

15 MASHUP is based on Service Mashups Web 2.0 COMPOSITION Relationship Management Rich Content Collaboration Discovery SOA Single User / App Global User / App A Mashup-Based Strategy for Migration to Web

16 Software Factory Automation (SFA) Approach Industrial Factory Programmable Logic Controller (PLC) Development Environment (DE) Computer Language (CL) Programmable Processor (PP) Software Factory Domain Specific Kit (DSK) Domain Specific Engine (DSE) Domain Specific Language (DSL) Domain Specific Toolset (DST) A Mashup-Based Strategy for Migration to Web

17 An Example to DSK (1): RDBMS DSK DST DSL DSE RDBMS Interactive SQL & DBA Utilities Structured Query Language Query Listener / Executer RDBMS is a business domain independent technology to be used without extensive programming efforts. SQL is generic enough to be a DSL. SQL is abstract enough to be used in wide variety. SQL is flexible enough for loosely-coupled designs. RDBMS is versatile enough to take part in choreography via different protocols: ODBC, JDBC, ADO, DAO, XA, etc. A Mashup-Based Strategy for Migration to Web

18 An Example to DSK (2): Web Server DSK DST DSL DSE Web Server HTML Authoring Tools Hyper Text Markup Language & XML HTTP Listener / Script Executer Web Server is a business domain independent technology to be used without extensive programming efforts. HTML/XML is generic enough to be a DSL. HTML/XML is abstract enough to be used in wide variety. HTML/XML is flexible enough for loosely-coupled designs. Web Server is versatile enough to take part in choreography via different protocols: HTTP, Socket, RPC, etc. A Mashup-Based Strategy for Migration to Web

19 Overview of The MASHUP Approach A Mashup-Based Strategy for Migration to Web

20 Software Factory Automation Model for MASHUP Software Factory Automation for Service-Oriented Computing Screen Scrappers for Mashups at B2C Level Reference Architecture Modeling A Software Factory Legacy Wrappers at B2B Level DSK DST DSL DSE Service Asset Repository Service Orientation Reference Architecture DSK DSK DSK DSK DSK Development & Administration Environment Service Asset Model Service Asset Meta Model Process And Service Quality Model Process Model A Mashup-Based Strategy for Migration to Web

21 MASHUP Methodology (1) Step 1: MODEL Models target business requirements Business model is expressed using a semantic notation (e.g. BPMN) Step 2: ANALYZE Analyzes existing legacy systems Quality of Service (QoS) attributes are identified Important data for Domain Specific Kits (DSKs) and reference architecture are revealed Step 3: MAP & IDENTIFY Maps functional and non-functional requirements to DSK components and composability issues for choreography Business Requirements to Services (B2RS) are determined Service to Service (S2S) requirements are determined A Mashup-Based Strategy for Migration to Web

22 MASHUP Methodology (2) Step 4: DESIGN Designs a concrete Mashup Server with DSKs Proper DSKs should be identified and associated languages, engines, and toolsets are developed Choreography Language is structured accordingly Step 5: DEFINE Defines Service Level Agreements Service repository is created QoS associations are described Step 6: IMPLEMENT & DEPLOY Implements and deploys the system Screen scrappers are implemented for service mashups and back-end functionality is wrapped by DSKs Components are deployed onto Choreography Engine A Mashup-Based Strategy for Migration to Web

23 Closing Remarks A Mashup-Based Strategy for Migration to Web

24 MASHUP Approach enables the context awareness and dynamic composition of legacy services via domain specific wrappers. does not re-engineer the existing source code. harmonizes the SOAP and REST models by means of a common Choreography Engine. improves the competitiveness of enterprises by moving to SOC fast and in a reusable manner. allows the dynamic harmonization of modern and legacy services. ensures the Quality of Services with an architecture-based and domain specific approach. provides declarative environments for business people. A Mashup-Based Strategy for Migration to Web

25 Why MASHUP is different Mashes up B2B Web Services with SOAP B2C Client Integration with REST (screen scrapping as needed) Ensures Quality of Services with Reference architecture modeling Domain specific wrappers Provides service interoperability through Service Asset Meta-Modeling (SAMM) A common Choreography Engine Maximizes the service reuse by Common service asset model Service asset repository (quick discovery of services) Migration strategy wrapped by Domain Specific Kits A Mashup-Based Strategy for Migration to Web

26 MASHUP Workplan MASHUP is 36-months project Detailed Business Plan is ready It has 8 Work Packages It requires collaborative research and industrial partnership 10 technical papers have already been published and presented A Ph.D. Thesis has been completed for background research and preliminary implementations A Mashup-Based Strategy for Migration to Web

27 What we look for... Strategic Partner for Investing in the research and development of MASHUP Using and marketing MASHUP for real-life cases Research Partners for Stabilizing the solid research background Exploring the what-if cases collaboratively Industrial Partners for Developing Legacy Service Wrappers (DSKs) Experiencing and improving the concept and tools Creating business channels for MASHUP A Mashup-Based Strategy for Migration to Web