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 and IT Pain Points
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

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
business services (Business)
future vision
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. 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
Regulatory Compliance
soa
Quote to Cash KM
CDI Solution
Customer Acquisition
Role Based Portal (workbench) BI
Business Value
Service Delivery
Utility Computing
Monitoring
Data Warehouse
BPM
Enterprise Security
ESS
CSS
SDS
Collaboration
Service Management
ESB
traditional approach
Portal Front-end for COTS
Portal Front-end for Mainframe
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
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. 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. SOA Lifecycle Initiate Develop SOA Roadmap Execute Plan Initiate SOA
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
Portfolio Management
Project
Management
Application
Infrastructure
Data
Testing
Publish
Discover
Governance
Organization
Skills Mapping
Review and Update Roadmap

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. 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 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. SOA Reference Architecture Web 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 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. 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 Data
Legacy

21. SOA Reference Architecture Web Application Tier: Custom Application 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 , 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. 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
User Interface
xyz
data
rst
Application
Criteria
List
Search Framework
Query Definition
Query Definition
Search Framework

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

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

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

27. 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
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
BEA Weblogic review Go
Results
LinuxPlanet reviews: BEA Weblogic for Linux…
BEA Weblogic review forum
More >> x
Welcome, Rhonda Hocker
Wednesday, February
Configure Portal 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
BEA Calendar
External Sources
BEA news (Factiva)
Industry news
Stock Quotes
Google Search
Yahoo Mail x
BEA x
From
Subject
Received
Philippe.B…. WLI Strategy /04/2004
Dale Slaug Re: SOA Architecture 02/03/2004
Yogish Pai SOA Architecture 02/
More >>
Major Opportunities
Customer
Name
Value
Albertson’s 8.1 WLI / WLP $7.5M
AT&T Portal 8.1 … $2M
Verizon W.. Platform / Ent.. $15M
More >> x
Yahoo Mail x
Sender
Subject
Date
Size
Friday trip Sun 2/1 2K
lara.en… Request Sun 2/1 1K
Remind… Birthday Reminder Fri 1/30 3K
More >>
Draft - Folders - Trash
Registry
of existing portlets
(local & remote)
My Travel
Conf #
Descrfption
Start Date
SFO-BOS-SFO Feb 14
SFO-LHR-SFO Feb 22
Make a reservation >> x
BEA Address Book x
Ashburn Go
Tom Ashburn IM
BEA News (Factiva) x
Prudential Selects BEA Systems …
E*Trade Japan builds Linux-based …
Norvergcence Standardizes on BEA...
More >>
Placement of portlets in the portal will be dynamic and also configurable by user

28. SOA Reference Architecture Services Tier: Enterprise Service Bus
SLA Monitor
Client App
JMS
Dynamic Message Transformation
Data Validation & Invoke External Service
Dynamic Message Transformation
JMS
Client App
JMS Queue WS
Message Broker
Message Broker
Client App
File
CORBA
Client App 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

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
Interoperability
Service Consumer
Service Producer
Runtime binding
Publish
Service Registry

30. 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

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. 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. Mapping SOA Reference Architecture to the Enterprise SOA Maturity Model
Traditional Development
Develop Web Applications
Composite Applications
Automate BP
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, , 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.
Shared Data Services: Extract, Transform & Load (ETL), Electronic Data Interchange (EDI), Enterprise Information Integration Data Quality (Matching Engine, Master Data Management)
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

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