1 / 34

SOA Alliance: SOA Reference Architecture

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. Agenda. Industry Background SOA Blueprint Objectives

Download Presentation

SOA Alliance: SOA Reference Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  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. Agenda • Industry Background • SOA Blueprint Objectives • SOA Lifecycle & Maturity Model • SOA Reference Architecture

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

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

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

  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. SOA Blueprint deliverables The SOA Blueprint shall be living document that is constantly updated based on the community experience

  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. Agenda • Industry Background • SOA Blueprint Objectives • SOA Lifecycle & Maturity Model • SOA Reference Architecture

  12. The three steps of SOA Lifecycle • Initiate SOA • Establish the process for getting started • Establish objectives, project teams, timelines, deliverables, etc. • Develop Roadmap • Establish SOA Principles • Develop Reference Architecture • Develop SOA roadmap based on business priority • 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. Execute Plan Develop SOA Roadmap Initiate Reference Architecture Initiate SOA SOA Principles Execute SOA Roadmap Business Principles Business Architecture BPM, COTS, etc. Project Objectives Develop SOA Roadmap Project Management Application Testing Application Principles Infrastructure Arch Portal, SO, ES, etc. Infrastructure Publish Team Members FTE & PT Technology Principles Information Arch MDM, ODS, DW, etc. Discover Data Timeline & Deliverables 6-12 weeks Data Principles Develop Roadmap Based on Biz Priorities Governance Organization Skills Mapping Review and Update Roadmap SOA Lifecycle Portfolio Management

  14. 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 Understand the SOA Maturity Model enables enterprises to develop the roadmap to achieve “Future Vision”

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

  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. SOA Reference ArchitectureWeb 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. SOA Reference ArchitectureWeb Application Tier • Custom Applications categories • Develop a custom (web) application leveraging an Application Servers • Develop a custom (web) application leveraging a Portal product • 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. SOA Reference ArchitectureWeb 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. 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 SOA Reference ArchitectureWeb Application Tier: Custom Application Architecture Approach Presentation Business Delegate Services Domain Layer Directory Service App Data Legacy

  21. SOA Reference ArchitectureWeb Application Tier: Custom Application Framework Components

  22. 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 rst data data data data data data SOA Reference ArchitectureWeb Application Tier: Custom Application Framework Components User Interface Application Criteria List Search Framework Query Definition Query Definition Search Framework

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

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

  25. SOA Reference ArchitectureWeb 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. Ent. Srvs Ent. Portal Custom App Ent. Srvs COTS Ent. Portal COTS Custom App SOA Reference ArchitectureWeb Application Tier: Enterprise Portal Cluster WSRP WSRP WSRP • Users login to a single portal that presents information (portlets) from multiple sources DB LDAP Legacy DB LDAP Legacy Current State Future State

  27. Available Portlets can reside either in internal servers or external providers – all communication to remote portlets through Web Services 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 Google Search x x Configure Portal BEA Weblogic review Go 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 V • Results • LinuxPlanet reviews: BEA Weblogic for Linux… • BEA Weblogic review forum • More >> BEA Email x From Subject Received Yahoo Mail Major Opportunities x Philippe.B…. WLI Strategy 02/04/2004 Dale Slaug... Re: SOA Architecture 02/03/2004 Yogish Pai SOA Architecture 02/03.2004 More >> Customer Name Value x Albertson’s 8.1 WLI / WLP $7.5M AT&T Portal 8.1 … $2M Verizon W.. Platform / Ent.. $15M More >> x x x Sender Subject Date Size My Travel x Conf # Descrfption Start Date jk100@... Friday trip Sun 2/1 2K lara.en… Request Sun 2/1 1K Remind… Birthday Reminder Fri 1/30 3K More >> Draft - Folders - Trash 0192985SFO-BOS-SFO Feb 14 0194677SFO-LHR-SFO Feb 22 Make a reservation >> x BEA Address Book x x BEA News (Factiva) x x Ashburn Go Tom Ashburn 408-570-8628 Email - IM Placement of portlets in the portal will be dynamic and also configurable by user V SOA Reference ArchitectureWeb Application Tier: Enterprise Portal Example x • Welcome, Rhonda Hocker • Wednesday, February 4 2004 Registry of existingportlets (local & remote) • Prudential Selects BEA Systems … • E*Trade Japan builds Linux-based … • Norvergcence Standardizes on BEA... • More >>

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

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

  30. SOA Reference ArchitectureServices Tier: Shared Data Services Enterprise Information Integration Database File Application Adapters LDAP • 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

  31. SOA Reference ArchitectureSOA 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. SOA Reference ArchitectureSOA 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. 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. Enterprise Services: Basic services required across the enterprise. Examples:Directory Service, Content Management, Search, eMail, Calendar, IM, Discussion Forum, White Board, etc. Shared Data Services: Extract, Transform & Load (ETL), Electronic Data Interchange (EDI),Enterprise Information Integration Data Quality (Matching Engine, Master Data Management) Business Process Manager: Configure and automate business process. Provide business users the capability to modify the business process & policies. 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.. Packaged Applications:These are the best of the breed packaged application that also act as the system of record for a particular business function. 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 Service Registry: Service registry containing service properties such as service capabilities, parameters, service levels, etc. Service Manager: Manage service lifecycle across the enterprise. Business Service Management:Monitoring, capacity planning,utility computing 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. Enterprise Security: Provide user authentication, authorization, identify management, profile management, delegated admin, etc. Mainframe Application :Access data via gateways Legacy Application:Applications that do not have open APIs & are not web based 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

More Related