1. SOA with Progress Philipp Walther Consultant

2. © 2007 Progress Software Corporation2 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio  Case Studies  Summary  Next Steps

3. © 2007 Progress Software Corporation3 Must reuse existing assets …not designed to collaborate Must show rapid, measurable ROI Can’t introduce operational risk …IT Bound By Constraints Develop new products and services Speed business transactions Comply with governance Integrate acquisitions Outsource business functions Business Demands Change… The Pressure on IT Information Technology

4. © 2007 Progress Software Corporation4 Introducing SOA  An Approach For Building Agile and Flexible Business Applications Loosely coupled systems = loosely coupled (flexible) business processes  SOA Is Not: A product or application A specific technology A specific standard A specific set of rules

5. © 2007 Progress Software Corporation5 Service Provider  Accomplishes A Defined, Self- Contained Unit Of Work Does not depend on the state of other process/functions  Internal Details Hidden Programming language The execution logic The data store (if any)  Exposes An Agreed-Upon Interface Stable- built to last! Service Interface Service Implementation Data Service Logic It’s all about Services…

6. © 2007 Progress Software Corporation6 Service Contract  What Service Operations Are Available The input & output messages supported by each operation The data representation model of each message's contents  Rules/Policies For Using The Service  Quality Of Service Aspects Terms And Conditions For Service Requestor

7. © 2007 Progress Software Corporation7 Implementing Service Contracts  Hardcopy Specification  Shared XML Schema  Representational State Transfer (REST) HTTP Get/Post/Put/Delete and XML  Web Service Description Language (WSDL) Available business methods (“operations”) Message structure (data fields, types) Bindings for operations (SOAP over HTTP) Some possibilities…

8. © 2007 Progress Software Corporation8 Services In Action Service Interface Service Implementation Service Provider Data Service Logic Service Requestor Fn() Service RequestService Response

9. © 2007 Progress Software Corporation9 SOA Infastructure  Connects Service Consumers With Providers  May Be Used To Communicate With Service Registry  May Be Implemented Using A Variety Of Technologies Service Requestor Service Requestor Service Provide r Service Provide r SOA Infrastructure AppServer™ REST JMS FTP Web Services

10. © 2007 Progress Software Corporation10 Defining Services: OpenEdge® Reference Architecture Presentation Business Services Data Access Data Sources Common Infrastructure Enterprise Services Service Requestor Service Provider

11. © 2007 Progress Software Corporation11 Getting Started With SOA: Initial Services  Benefit: New Functionality  Scope: R&D experiments, pilot projects, web site, portal, custom integrations, small number of services  Champion: Development Managers  Goals: Learn SOA Technology  Practices: Creating Service Definitions 5 Optimized Business Services 4 Measured Business Services 2 Architected Services 3 Business Services Collaborative Services a b 1 Initial Services

12. © 2007 Progress Software Corporation12 Example: Initial Services Online Ordering Application Online Ordering Application Order Management Customer Management Inventory Management Basic Service Layer Application Client Layer Warehouse Application Warehouse Application

13. © 2007 Progress Software Corporation13 Next Step: Institutionalize SOA  Benefit: IT Cost Reduction And Control  Scope: Multiple Integrated Applications  Champion: CIO  Goals: Institutionalize Use Of SOA  Practices: Setting Key Technology Standards For Protocols, Platforms, Policies And Processes 5 Optimized Business Services 4 Measured Business Services 2 Architected Services 3 Business Services Collaborative Services a b 1 Initial Services

14. © 2007 Progress Software Corporation14 Multi-Level SOA Online Ordering Application Online Ordering Application Order Management Customer Management Inventory Management Basic Service Layer Application Client Layer Order and Ship Intermediate Service Layer

15. © 2007 Progress Software Corporation15 Process-Driven SOA Online Ordering Application Online Ordering Application Order Management Customer Management Inventory Management Basic Service Layer Application Client Layer Order and Ship Intermediate Service Layer Catalog Service Business Process Service Layer Order Cancellation Service

16. © 2007 Progress Software Corporation16 Is The Integration Problem Now Solved?  How Do You Deploy, Monitor And Control The Services Or Their Interactions?  How Do You Connect Legacy Systems With Different Protocols  How Do You Mediate Data Formats And Interaction Models  How Does It Scale It Up? J2EE™ APPLICATION PACKAGED APPLICATION & LEGACY SYSTEMS.NET™ APPLICATION PARTNER SYSTEM FUTURE SERVICES

17. © 2007 Progress Software Corporation17 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio  Case Studies  Summary  Next Steps

18. © 2007 Progress Software Corporation18 Enterprises Are Complex Your Offering Web SiteEAI Supply Chain Headquarters Module 2 Module 3 Module 1 Partner Website Web Order Entry Accounting Application CRM Application XML Partners EDI Partners Corp Purchasing Corp Accounting Corporate System Trading System

19. © 2007 Progress Software Corporation19 No Flexibility, No Control USER-DEFINED SERVICE LEGACY APPLICATION PROCESS SERVER RELATIONAL DATABASE BATCH SYSTEM PORTAL SERVICE APPLICATION SERVER Integration done “Once in a row”

20. © 2007 Progress Software Corporation20 Processes Are Fragmented Applications deployed in different departments and business units become silos of data and process. How can I flexibly incorporate data and process from across the enterprise?

21. © 2007 Progress Software Corporation21 SOA Vision APPLICATION SERVER USER-DEFINED SERVICE LEGACY APPLICATION PROCESS SERVER RELATIONAL DATABASE BATCH SYSTEM PORTAL SERVICE By 2008, Gartner predicts that SOA will be a prevailing software-engineering practice, ending the 40-year domination of monolithic software architecture Idealized world where data and process flows naturally

22. © 2007 Progress Software Corporation22 Sonic ESB APPLICATION SERVER USER-DEFINED SERVICE LEGACY APPLICATION PROCESS SERVER RELATIONAL DATABASE BATCH SYSTEM PORTAL SERVICE Pre-built SOA infrastructure The direct path to SOA

23. © 2007 Progress Software Corporation23 Enterprise Service Bus (ESB)  Standards-Based Integration Backplane  Provides Connectivity, Scalability, Security  Connects Applications Expressed As Services  Provides Data Transformation, Content-Based Routing Web Service Web Service OpenEdge App OpenEdge App Siebel Legacy App. Java™ App. Java™ App. PeopleSoft Enterprise Service Bus (ESB)

24. © 2007 Progress Software Corporation24 The ESB Approach INFRASTRUCTURE SERVICES RELIABLE COMMUNICATIONS SERVICE MEDIATION SERVICE HOSTING Advanced service-handling capability

25. © 2007 Progress Software Corporation25 Provide Additional SOA Infrastructure ENTERPRISE SERVICE BUS APPLICATION OPENEDGE APPLICATION.NET™ APPLICATION PARTNER SYSTEM WEB SERVICE …To map services, processes and IT assets

26. © 2007 Progress Software Corporation26 Adding Value Beyond Basic Services  Mediate The Interchange Reliably transport business data and events Enforce security policies Transform data between services  Control The Process Define and alter process flows Track business transactions between applications ESB capabilities…

27. © 2007 Progress Software Corporation27 Adopting An ESB  Benefit: Business Responsiveness  Scope: Processes Across & Beyond Business Unit  Champion: Business Unit Manager  Goals: Ongoing Partnership Between Business And Technology Organizations  Practices: Specify Policies For Use Of SOA In Creation, Change Of Processes 5 Optimized Business Services 4 Measured Business Services 2 Architected Services 3 Business Services Collaborative Services a b 1 Initial Services Collaborative Services b