SOA Alliance SOA Reference Architecture Contributors Ashok Kumar

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 SOA Lifecycle & Maturity Model SOA Reference Architecture 2

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

The ideal architecture representation of a typical current state does not cut Representation it any more 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 4

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

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

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

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 8

SOA Blueprint deliverables SOA Blueprint Section Deliverable Starting with 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 9

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 10

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

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 12

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

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

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

SOA Reference Architecture – “Future For Version 1. 0 the focus of SOA State Architecture” 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 16

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 17

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 18

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 19

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

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

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

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

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

SOA Reference Architecture Web Application Tier: Enterprise Infrastructure Services Provide standard enterprise infrastructure services Ø Ø Director Service (LDAP v 3. 0 or above) Personal Information Management: Calendar, e. Mail, 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 25

SOA Reference Architecture Web Application Tier: Enterprise Portal Ent. Portal Cluster Custom App COTS Ent. Srvs WSRP Custom App DB LDAP WSRP COTS WSRP Ent. Srvs Legacy DB Current State LDAP Legacy Future State Users login to a single portal that presents information (portlets) from multiple sources 26

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

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

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

SOA Reference Architecture Services 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 30

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 J 2 EE or object-oriented design 31

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 32

Mapping SOA Reference Architecture to the Enterprise SOA Maturity Model Traditional Development Develop Web Applications Composite Applications Automate BP Enterprise Services: Basic services required across the enterprise. Examples: Directory Service, Content Management, Search, e. Mail, Calendar, IM, Discussion Forum, White Board, etc. 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 Enterprise Portal: Role based portal that is available 24 x 7. Provides single point of entry for all users, multi-channel support, consistent look and feel, access to business capabilities based on role. 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. Business Process Manager: Configure Shared Data Services: Extract, and automate business process. Provide business users the capability to modify the business process & policies. Transform & Load (ETL), Electronic Data Interchange (EDI), Enterprise Information Integration Data Quality (Matching Engine, Master Data Management) Service Registry: Service registry containing service properties such as service capabilities, parameters, service levels, etc. 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. . Business Service Management: Monitoring, capacity planning, utility computing 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 33

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