1. Rob Straight SOA-1: Applied SOA: Building Out Your SOA Environment with OpenEdge ® Principal Product Manager

2. © 2008 Progress Software Corporation2 What If You Could…  Speed business transactions  Re-use existing software assets Reduce costs Extend lifetime of assets  Integrate acquisitions  Quickly develop new products and services Address new market opportunities and cope with ever-changing business requirements

3. © 2008 Progress Software Corporation3 Today’s Business Environment  Distributed, 24x7 operations  Heterogeneous systems  Poor application-to-application connectivity  Data access and consistency challenges Raw Goods Inventory Accounting Order MGMT Supply Chain Production Control Credit Control HQ Retail Plant Distribution Center Supplier Partner

4. © 2008 Progress Software Corporation4 Screen Scrape Screen Scrape Screen Scrape Screen Scrape Message Queue Message Queue Message Queue Download File Download File Download File Transaction File Transaction File Transaction File ORB CICS Gateway APPC RPC Transaction File Sockets Message Application Source: Gartner The Technical Challenge

5. © 2008 Progress Software Corporation5 Agenda  SOA Concepts  Getting Started with SOA using OpenEdge  Examples

6. © 2008 Progress Software Corporation6 What is SOA?  A software systems architectural style  An approach for building agile and flexible business applications, based on services  Loosely coupled services = flexible business processes Service-Oriented Architecture

7. © 2008 Progress Software Corporation7 GET OUT OF MY KITCHEN! Real-World Service Example

8. © 2008 Progress Software Corporation8 Service Provider  Accomplishes a defined, self-contained unit of work Does not depend on the state of other processes/functions  Internal details hidden Programming language Execution logic Data store (if any)  The service, exposed using a service interface, is stable and built to last Service Implementation Data Business Logic Service Interface

9. © 2008 Progress Software Corporation9 Service Contract  Service provider defines the available service operations Input & output information supported by each operation Data representation model for each parameter  Rules and/or policies for using the service  Quality of Service (QoS) attributes

10. © 2008 Progress Software Corporation10 Service Requester  Presentation (UI) layer or another service  Locates service provider through agreed-upon service directory  Binds/invokes a service based on a service contract  Service adapter encapsulates all issues associated with accessing the service Fn() Service Adapter

11. © 2008 Progress Software Corporation11 SOA Infrastructure Services In Action Service Provider Service Requester Fn() Service Adapter Service RequestService Response Service Implementation Data Business Logic Service Interface Service Contract

12. © 2008 Progress Software Corporation12 SOA Infrastructure  Connects service requesters with providers  May communicate with a Service Registry  A variety of technologies available Service Provider Service Provider SOA Infrastructure Service Requester Service Requester FTP AppServer™ Messaging HTTP+XML (REST) Web Services

13. © 2008 Progress Software Corporation13 SOA: Just Service Providers & Requesters?  How do you: SOA-enable existing applications? Mediate service interactions? Compose and reuse service capabilities?  Don’t forget about Distribution, Scalability, Reliability and Security! OPENEDGE APPLICATION PACKAGED APPLICATION & LEGACY SYSTEMS.NET™ APPLICATION PARTNER SYSTEM J2EE™ APPLICATION Web Services Interface SOAP HTTP XML

14. © 2008 Progress Software Corporation14 Enterprise Service Bus  Abstract the service location  Facilitate service exchanges with the desired QoS  Promote reuse through service composition SONIC ™ ESB ENTERPRISE SERVICE BUS OPENEDGE APPLICATION PACKAGED APPLICATION & LEGACY SYSTEMS.NET APPLICATION PARTNER SYSTEM J2EE APPLICATION

15. © 2008 Progress Software Corporation15 Agenda  SOA Concepts  Getting Started with SOA using OpenEdge  Examples

16. © 2008 Progress Software Corporation16 OpenEdge Reference Architecture Presentation Business Components Data Access Data Sources Common Infrastructure Enterprise Services Service Provider Service Requester

17. © 2008 Progress Software Corporation17 Business Components Start Order Update Customer Check Inventory Schedule Shipping Close Order Getting Started Defining OpenEdge Services PROCEDURE StartOrder:.. END. PROCEDURE UpdateCustomer:.. END. PROCEDURE CheckInventory:.. END. PROCEDURE ScheduleService:.. END. PROCEDURE CloseOrder:.. END. PROCEDURE StartOrder:.. END. PROCEDURE UpdateCustomer:.. END. PROCEDURE CheckInventory:.. END. PROCEDURE ScheduleService:.. END. PROCEDURE CloseOrder:.. END. PROCEDURE StartOrder:.. END. PROCEDURE UpdateCustomer:.. END. PROCEDURE CheckInventory:.. END. PROCEDURE ScheduleShipping:.. END. PROCEDURE CloseOrder:.. END.

18. © 2008 Progress Software Corporation18 Using Initial Services Business Components On-line Order Entry Start Order Update Customer Check Inventory Schedule Shipping Close Order Warehouse Application Mainframe.NETJava ™ OpenEdge

19. © 2008 Progress Software Corporation19 Composite Services Business Components On-line Order Entry Start Order Update Customer Schedule Shipping Close Order Warehouse Application Check Inventory Order and Ship Data Transformation Intermediary Services

20. © 2008 Progress Software Corporation20 Enterprise Service Bus Start Order Update Customer Check Inventory Data Transformation Order and Ship Schedule Shipping Close Order On-line Order Entry Warehouse Application Sonic ESB

21. © 2008 Progress Software Corporation21 Progress Technology Supporting SOA  OERA, ABL, ProDataSets, XML, Web services  Application Server & Open Clients  SOA Portfolio: Enterprise Messaging & Service Bus SOA & Business Process Management Registry/Repository Data Interoperability Complex Event Processing Mainframe Integration

22. © 2008 Progress Software Corporation22 Agenda  SOA Concepts  Getting Started With SOA using OpenEdge  Examples

23. © 2008 Progress Software Corporation23 Getting Started with SOA: Pilot Project Example  Situation Specialized lighting manufacturer 27 corporate divisions: no common integration Re-use mix of OpenEdge and other solutions  Pilot project: start small and build on success Deliver part diagrams electronically  Next look outward: invoicing service Suppliers send invoices to a service Correlate purchase orders & receipts to invoices

24. © 2008 Progress Software Corporation24 SOA to Increase Business Example  Situation Financial services company with 250K customers and 20K transactions/day Goal: customer/revenue growth through superior on-line banking & call center Lacked integration across 8 backend systems and 2 external partners  Layered architectural and services approach Started with internal processes first

25. © 2008 Progress Software Corporation25 ESB Technical Solution Overview SOAP WebServices Client HTTP WS JMX Management and BAM 1 Validate Route 2 DB WS HTTP WS 3 Back-Office Application 3 Process Model Business Process 3 FTP SMTP 44 3

26. © 2008 Progress Software Corporation26 Results  Lowered development time 40% and cost 50% Now have the ability to change business logic independent of other layers  Successfully managing 1M+ messages / day  50% increase in on-line customers in first 6 months  Improved customer service while reducing costs  The technology is very exciting, but… Stay focused on reusable business logic Do not add complexity if it is not needed

27. © 2008 Progress Software Corporation27 Establishing New Sales Channels Example  Situation $40M company shipping 6,000 packages/day Goal: common infrastructure for the print catalog, online and retail store sales channels Phase 1: Catalog system to make order fulfillment  Followed the SOA pattern: Reusable OpenEdge components for common activities, e.g. tax calculations Messaging replaces batch Integrated to backend systems (e.g. AS400, Unisys) without application code changes ESB validates and transforms data

28. © 2008 Progress Software Corporation28 Results  Only 6 months from initial design to deployment! System is extremely stable  Flexible business processes without coding changes  Near real time processing as compared to batch

29. © 2008 Progress Software Corporation29 In Summary  SOA is the architecture for the agile business A design approach, not a technology  OERA provides a framework  Progress Software supplies the technologies you need to achieve your SOA

30. © 2008 Progress Software Corporation30 For More Information  PSDN Service-Oriented Architecture http://www.psdn.com/library/kbcategory.jspa?categoryID=1591 OpenEdge & Sonic Evaluation Kits http://www.psdn.com/library/entry.jspa?externalID=1131  Education: eLearning Catalog http://www.psdn.com/library/entry.jspa?externalID=4734

31. © 2008 Progress Software Corporation31 Relevant PSDN Live Sessions SOA-2Introduction to the Sonic ESB Product Family DEV-8AppServer Mode Case Studies SOA-3Extending Your Application with OpenEdge Web Services SOA-4Enabling Your OE Application with Web 2.0 SOA-5Introducing Native Invocation with the OpenEdge Adapter for Sonic ESB

32. © 2008 Progress Software Corporation32 Questions ?

33. © 2008 Progress Software Corporation33 Thank You

34. © 2008 Progress Software Corporation34