1. SOA Alliance: SOA Reference Architecture Contributors: Ashok Kumar, Cendant Jeffery Lamb, Wells Fargo Tom Mitchell, Wells Fargo Burc Oral, Dev Atma Technologies Yogish Pai, BEA Systems Sankar Ram Sundaresan, HP

2. 2 Agenda Industry Background SOA Blueprint Objectives SOA Lifecycle & Maturity Model SOA Reference Architecture

3. 3 Business Pain Points  Globalizations: Competition from geographies that have lower cost structures  Economic Pressures: Record cash reserves but anemic growth  Business Process Outsourcing: Outsource non-core capabilities  Regulatory Compliance: Must comply to stay in business  Technology: New technologies that provide additional business capability  IT Investments: Investment in improving IT efficiency, rather than creating new business opportunities IT Pain Points  Globalizations: Business acting globally and IT is an after thought  Economic Pressures: IT not generally viewed as a differentiator  Business Silos: redundant infrastructure and higher cost  Lack of Cohesive Business Information Strategy across the enterprise  Governance & Organization for agility  Standards: At last count over 50 standard bodies  Technology Refresh: Business reluctant to upgrade to latest versions Business and IT Pain Points

4. 4 The ideal architecture representation of a typical current state does not cut it any more Representation of the enterprise architecture of an highly successful IT organization (Complex and Expensive) Enterprise are attempting to increase revenue (cross sell or up sell existing customers) and reduce cost (especially IT) SOA enables Enterprises to achieve both these objectives Alternate vision is to consolidate business process to applications provided by a single vendor

5. 5 Both Business and IT have the same future vision and have different approaches to get there Business Complexity Business Value traditional approach soa current state infrastructure services (IT) business services (Business) future vision Portals Integration App Server Database COTS packages, etc. Process Driven Enterprise Business Priority IT Priority

6. 6 Business Solutions SOA’s unique value proposition – Business Solutions through infrastructure instead of Business Solutions through applications Business Complexity Business Value traditional approach soa Portal Front-end for COTS Portal Front-end for Mainframe Monitoring Regulatory Compliance ESS CSS Utility Computing Customer Acquisition Service Delivery Quote to Cash Business shall tend to prioritize business solutions over infrastructure SOA provides IT the ability to build out the infrastructure while meeting immediate business needs Infrastructure CapabilitiesBusiness Process Enterprise Security KM Role Based Portal (workbench) Collaboration BI Data Warehouse Service Management CDI Solution ESBSDSBPM

7. 7 Agenda Industry Background SOA Blueprint Objectives SOA Lifecycle & Maturity Model SOA Reference Architecture

8. 8 SOA Definition and Objectives SOA is the business operations strategy for leveraging information to meet their objectives, such as increasing overall revenue, increasing customer satisfaction, improving product quality, etc. To provide leadership in the industry by identifying the end customers and IT needs Provide a roadmap for successful adoption of SOA Identify important business and technology patters of SOA

9. 9 SOA Blueprint deliverables SOA Blueprint Section Deliverable Starting with SOA SOA Lifecycle, Maturity Model and defining SOA Strategy SOA Reference Architecture The proposed end-state architecture SOA Framework SOA Methodology similar to Enterprise Architecture Framework Governance and Organizations Document various patters and best practices around governance and organizations Service Lifecycle Service definition, deployment and management process including templates, best practices, patterns, etc. Appendix Frequently Asked Questions (FAQs) Common vocabulary The SOA Blueprint shall be living document that is constantly updated based on the community experience

10. 10 Intended Audience for the SOA Blueprint Business sponsors of IT projects and IT leadership team responsible for SOA across the Enterprise or LOB Enterprise Architects who shall be responsible for driving the vision, roadmap and architecture or each of these implementations The Program Management Office so that they can get a better understanding of how to manage SOA initiatives The Project teams so that they can get a better understanding of how to map dependencies and develop a timeline that meets business expectations The vendors who shall be providing the products and tools Standards bodies so that they can get a better understanding with use cases on how end users plans to leverage technology to meet their business objectives

11. 11 Agenda Industry Background SOA Blueprint Objectives SOA Lifecycle & Maturity Model SOA Reference Architecture

12. 12 The three steps of SOA Lifecycle 1.Initiate SOA  Establish the process for getting started  Establish objectives, project teams, timelines, deliverables, etc. 2.Develop Roadmap  Establish SOA Principles  Develop Reference Architecture  Develop SOA roadmap based on business priority 3.Execute SOA Roadmap  Initiate transformation Business and IT by establishing SOA Governance  Manage Services Portfolio and execute roadmap  Revise and update roadmap on a periodic basis, based on internal and external environmental changes

13. 13 SOA Lifecycle Portfolio Management Project Management Application Infrastructure Data Testing Publish Discover Project Objectives Develop SOA Roadmap Team Members FTE & PT Timeline & Deliverables 6-12 weeks Initiate SOA Initiate Business Principles Application Principles Technology Principles Data Principles Business Architecture BPM, COTS, etc. Infrastructure Arch Portal, SO, ES, etc. Information Arch MDM, ODS, DW, etc. SOA Principles Reference Architecture Develop Roadmap Based on Biz Priorities Develop SOA Roadmap Execute SOA Roadmap Execute Plan GovernanceOrganizationSkills Mapping Review and Update Roadmap

14. 14 Understand the SOA Maturity Model enables enterprises to develop the roadmap to achieve “Future Vision” Following are the three stages of SOA Maturity Model  Phase 1: Develop Web Applications – demonstrate “quick wins” to business by rapidly deploying new business solution by reusing services  Phase 2: Develop composite applications such as single view of the customer or automate integration points between systems  Phase 3: Automate Business Processes across the enterprise or LOB It is not necessary to exist one stage to start the next

15. 15 Agenda Industry Background SOA Lifecycle & Maturity Model SOA Blueprint Objectives SOA Reference Architecture

16. 16 SOA Reference Architecture – “Future State Architecture” For Version 1.0 the focus of SOA Reference Architecture with three major tiers for providing business capabilities  Web Application Tier (sometimes also referred to as the Presentation Tier) provides the multi-channel web presence for the enterprise  Service Tier provide service lifecycle management, service discovery and composition capability. Also provides services that cross application boundary  Application Tier contains the traditional legacy or mainframe applications and EAI

17. 17 SOA Reference Architecture Web Application Tier Packaged Applications  Industry standard core applications – robust core business logic and data structure  Vanilla Implementation (limit custom changes) Easier and cheaper to maintain Easier and cheaper to upgrade or replace  Footprint – Limited to the best of the breed  One standard Implementation Worldwide Limitations of Packaged Applications  Modification of business process and user interface is not very easy  Most packaged applications are still based on proprietary technology Difficult to find resources Upgrades are expensive Integration is not straight forward

18. 18 SOA Reference Architecture Web Application Tier Custom Applications categories 1. Develop a custom (web) application leveraging an Application Servers 2. Develop a custom (web) application leveraging a Portal product 3. Develop a thick client by either using tools based on open standards or proprietary technology  Focus of this presentation shall be on option 1 & 2

19. 19 SOA Reference Architecture Web Application Tier Custom Application Requirements  Provide unified user experience across the web site  Standardize look and feel across all the sites  Create a single point to access all information  Provide only the information the user has access to  Provide a highly reliable, available and scalable environment  Provide user the capability to personalize their pages  Reduce operational cost / TCO

20. 20 SOA Reference Architecture Web Application Tier: Custom Application Architecture Approach Based on SOA that promotes re-use at multiple levels Provides rapid delivery capability Leverage each product for what it is good at, example portal for presentations based on entitlements Enable business to combine multiple services to provide new capabilities Loosely coupling presentation from the business logic makes it reliable and scalable Presentation Business Delegate Services Domain Layer Directory Service App DataLegacy

21. 21 SOA Reference Architecture Web Application Tier: Custom Application Framework Components Framework Components Description Data Services, Logging, Exception Handling, Applications Configuration, Monitoring Standard framework components and most IT organizations already have these components Search Framework Service leveraged by the Presentation tier for paginations Notification Framework Leverage for any external notification such as eMail, IM, SMS, etc. Service Proxy Service proxy to EJBs, Web Services or any other external service/protocol Security Framework consisting of Authentication, Authorizations, SSO, Identity Management, Auditing Standard client security framework to integrate with enterprise security service as well as develop custom authorization modules for the applications

22. 22 SOA Reference Architecture Web Application Tier: Custom Application Framework Components Dynamic query generation based on user input Consistent mechanism for handling search Abstract all database access code from applications Query reside in external files Utilities to handle common UI tasks xyz data rst data User Interface Application Search Framework Criteria List Query Definition Search Framework

23. 23 SOA Reference Architecture Web Application Tier: Custom Application Framework Components One notification client for all applications Supports Synchronous and Asynchronous interface to the notification engine Capabilities to send notifications to multiple channels Notification Framework Notification Notification Engine Channel Handler eMailIMSMS JMS Template Channel Config.

24. 24 SOA Reference Architecture Web Application Tier: Custom Application Framework Components Allows services to deployed locally or remotely, transparent to the presentation layer EJB Service EJB Proxy WS Proxy …. Proxy Web Service …. Service Service Proxy Presentation Layer (Business Delegate) Service Repository Service GetAddiress GetSupportCases AddContact Target EJB Service WSService ESB Service Proxy

25. 25 SOA Reference Architecture Web Application Tier: Enterprise Infrastructure Services Provide standard enterprise infrastructure services  Director Service (LDAP v3.0 or above)  Personal Information Management: Calendar, eMail, Address Book, etc.  Content Management System: Standardize on one across the Enterprise/LOB and provide interfaces and best practices  Search: Standardize on a search engine across the Enterprise/LOB and provide interfaces and best practices

26. 26 SOA Reference Architecture Web Application Tier: Enterprise Portal Users login to a single portal that presents information (portlets) from multiple sources Custom AppEnt. SrvsCOTS DBLDAPLegacy Cluster Custom AppEnt. SrvsCOTSEnt. Portal DBLDAPLegacy WSRP Current State Future State

27. 27 Registry of existing portlets (local & remote) New functions and content can be added on the fly simply by adding the remote portlet web service definition to the catalog – The resulting portals can be continuously expanded without affecting current functions Welcome, Rhonda Hocker Wednesday, February 4 2004 Google Search BEA Weblogic review Go Results -LinuxPlanet reviews: BEA Weblogic for Linux… -BEA Weblogic review forum - More >> x BEA Email x FromSubjectReceived Philippe.B…. WLI Strategy 02/04/2004 Dale Slaug... Re: SOA Architecture02/03/2004 Yogish Pai SOA Architecture02/03.2004 More >> Yahoo Mail x SenderSubjectDateSize jk100@... Friday trip Sun 2/12K lara.en…RequestSun 2/11K Remind… Birthday ReminderFri 1/303K More >> Draft - Folders - Trash BEA Address Book x Ashburn Go Tom Ashburn408-570-8628Email - IM Placement of portlets in the portal will be dynamic and also configurable by user Available Portlets can reside either in internal servers or external providers – all communication to remote portlets through Web Services Major Opportunities CustomerNameValue Albertson’s8.1 WLI / WLP$7.5M AT&TPortal 8.1 …$2M Verizon W..Platform / Ent..$15M More >> x My Travel Conf #DescrfptionStart Date 0192985SFO-BOS-SFOFeb 14 0194677SFO-LHR-SFOFeb 22 Make a reservation >> x BEA News (Factiva) x -Prudential Selects BEA Systems … -E*Trade Japan builds Linux-based … -Norvergcence Standardizes on BEA... -More >> Configure Portal V V Employee Self Service My Benefits My Information My Payroll My Travel My Purchasing Electronic W2 Sales Support Major Opportunities Customer Contacts Productivity BEA Address Book BEA Email BEA Calendar External Sources BEA news (Factiva) Industry news Stock Quotes Google Search Yahoo Mail x x x x x x x x x SOA Reference Architecture Web Application Tier: Enterprise Portal Example

28. 28 SOA Reference Architecture Services Tier: Enterprise Service Bus Provide Message and Service broker capability Dynamic message & transformation Data Validation & invocation of external services Monitor SLA’s for each of the services Client App JMS Queue Client App File Client App Message Broker Dynamic Message Transformation Data Validation & Invoke External Service Dynamic Message Transformation Message Broker JMS WS JMS WS CORBA Service Log SLA Monitor

29. 29 SOA Reference Architecture Services Tier: Service Registry Service Registry contains Service descriptions and contract information Supports UDDI Configuration and administration console Provide horizontal and vertical replication capability Service Consumer Service Producer Service Registry Publish Runtime binding Interoperability

30. 30 SOA Reference Architecture Services Tier: Shared Data Services Provide data modeling capability across multiple sources Develop query (read & write) across multiple sources (Standards bodies have so far defined only the read operations – SDO) Provide data transformation capability Provide data validation capability Expose data services to client applications – RMI or Web Services Database File Application Adapters LDAP Enterprise Information Integration

31. 31 SOA Reference Architecture SOA Framework Required to enable rapid development and consists of following layers  Transformation Layer  Business Logic Layer  Business Data Layer  Integration Layer Reasons for an SOA Framework  Solid foundation for creating services  Improved productivity  Utilize Off-the-self framework  Don’t need to know the internals of J2EE or object-oriented design

32. 32 SOA Reference Architecture SOA Framework Business Benefits of the SOA Framework  Catalyst for adopting SOA  Consistent design and development process across all projects  Repeatability and the ability to guarantee a minimal level of architecture and design rigor  Improved business agility as a result of having modular solutions that can be changed easily (often via configuration changes)  Use of software engineering best practices amongst developers with varying skill levels  More consistent, predictable and better tested solutions  Improved mobility of developers to move from one project to another

33. 33 Enterprise Portal : Role based portal that is available 24x7. Provides single point of entry for all users, multi-channel support, consistent look and feel, access to business capabilities based on role. Custom Applications : These are either built on an App Server, Portal or proprietary thick client. Application Framework required to leverage reuse. Examples: Logging, Exception handling, data services, application configuration, monitoring, search framework, notification framework, service proxy, Single Sign-On Packaged Applications : These are the best of the breed packaged application that also act as the system of record for a particular business function. Enterprise Services : Basic services required across the enterprise. Examples: Directory Service, Content Management, Search, eMail, Calendar, IM, Discussion Forum, White Board, etc. Business Process Manager : Configure and automate business process. Provide business users the capability to modify the business process & policies. Enterprise Service Bus : Route services to the appropriate destination; receive and transmit messages in any protocol, provide message transformation, routing, validation, auditing, security, monitoring and reporting services. Service Registry : Service registry containing service properties such as service capabilities, parameters, service levels, etc. Shared Data Services : Extract, Transform & Load (ETL), Electronic Data Interchange (EDI), Enterprise Information Integration Data Quality (Matching Engine, Master Data Management) Service Manager : Manage service lifecycle across the enterprise. Enterprise Application Integration : Traditional enterprise integration approach. Provide Application Adapters, Business Process, Messaging, Security, etc. capabilities. Mostly proprietary in nature and application integration generally implemented as a point-to-point integration on a Hub.. Legacy Application : Applications that do not have open APIs & are not web based Mainframe Application : Access data via gateways Enterprise Security : Provide user authentication, authorization, identify management, profile management, delegated admin, etc. Business Service Management : Monitoring, capacity planning, utility computing Mapping SOA Reference Architecture to the Enterprise SOA Maturity Model Traditional Development Develop Web Applications Composite Applications Automate BP

34. SOA Alliance: SOA Reference Architecture Contributors: Ashok Kumar, Cendant Jeffery Lamb, Wells Fargo Tom Mitchell, Wells Fargo Burc Oral, Dev Atma Technologies Yogish Pai, BEA Systems Sankar Ram Sundaresan, HP