ARCH-01: Introduction to the OpenEdge™ Reference Architecture

1. ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group

2. Agenda • Architecture defined • Why is architecture important? • Reference architectures and the OpenEdge Reference Architecture • Anatomy of the OpenEdge Reference Architecture ARCH-01 – Intro to the OpenEdge Reference Architecture

3. Agenda • Architecture defined • Why is architecture important? • Reference architectures and the OpenEdge Reference Architecture • Anatomy of the OpenEdge Reference Architecture ARCH-01 – Intro to the OpenEdge Reference Architecture

4. What Is Architecture? The structure and organization of a software system • The principles and standards that define how an application is organized • Captured not in code, but the code itself • The result of analysis and design • The foundation of application documentation • Forward-looking Architecting is the discipline of designing an application to meet needs T ARCH-01 – Intro to the OpenEdge Reference Architecture

5. Agenda • Architecture defined • Why is architecture important? • Reference architectures and the OpenEdge Reference Architecture • Anatomy of the OpenEdge Reference Architecture ARCH-01 – Intro to the OpenEdge Reference Architecture

6. Why Is Architecture Important? • Architecture represents foundational design decisions • Hardest to change later on • Most critical to get right up front • Architecture serves as a foundation for the capture of intellectual property • Code • Business rules/domain expertise • A vehicle for communication • Sponsors • Developers • Project Managers • Documenters • Customers The blueprint for a successful software application ARCH-01 – Intro to the OpenEdge Reference Architecture

7. Agenda • Architecture Defined • Why Is Architecture Important? • Reference Architectures and the OpenEdge Reference Architecture • Anatomy of the OpenEdge Reference Architecture ARCH-01 – Intro to the OpenEdge Reference Architecture

8. What is a “Reference Architecture”? Guidance for success • Taken at literal value – • “Architecture”: The structure of an application • “Reference”: Intended to provide guidance • Reference Architectures are for knowledge transfer and learning • Applications/code • Documents • Diagrams • Describing and demonstrating best practices for software application development ARCH-01 – Intro to the OpenEdge Reference Architecture

9. The OpenEdge Reference Architecture • Conceptual level guide / roadmap • Combines latest industry, Progress and community best practices • Link to details - • Models and patterns • Scenarios and use cases • Methodology • Common vocabulary for discussion • Technology independent until Implementation time ARCH-01 – Intro to the OpenEdge Reference Architecture

10. Defining a Competitive Application Know where you are, and where you want to go Desired Situation Scope Componentize Integrate Collaborate Global BM3 – Model, Manage, Monitor BPM –Business Process Mgmt • Full SOA • - Contracts • Service Desc • Open Stds • - Security etc models GLOBALISE BUSINESS SERVICES Service Enable Your App 4 Hor. & Vertical Int. Supplier of choice to Global Accounts - Transacting across Industry Supply Chains Extended Enterprise WORKFLOW Template process / work flow control with Flex rules EXPOSE Expose Process Level Business Components as Services MODULARISE Group Bus. Functions into Service Domains Supplier of choice for Enterprise Solutions Enterprise Admin, Management and Monitoring Growing Businesses with Modern, Best of Breed Business Applications CO-ORDINATE Manage Events and In-Process Flow / Thread Control FORMALISE Formalise Interface Defns / APIs N-TIER Separate BL from UI, Data Access, External Conn. Application Tool Support Processing Engines Services Platform ARCH-01 – Intro to the OpenEdge Reference Architecture

11. Modern Application Architectures Separated presentationand integration layers Common business logic withadvanced models Data accessabstracted fromstorage OpenEdge Reference Architecture – a layered view Users Enterprise Services Presentation Layer/s Integration Layer/s Business Servicing Layers Data Access Layers Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

12. Agenda • Architecture Defined • Why Is Architecture Important? • Reference Architectures and the OpenEdge Reference Architecture • Anatomy of the OpenEdge Reference Architecture ARCH-01 – Intro to the OpenEdge Reference Architecture

13. OpenEdge Reference Architecture Users Enterprise Services Presentation Layer Integration Layer Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

14. Presentation Layer Users Enterprise Services User Interaction Point for the Application Presentation Layer Integration Layer Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

15. Integration Layer Users Enterprise Services Data-Centric Integrates data from existing systems Presentation Layer Integration Layer Functional Integrates processes with existing systems Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

16. Business Servicing Layer Users Enterprise Services Presentation Layer Integration Layer AppServer™ Business Logic The body of domain expertise Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

17. Business Entities Users Enterprise Services Provide single-point of definition, interaction, and management for all persistent application entities Presentation Layer Integration Layer BusinessEntities Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

18. Business Tasks Users Enterprise Services Presentation Layer Integration Layer Encapsulate reusable business functions, algorithms and calculations Business Tasks BusinessEntities Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

19. Workflow STOP Alert Users Enterprise Services Presentation Layer Integration Layer Automates a business process according to a set of business rules BusinessWorkflows Business Tasks BusinessEntities Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

20. Data Access Layer Users Enterprise Services Presentation Layer Integration Layer Data access abstracted from storage Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

21. Environment Managers and Utilities Users Enterprise Services Centralize application feature support Presentation Layer Integration Layer Environment Managers and Utilities Business Servicing Layer Data Access Layer Managed Data Stores Unmanaged Data Stores ARCH-01 – Intro to the OpenEdge Reference Architecture

22. In Summary… • Architecture is key to successful applications • The OpenEdge Reference Architecture provides guidance for building competitive applications ARCH-01 – Intro to the OpenEdge Reference Architecture

23. Next Steps… • Learn more about the OpenEdge Reference Architecture • This conference • Progress Software Education Services • Begin assessing your business goals and application(s) ARCH-01 – Intro to the OpenEdge Reference Architecture

24. Questions? ARCH-01 – Intro to the OpenEdge Reference Architecture

25. Thank you for your time! ARCH-01 – Intro to the OpenEdge Reference Architecture

26. ARCH-01 – Intro to the OpenEdge Reference Architecture