Service Oriented Architecture SOA An Overview from BEA - PowerPoint PPT Presentation

1 / 29
About This Presentation
Title:

Service Oriented Architecture SOA An Overview from BEA

Description:

High-level depiction of architectural layers and their relationships ... Functional depiction of architectural layers and components to illustrate ... – PowerPoint PPT presentation

Number of Views:74
Avg rating:3.0/5.0
Slides: 30
Provided by: jesp7
Category:

less

Transcript and Presenter's Notes

Title: Service Oriented Architecture SOA An Overview from BEA


1
Service Oriented Architecture (SOA) An Overview
from BEA
SOCITM East Regional ConferenceSeptember 2007
  • Kenneth Wright
  • BEA Systems Ltd
  • September 2007

2
About BEA Systems
  • At a Glance
  • 1.4B revenue
  • 2,000 partners
  • 4,200 employees
  • 18,000 customers
  • BEA AquaLogic, WebLogic and Tuxedo product
    families

3
SOA Adoption Trends 2005 - 2007
Source InfoWorld 2007 SOA REPORT
2007 Service-Oriented Architecture Graduates to
the Enterprise
4
Service-Oriented Architecture (SOA)
SOA is an architectural approach that enables the
creation of loosely coupled, interoperable
business services that can be easily shared
within and between enterprises.
Service-Oriented Architecture
5
Service-Oriented Architecture (SOA)
Need to Consider some target architecture
SOA is an architectural approach that enables the
creation of loosely coupled, interoperable
business services that can be easily shared
within and between enterprises.
Service-Oriented Architecture
6
Service-Oriented Architecture (SOA)
Need to think about standards, visibility
SOA is an architectural approach that enables the
creation of loosely coupled, interoperable
business services that can be easily shared
within and between enterprises.
Service-Oriented Architecture
7
Service-Oriented Architecture (SOA)
SOA is an architectural approach that enables the
creation of loosely coupled, interoperable
business services that can be easily shared
within and between enterprises.
Service-Oriented Architecture
Need to give each role their own view on how to
find services. Must be easy to understand, have
well defined rules of engagement, well documented
and linked for each role.
8
Application Infrastructure vs. Service
Infrastructure
  • Application Infrastructure
  • Service Design and Enablement
  • Execution Environment
  • Enterprise-Class RASP
  • Service Infrastructure
  • Cross-platform management
  • Governance and control
  • Service publishing and discovery
  • Service and data integration
  • Security
  • Process orchestration
  • Business interaction

9
SOA Reference Architecture Layered Views
10
SOA Starting Points
High
MegaProjects
Business-LedProjects
Business Sponsorship
ProcessProjects
IT-LedProjects
Low
Low
High
SOA Complexity
11
SOA is Business Driven
Product inquiry
SOA A Service Invocation Framework
Product inquiry
12
SOA Service Lifecycle Design, Development and
Deploy
Business Analyst
Business Process Modeling
ServiceArchitect
Business Activity Monitoring
Core Metadata
Management
Service Development
Service Develop and Deploy
BusinessOperations
Monitoring
13
Service ModelingServices That Map To Real
Business Processes, Not As Silo-ed Apps
  • Think strategically, execute tactically start
    with a single core process
  • Top down identify the services required to
    support this single core process
  • Bottom up identify functions in existing systems
    that could be exposed as services to support this
    process
  • Infrastructure services identify common
    supporting functionality requirements

14
What is a Service
  • Service Contract
  • The service contract specifies the purpose,
    functionality, constraints, and usage of a
    service. The contract is defined by the business
    in business terms.
  • Service Interface
  • A Service interface provides a means for the
    users of a service to access its functionality
    according to the contract it offers. A given
    service may offer multiple interfaces to allow
    consumption of the service through different
    means.
  • Service Implementation
  • The implementation part of a service is the
    actual code. The implementation may be
    accomplished using any technology.
    Implementations, especially early ones, often
    represent functionality that already exists in an
    enterprise.

15
Project Approach Incremental Project Harvesting
Applications
Composite Applications
1
2
3
Presentation Services
1
3
4
5
5
8
Service Infrastructure Layer
Shared Business Services
Services Management
Service Bus
Common Services
6
7
5
9
10
11
12
2
7
8
9
7
3
Information and Access Services
10
11
7
1
2
4
6
8
12
10
11
9
3
11
9
1
7
Cost Curve Over Time
Services Catalog
1
2
3
4
5
6
7
8
9
10
11
12
16
Shared Services Functional Architecture
Business Process Services
Shared Services
17
Service Modeling
Service Modeling What services should be
created? What is the process for identifying
these services? What are the characteristics
that identify these services?
?
?
?
?
?
Business Process Services
?
Shared Services
?
?
?
?
18
Service Enablement
Business Process Services
Shared Services
19
Integration Services
Composite Applications
Shared Service Access
Business Process Services
Shared Services
20
Business Process Services
Business Process Services
Shared Services
21
Presentation Services
Business Process Services
Shared Services
22
Shared Service Access
Business Process Services
Shared Services
23
Shared Service Access
Business Process Services
Shared Services
24
Connecting Applications is Not Enough The
Point-to-Point Integration Approach Inhibits
Agility
  • Point-to-Point
  • Brittle connections
  • Redundant logic
  • Doesnt scale
  • Lack of visibility
  • Business Impact
  • Delays responding to changing business needs

Service
Service
Service
Service
Service
Service
Service
Service
The Solution Service Integration
25
Enterprise Service BusSummary
Enterprise Service Bus
  • Embedded service management - optimized
    governance of all messaging
  • Rich composition environment - configuration
    driven, no coding approach
  • Optimized pluggable security secure any service
  • Adaptive service messaging - connect any service
  • Best-of-breed distributed run-time -
    reliability, availability, scalability, and
    performance

Service
Service
Service
Service
Service
Service
Service
Service
26
Benefits of SOA
  • Allows IT to deliver services faster and align
    closer with business
  • Use existing assets more effectively
  • Improved productivity, agility and speed for
    Business IT
  • Reduced development times and costs through
    re-use
  • Decreased integration costs and risks
  • Lower maintenance costs and higher data integrity
  • Allows business to respond quicker and deliver
    enhanced user experience
  • Enables new ways to relate to employees, partners
    and customers

27
Reference Architecture
Portal Tier
Portlet
Web App
Process Tier
Process Integration Process Management
Security Services Enterprise Security
Service Integration Enterprise Service Bus
Service Integration
Data Services Data Services Platform
Service Registry Service Registry
Data Service
Data Service
End-to-end Web Services Management
Data Warehouse
Tuxedo
.Net
J2EE
Packaged Apps
28
The BEA Stack (SOA Driven)
Business Process Management
Enterprise Service Bus
Application Integration
User Interaction
Enterprise Registry Repository
Data Services
LegacyApplications
CustomApplications
Database
LegacyApplications
PackagedApplications
Database
XML DataSource
PackagedApplications
29
The BEA Stack (The Products)
AquaLogic BPM Suite
AquaLogic Service Bus
WebLogic Integration
AquaLogic User Interaction
AquaLogic Enterprise RepositoryAquaLogic Service
Registry
AquaLogic DSP
LegacyApplications
CustomApplications
Database
LegacyApplications
PackagedApplications
Database
XML DataSource
PackagedApplications
30
Thank You
Write a Comment
User Comments (0)
About PowerShow.com