Embed Size (px)
Citation preview
Page 2
Page 2
1. What is SOA ?
2. SOA Strategy & Maturity Model
3. SOA Implementation Methods
4. SOA in e-Business Suite
Page 3
Page 3
1. What is SOA ?
2. SOA Strategy & Maturity Model
3. SOA Implementation Methods
4. SOA in e-Business Suite
Page 4
Page 4
230년 VS. 43년
230년 역사의 자동차와 43년의 역사의 IT 의 공통된 화두는 표준화를 통한 한번 개발을 통한공용화/재사용 성 강화 임 ( One Build, Many Use )
Dodge Neon 4 doors small sedan 4cyl 132HP, $13.000
Dodge Viper sports coupe 10cyl 500HP, $81.000
40% reuse
70% reuse
Chrysler PT Cruiser wagon 4cyl 154HP, $16.000
Page 5
Page 5
전통적인 IT VS SOA
SOA ( Service Oriented Architecture ) 는 IT 자원을 Web Service 기술을 이용하여 표준화를통한 재 사용성 강화 및 Flexibility 를 강화하기 위한 Architecture 의 Ideology 임
Service Oriented ArchitectureTraditional IT
• 기능추가/변경이힘들다• Tightly Coupled System
• 기능추가/변경이쉽다.• Loosely Coupled System• 표준커넥터를이용하여원
하는기기추가/변경작업이가능
오디오의표준인 RCA단자
Agility, Adaptability, Extensibility
Page 6
Page 6
What is SOA ?
Definition– SOA is a design paradigm based on best practices that facilitates
an integrated software infrastructureGoal
– To achieve loose coupling among interacting software assets– Enables reuse and sharing of IT infrastructure including legacy, Java,
.Net, and packaged applications & data sources– Abstracts complexity of existing assets and presents standards-based, business-o
riented interfaces to other applications
Service-oriented ArchitectureService-oriented ArchitectureTraditional Architecture Traditional Architecture
Functionality DrivenFunctionality Driven
Long development cyclesLong development cycles
Tightly CoupledTightly Coupled
Application SpecificApplication Specific
Designed to lastDesigned to last
Object OrientedObject Oriented
Process OrientedProcess Oriented
Iterative developmentIterative development
Loosely CoupledLoosely Coupled
HeterogeneousHeterogeneous
Designed for changeDesigned for change
Message OrientedMessage Oriented
Page 7
Page 7
SOA 의 기대 효과
SOA를 구축하면 기존 IT자원의 재사용을 통한 유연성과 민첩성을 강화하여 IT 환경 통합을 더손쉽고 빠르게 구축 할 수 있음.
소프트웨어의유연성과민첩성향상– 코드변경대신에프로세스모델을변경
생산성과재사용성향상– 기존비즈니스서비스의토대위에새로운기능
구축
소프트웨어수명증가를통한높은 ROI 실현– 기존서비스를이용할수있는재사용성
쉬운마이그레이션과좋은운영성– 잘정의된인터페이스와미리정해진상호운영성
코드보다비즈니스로직에집중할수있는개발환경
– 서비스(Interface) 중심의비즈니스로직구현가능
Page 8
Page 8
Service
What is a Service ?
Service is a software component of distinctive functional meaning that typically encapsulates a high-level business concept. It consists of several parts
Interface A-Operation 1-Operation 2-Operation 3
……
Interface B-Operation 1-Operation 2
……
Service Contract
Implementation
BusinessLogic
Data
Data
A service consists of both data and business logic along with interface andtheir descriptions
Source : Enterprise SOA, Prentice Hall Press
개발영역
서비스정의및도출영역
Page 9
Page 9
OO, CBD, Service
ServiceService
ComponentComponent ComponentComponent
ObjectObject ObjectObjectObjectObject
Coarse Grained
Fine Grained
Business Perspective
Technical Perspective
SOA = CBD + @– 서비스를 나누는 기준은 기술적인 관점이 아니라 비즈니스적인 관점에서 나눔
– UML Use Case Diagram. Function Decomposition Diagram
SOA = Modular + Distributed + Loosely Coupled
Page 10
Page 10
SOA 특징
서비스 인터페이스SOA 디자인에서는 컴포넌트 기능 구현을 위한설계는 부차적인 문제이고, 핵심적인 사항은 서비스 인터페이스 설계임. 즉, SOA는 근본적으로서비스 인터페이스들의 흐름과 이들의 관계에
관한 것임.
블랙 박스 접근 방식서비스 내부의 디자인이나 구현 내용을 모르더라도 찾고 사용하는데 충분한 정보를 갖추어야함. 즉, 블랙 박스적인 속성을 갖추어야 한다는
것임.
느슨한 연계 (Loose coupling) 서비스가 특정 서비스 사용자를 염두에 두고 디자인되지 않는 것을 말함.
Page 11
Page 11
SOA 방향
SOA 는 단순하게 Peer-to-Peer 방식에서 SOA를 기반으로 한 BPM으로 적용되고 있음.
Enterprise Layer
Process Layer
Intermediary Layer
Service Layer
Enterprise Layer
Intermediary Layer
Service Layer
Enterprise Layer
Service Layer
Source : Enterprise SOA ( Prentice Hall ) App App App
Service Service
Service
.Net G/W CICS G/W MQ
Service Service
Service
App App App
App App App .Net G/W CICS G/W MQ
Service Service
Service
Fundamental SOA
Networked SOA
Process Enabled SOA
Page 12
Page 12
SOA 적용 Image
Customer Service Billing Service Customer InteractiveService
ChannelService
CRMService
Service Portal
Customer Process Billing Process Customer InteractiveProcess
ChannelProcess
CRMProcess
Composition/Orchestration
Shared Service
Components & Legacy
Service 1 Service 2 Service 3 Service 4 Service 5 Service 6 Service 7 Service 8
Component Component Component Component Legacy Legacy Legacy
PCS 고객PCS 고객 Non-PCS 고객Non-PCS 고객 Wire 고객Wire 고객 SP/CPSP/CP
통신업계사례
Page 13
Page 13
1. What is SOA ?
2. SOA Strategy & Maturity Model
3. SOA Implementation Methods
4. SOA in e-Business Suite
Page 14
Page 14
SOA 를 바라보는 관점
SOA 에 대한 정의 및 관점에 따라 여러 가지로 해석될 수도 있으며 가장 포괄적인 해석은 재 사용성을 높이기위하여 표준화된 기술을 이용한 기업내의 IT자원을 서비스화 하는 총체적인 활동이라 할 수 있음.
이미지출처 : Naver
1) 쎅스폰을부는남자
2) 미녀의실루엣
SOA is….
1) EAI 를대체하는표준기술의Integration 기술
2) IT 자산의서비스화를통한재사용성강화의품질활동
3) IT를비즈니스관점으로의전환
4) Web Service 기술을통한표준기술적용
5) 웹의새로운표준
…관점에따라해석이다름…
Page 15
Page 15
전사 Architecture 관점의 SOA
SOA 는 단순한 표준 기술을(Web Service) 적용한 Service 적용이 아닌 전사 Architecture관점의 통합 및 표준 정의, 재 사용, 조합을 통한 IT Architecture Agility를 극대화 하는 것임.통합 Architecture Framework 각 Layer 별로추구하는방향
언제어디서나한번의 Log-In 을통해개인에게필요한모든기업정보에접근가능한환경
UI 표준/Web Style Guide/Template 적용등
프로세스지향형의모든단위업무가통합된시스템Service기반의 BPM 구현, BPP통합 Data 기반의 Business Prccess의 Service화
통합데이터모델을통한모든 Data가통합된 Single Source of Truth
Datahub개념의 Master/기준정보관리Data Access Layer의분리및독립
Grid Computing 기반의저비용고효율의 IT Infrastructure 구축
Infra Service, Utility Service
InformationAccess
Architecture
TechnicalArchitecture
BusinessProcesses
Architecture
EnterpriseData Architecture
Page 16
Page 16
Key Underlying SOA Enablers
대부분의 기업이 제품을 선정하고 표준을 정하면 SOA 를 구현할 수 있는 것으로 오해하고 있으며 진정한 SOA 는 전략수립부터 제품의 선정 및 구현, 관리 등의 일관된 체제를 필요로 함.
Technology Standards Delivery Operations
Information Organization Processes
Architecture Governance
Strategy
Experiment and Learn
Get Maximum Benefits
Key Underlying SOA Enablers
대부분의회사가 SOA 제품을도입했다고SOA 적용을했다고함. 역으로벤더도 SOA 제품을납품하였다고 SOA 사례라고발표
진정한 SOA 적용은전략수립부터제품의선정및적용그리고관련된체제,조직,프로세스확립을하여야완성이됨.
Page 17
Page 17
Enterprise Scope
Project Scope
SOAProjectDelivery
Best Practices
Planning
SOAAppl.Scope
Execution
Candidate SOA Projects
Value/ Benefits Assessment
• Org. Goals and Bus. Drivers• SOA Biz Case /ROI Considerations• SOA Project Selection
Physical Design
SOA Development
•SOA Ref. Architecture •Design Patterns•Dev. Best Practices
Biz Modeling / Service Discovery & Design
Solution Requirements
SOA Roadmap
Maturity Assessment & Improvement
• SOA Tech. Infrastructure• SOA Adoption Model• Service Portfolio Planning• Governance
SOA Success Strategy – Engagement Scopes
Think big, Start small : SOA 전략을 수립하여 순차적으로 ROI 산정이 용이한 영역부터 적용
Page 18
Page 18
The Roadmap to SOA
SOA Success Methodology
SOA 를도입하기위해서는적절한평가방법을이용하여 Maturity model을적용하여적절한Implementation 방안을제시하여야함.
1 2 3 4
ASSESS COMPARE VALIDATE PREPARE
Capability Matrix
Readiness Assessment
Maturity Model
Gap Analysis
Metrics and Assumptions
Business CaseAnalysis
Adoption Roadmap
Success Metrics
5
IMPLEMENT
Project Execution
Service & ProcessPortfolios
Page 19
Page 19
The Path to Level 5 SOA-Maturity Model
StrategicGoals
Tactical Plans
Level 1Opportunistic
Identify Simple “quick win” Projects
Build Services
Consume in Portal, BAM
Organize and Strategize
Create_customer, Messaging, Error
HandlingExamples
Level 2Tactical
Sell Business on SOA Benefits
IntegrateServices
Manage Services
Tactical SOAImplementations
Customer DataIntegration
Level 3Strategic
Business Process
Automation
EnterpriseArchitecture
Group DrivingSOA
Process AutomationAnd Improvement
With SOA
Integrated Work Order Management
Be a leader in the industry eco-system and provide/
consumerelevant
services. Enable the virtual
enterprise with business
insight, and real time information
access
Level 5
SOA isindustrialized
Strategic SOA, B2B, B2C, A2A
Deploy BAM + BPEL for
Measurement
Level 4Enterprise
SOA isQuantitatively
Managed
Monitor End Customer SLAs
Measurement&
Improvement
*Source: Accenture + Oracle + The Hartford
Page 20
Page 20
Level 1 – Opportunistic
Technology– Application Server Platforms– Development Tools with Web Services Support
Standards– WSDL, SOAP, XML– WSRP, JSR168
WarehouseManagement
Inventory
Portal
Example : Publish Inventory to Account Reps
Page 21
Page 21
Level 2 – Tactical
Technology– BPEL Process Orchestration– Enterprise Service Bus – Registry– Web Services Management & Security
Standards– BPEL, WSIF, JMS, JCA– UDDI– WS-Security
INTEGRATION FLOW
SiebelCRM
Oracle Financials
Packaged ApplicationsFulfillmentCenterCustomerService
Consumers Services
Web
Phone
Systems
BusinessPartners
Apply PoliciesSecurityMonitoringLoggingAuditing
1
1
Page 22
Page 22
Level 3 – Strategic
Technology– Business Process Modeling– Business Rules Engines– Data Hubs– Integrated Services
Environment– Metadata Management
Standards– BPMN, BPEL– Industry XML
submit
OrderJSF
CREATE
BPEL
?
ACTIVATION FLOW
BPEL
Promotion Management(Business Rules)?
Applications
Customer (DataHub)
Exception ManagementPortal – Order Hospital(Human Workflow)
Order Validation (EJB 3.0)
Applications
Customer (DataHub)
Exception ManagementPortal – Order Hospital(Human Workflow)
Order Validation (EJB 3.0)
Automated & Flexible Order Processing
Page 23
Page 23
Level 4 – Enterprise
Technology– Business Process Simulation– Business Activity Monitoring– Complex Event Processing– Metadata Management Systems– Grid
Standards– Service Component Architecture
(SCA)– WS-Addressing, WS-Eventing– WS-Trust, WS Secure
Conversations
BPEL
submit
OrderJSF
?
ACTIVATION FLOW
CREATE Applications
Customer (DataHub)
BPEL
Exception ManagementPortal – Order Hospital(Human Workflow)
Promotion Management(Business Rules)
Exception RateSLA Management
?
Order Validation (EJB 3.0)
Event-Driven Exception Management
Page 24
Page 24
Level 5 - Industrialized SOA Continuous Improvement & Innovation
Strategy– Enable Business Insight, Real-
time Information & Automation – Achieve Agility with Feedback
Architecture– Enable Smoother Migration to
SOAGovernance
– Enable Automation– Transition to Exception Handling
ProcessesOrganization
– Continue to Drive Innovation
Page 25
Page 25
SOA Maturity
•Enable the virtual enterprise with business insight, and real time information access
Deploy BAM + BPEL for Measurement
EnterpriseArchitecture Group
DrivingSOA
IntegrateServicesBuild Services
Tactical Plans
Over and above Enterprise
(SOA isindustrialized)
Enterprise(SOA is
QuantitativelyManaged)
Strategic(Process Automation
And ImprovementWith SOA)
Tactical(Tactical SOA
Implementations)
Opportunistic(Organize and
Strategize)Scope & Level
Be a leader in the industry eco-system
and provide/consume
relevant services.
Measurement& Improvement
Business Process Automation
Sell Business on SOA Benefits
Identify Simple “quick winStrategy Goals
•Enable Business Insight, Real-time Information & Automation •Achieve Agility with Feedback
•Business Process Simulation•Business Activity Monitoring•Complex Event Processing•Metadata Management Systems•Grid
•Business Process Modeling•Business Rules Engines•Data Hubs•Integrated Services Environment•Metadata Management
•BPEL Process Orchestration•Enterprise Service Bus •Registry•Web Services Management & Security
•Application Server Platforms•Development Tools with Web Services Support
Technology
Level 5Level 4Level 3Level 2Level 1
프로젝트에서는 Risk, Schedule, Budget등을고려하여달성가능한목표 Level 를설정및추진하여 Business Agility를향상
Page 26
Page 26
1. What is SOA ?
2. SOA Strategy & Maturity Model
3. SOA Implementation Methods
4. SOA in e-Business Suite
Page 27
Page 27
SOA Realization Process
Service Discovery
Service Specification
Service Acquisition (Implementation
Or 3rd Party)
Service Classification
Service Portfolio PlanningEnterprise Scope
Project Scope
Application Scope
Page 28
Page 28
Service Classification
서비스의 분류 체계는 기업 및 선정된 제품에 따라 적절하게 분류되어져야 하며 기업의 핵심이 되는 서비스에 대하여 정확한 개념으로 정리되어져야 함.
Functionality-based (what does the service provide)–Infrastructure services (ex. DNS lookup)–Data services (ex. federated query)–Business logic services (ex. fraud-check algorithm)–Utility services (ex. transformation or routing)–Information system services (ex. an ERP functionality)–Process control services (ex. an approval process)–UI services (ex. a pre-packaged portlet)
Usage-based (who typically uses the service)–High-level Business Services (ex. PO processing)–Supporting Business Services (ex. PO approval workflow)–High-level Technology Services (ex. User lookup)–Supporting Technology Services (ex. Logging)
Construction-based (how the service is put together)–Simple Services (ex. a web service provided OUB by email app.)–Wrapped Services (ex. a WS invoking invoicing in an ERP app.)–Composite Services (ex. a loan origination combining credit check and loan bids from multiple banks)
Invocation-based (how the service is accessed)–Synchronous/Asynchronous (ex. request/reply to specific service)–Event-based (ex. notifications for any interested party to consume)
Service Classification - Sample
Page 29
Page 29
Service Granularity
Service의 크기를 결정하는 것은 매우 중요함
Right-Sizing of services.
Considerations in service granularity:– Loose-Coupling– Abstraction– Manageability
• Too many low level services can lead to proliferation of inter-dependent services that are hard to manage.
– Business Value• Every service must provide additional value, and not merely
exist as an implementation detail.
Page 30
Page 30
SOA Implementation Workshop
1. WHY? 2. WHAT? 3. HOW?CONCRETE GOAL SETTING – BUSINESS-IT ALIGNMENT
SOLUTION SPECIFICATION SOLUTION REALIZATION
Business Goals(BG) & Knowledge
SOA Vision &Expertise
Discovery & Mapping
EBPs,KBRs
MAP –KBR vs.
BGs
KTRs MAP –KTRs vs.
KBRs
MAP –Req. vs.
SOA
Service Discovery
Functional & OperationalSpecifications
ProcessPortfolio
ServicePortfolio
Solution Spec.(Incl. a HLA)
Analysis & Logical Design(Design Best Practices)
Solution Schematics(At different levels of
detail)
Implementation Design(Product Best Practices)
Implement-ation details
DeploymentArchitecture
Page 31
Page 31
Service Discovery Methods
각 방법을 상황 별로 혼용하여 사용하는 전략이 필요 함.
특정비즈니스이벤트(예:계좌소멸,대출신청,등)의생명주기전반에걸쳐필요한개별이벤트를나열하고해당이벤트를처리하는있어서어떠한서비스가필요한지를발굴한다.이과정을모든핵심비즈니스이벤트에대해서반복한다.
Business Event Driven 분석방법은기업이만들어놓은서비스포트폴리오가충분한지를검증하는데도움을준다.
기존에존재하고있는서비스나시스템을평가하여기존서비스로등록기존서비스를조합하여새로운서비스를만들수있는가를분석“Business Service” catalog가완성될때까지반복
Bottom-up 분석은다른기법에더해거의항상유용하게쓰일수있는방법으로, 존재하고있는서비스에대한 Catalog를만듦으로써갭-분석(gap analysis)이가능하게한다.
비즈니스요구사항이필요한서비스를도출할때까지반복적으로분해(decomposed)하는방법
기존시스템을거의사용하지않는새로운응용프로그램개발프로젝트(greenfield project)나기업전반에 SOA를적용하는기획(enterprise-wide planning) 단계에적절함
이방법만사용할경우실제적용에있어서서비스의크기(Service Granularity) 문제에직면할수있음
In this approach, the lifecycle of a particular business event is followed
to discover what services are needed to process the event through its
lifecycle. The process is then iterated for each key business event.Business Event Driven
In this approach, the existing services and systems are evaluated to catalog the existing services. These services are analyzed to arrive at what services can be composed from these services. The process is iterated to finally arrive at the catalog of ‘Business Services’.Define Data Model Design CRUD Service = Assembly of CRUD
Intra-Application Service
Bottom Up
In this approach, the business requirements are decomposed iteratively to discover the services required.
Define App domain Model biz process Service = Process Activity
Inter-Domain Service
Top Down
Page 32
Page 32
Top-Down Domain Decomposition
RetailCustomer
BusinessDomain
OrderInformation
StoreInventory
ReverseLogistics
Services
GetStore
Inventory
GetBackroomInventory
ScrapInfo
Operations
비즈니스 요구사항이 필요한 서비스를 도출할 때까지 반복적으로 분해(decomposed)하는 방법으로 기업 전반에 SOA를 적용하는 기획(enterprise-wide planning) 단계에 적절함
Page 33
Page 33
Bottom Up Analysis
기존에 존재하고 있는 서비스나 시스템을 평가하여 기존 서비스로 등록 하거나 기존 서비스를조합하여 새로운 서비스를 만들 수 있는가를 분석 하는 방법.
Page 34
Page 34
Business Process Tracing
특정 비즈니스 이벤트(예:계좌생성, 대출신청,등)의 Lifecycle 전반에 걸쳐 필요한 개별 내외부이벤트를 나열하고 해당 이벤트를 처리하는 있어서 어떠한 서비스가 필요한지를 발굴한다.
Page 35
Page 35
Service Discovery Method-Summary
○○○○○○-Departmental Project
○○○○○○○Increase Re-Use
○○○○○-Re-Use Existing
○○○○○Enterprise Wide
--○○○Green Field
Business Event DrivenBottom UpTop DownProject Type/Scope
Applicability : ○○○ High , ○○ Moderate , ○ Low , - None
SOA Implementation 에서의핵심은 Service를어떻게발견하고 Service의크기를(Granularity) 나누는것에달려있음
Page 36
Page 36
Incrementally growing size and scope of SOA
ORB, TPM, ESB, MOM, IBS
ORB, TP, ESB, MOMProgr. IS, ESBProgr. IS, WS ESBSOA Backplane
EnterpriseBusiness UnitInter-AppSingle AppScope
> 100< 100< 20< 10# of Service Developers
> 1,000,000< 1,000,000< 100,000< 10,000# of Service calls/Day
> 100< 50< 25< 5# of Service Consumers
> 1,000< 500< 100< 25# of Published Service
Extra LargeLargeMediumSmall
Experimental Mainstream Leading Edge
Source : Gartner
현재 ROI 혹은검증된 Service Size에대한것은없음. 그러므로기업의적용범위및내용에따라적절한목표를설정하여진행하는것이적합함.
Page 37
Page 37
Iteration & MGPP
SOA 구현 Project에서는 6Sigma의 NPI (New Product Initiative)의 MGPP (Multi Generation Product process) 방법처럼 여러 차례에 걸쳐 완성된 시스템을 구축하는 Iteration 방법이절대적으로 필요함.
다세대제품개발프로세스
지속적인시장관찰, 평가와고객 Needs 분석
제품에대한요구정의
제품 Concept개발
제품과공정설계
Field Test 및고객평가
신제품출시
피드백과
평가
제품과공정설계
Field Test 및고객평가
신제품출시
피드백과평가
제품과공정설계
Field Test 및고객평가
신제품출시
InceptionInception ElaborationElaboration ConstructionConstruction TransitionTransition ProductionProduction
LA IOC SPLO SORR RR
DD
CC
TT
RR
DD
CC
TT
RR
DD
CC
TT
RR
DD
CC
TT
RR
DD
CC
TT
RR
DD
CC
TT
RR
DD
CC
TT
time
SS
MG
PP
Itera
tion
Met
hods
Page 38
Page 38
Oracle SOA 적용 방법론
Oracle의 OUM (Oracle Unified Methods)는 UP (Unified Process) 를 근간으로 Iteration 한 방법으로 Service를 발굴 및 적용이 가능 하며 방법론은 제품의 역량 못지 않게 중요한 요소임.
Page 39
Page 39
Getting Ready for SOA : R&R
SOA 를 구현하기 위해서는 기존의 R&R과는 다른 개념의 R&R이 필요 함.
•Identify & Design Common component & Design Standardization Team
•Best support and establish the SOA in the enterprise•Guide service define & service development
SOA Team
•End-To-End testing and validationQA Team
Senior•Identify Service / Define size of service granularity•Identify message In/Out / Define user requirement
Business Analyst
CBD 개발의 Role 참조( UI 개발자 , Data Handling 개발자 , Biz Logic 개발자 )
•Implement Service / Develop consumer application•Change Management
Development Team
SOA Product Admin & Implementation
•Support Service Developer / Implementation SOA Backplane•Management of Service Registry
Integration Team
ChiefData/Application/Technology/Service
•Update Architecture Blueprint to enable SOA•Define SOA Pattern, Standards and Guideline•Setup and manage the service definition process•Select proper technology and tools
Architecture Team
DescResponsibilityRole
Page 40
Page 40
SOA Do : Applying SOA
Simple internal integration
Rich internal integration
Multi channel application
Business process automation
Multi-interaction channel (multi CRM)
Portal (UI) integration and simplification - compare to client/server
Core business flexibility
Business visibility and information access
Business process outsourcing.
다음의영역에 SOA를적용하면 ROI 및효과가큼
Page 41
Page 41
SOA Don’t : Anti Patterns
Do not wrap every interface (API) into a service
Do not assume web service development as the same as SOA
Do not use proprietary technology for SOA
Do not attempt SOA without involving the users
Do not blindly apply SOA to every project
SOA 는모든분야에맹목적으로적용을금하며 Service 도출기준에의한부분적인적용이가장권장됨
Page 42
Page 42
SOA True & Falsehood
SOA 는 전혀 새로운 개념이 아님
SOA 제품 보다는 제품+컨설팅능력+적용방안을 고민해야 함.
표준 Interface 규약을 정한다고 모든 Apps를 바로 적용 가능한 것은 아님
SOA 는 Layer의 증가로 성능의 문제를 야기 할 수 있음
전통적인 개념으로 SOA 를 접근한다면 아무런 Benefit을 얻을 수 없음
모든 분야 전 영역을 SOA 로 한다는 생각은 금물
새로운 IT 기술 보다는 좋은 Project Management가 더욱 더 좋은 시스템을 만들어 냄
( Communication / 변화관리 / Skill전환 / 조직 / Vision / Top의 지원 등 )
Page 43
Page 43
1. What is SOA ?
2. SOA Strategy & Maturity Model
3. SOA Implementation Methods
4. SOA in e-Business Suite
Page 44
Page 44
SOA & e-Business Suite
EBS is becoming a SOBA Suite– New Applications Developed Using Framework– Existing Interfaces Wrapped as Services– SOA Infrastructure Provided By Oracle Application Server
SOBA Facilities to Simplify Integration– Broader range of core services being exposed– Integration (Service) Repository – Makes Service Discovery and Implementation Easier– Delivered with EBS 11.5.10
EBS SOA can be Orchestrated– OAS10g For Service Orchestration– Coordinated Private & Public Business Flows– Plans for Business Flows (eg. SCM Gateway)– Canonical Data Transformations (eg. Data Hub Model)
Page 45
Page 45
How Does the E-Business Suite Help Make Integration Simple?
Integration RepositoryIntegration Repository•• Comprehensive repository of interfaces and Integration pointsComprehensive repository of interfaces and Integration points
Service Oriented ArchitectureService Oriented Architecture•• Web Services deployed from the Integration Repository Web Services deployed from the Integration Repository
Business Events Business Events •• Preconfigured Integration points Preconfigured Integration points
PrePre--Built Standards based MessagesBuilt Standards based Messages•• OAG, RossettaNet, HL7, EDIOAG, RossettaNet, HL7, EDI……
Four Simple Approaches
Page 46
Page 46
Integration Repository
EBS 내부의 모든 Service를 Catalog 화 하여 Web Service 를 지원 하는 통합 Repository제공
Catalog of all E-Business Suite Interfaces-Business Events-B2B Protocols-Application Programming Interfaces (API’s)-Legacy Integration Technologies
Catalog of every E-Business Interfaces that a Customer may wish to call or expose
-All Interface Type-All Documents
Unified Repository from which ALL E-Business Suite Web Services are exposed
Page 47
Page 47
SOA in EBS ( Web Services deployed from the Integration Repository )
EBS 내의 모든 서비스는 Integration Repository 에 정의되어 있으며 Service Bean형태로Framework, 외부, BPEL 등 에서 즉시 사용이 가능 함.
integration RepositoryClient
PL/SQL ProcedureJava ClassesEDI MessagesInterface TablesConcurrent ProgramsWorkflow Processes
XML Gateway Messages
Java Service Beans
OracleApplication
Server
Web Services
WSDL
SOAPEngine
HTTP ServerB
PE
L Process M
anager
Page 48
Page 48
SOA in EBS ( BPEL Process Manager )
모든 Service 는 BPEL/ESB 에서 Web Service 형태로 호출이 가능하며 이를 지원하기 위한EBS Adapter 를 제공 함.
BPELBPELProcess MgrProcess Mgr
GG--Log LogisticsLog Logistics
AADDAAPPTTEERR
OracleOracleFinancialFinancial
WSDLWSDL
Application ServerApplication ServerService BusService Bus
People &People &JDEJDE
WWSSDDLL
Siebel CRMSiebel CRM Retek RetailRetek RetailEEBBSS
AADDAAPPTTEERR
EEBBSS
AADDAAPPTTEERR
Page 49
Page 49
BES ( Business Event System )
EBS 내에는 약 1000개의 Business Event 가 정의 되어 있으며 Pre-built된 Event 를 통하여Service 호출 및 외부 Message 전달이 가능하며 서비스 호출/작동의 메커니즘을 제공 함.
ApplicationApplication
WorkflowWorkflow
BusinessBusinessEvent Event
BusinessBusinessLogicLogic
IntegrationIntegration(XML or WS) (XML or WS)
Act
ions
Act
ions
RaiseLocal Events
ListenExternal Events
EventDispatcher
Action(Java/PLSQL)
WorkflowProcess
XML on JMS
Matching Event Subscription
Application
JMS Queue
Out-Bound
In-Bound
Oracle EBS Legacy 시스템
Event-driven business processes allows you to design & deploy, or change flows quickly
Each Business Event represents a ready to use Integration point
~900 Outbound Integration points
~900 Inbound Integration points
Page 50
Page 50
PrePre--Built Standards based MessagesBuilt Standards based MessagesApplication간의 표준 호환을 제정하기 위한 표준단체인 OAG 및 Non-OAG 단체의 표준의 근거한 Application Integration 규약을 Pre-Built 제공하여
PKG Application간의 통합을 쉽게 구현 할 수 있음.– OAG / RossettaNet / HL7 / EDI / UCCnet …
SyncPO SupplierItemUOMGroupFieldExchngrateCOAPlanSchdShipSchdProdOrderInventorySalesOrder
ShowShipmentDeliverySalesOrderPmtErrorPmtAdviceRequisitionPlanSchd
UpdateDelivery
ConfirmBOD
CreateProdOrderRequisition
ProcessInvoicePaymentPO
AcknowledgePO
AddPORequisition
CancelPORequisition
ChangePOProdOrderRequisition
ProprietaryLease BookingLease QuoteLease RestructureLoan BookingLoan Restructure
US Dept of EducationFinancial Aid (Grant/Loan)
PESCDegree Audit
SEVISStudentsTranscripts
Rosettanet3A43A6
IFXBank Statements
30+ Non-OAG Implementations
150+ OAGIS Implementations
Page 51
Page 51
Oracle AcquiresProfit Logic
Oracle AcquiresPeopleSoft
Oracle AcquiresOblix
Oracle AcquiresRetek
Oracle AcquiresTripleHop
Oracle AcquiresG-Log
Oracle ‘announces’Siebel
Oracle Acquires stake ini-Flex
Oracle AcquiresContext Media
Oracle AcquiresTimesTen
PeopleSoft : Jan.2005Oblix : March.2005Retek : April.2005
TripleHop : June.2005TimesTen : June.2005
Innobase : 2005ProfitLogic : July.2005
ContextMedia : July.2005iFlex : August.2005
G-Log : September.2005Thor : November.2005
OctetString : November.2005TempoSoft : December.2005
Siebel : January.2006Hotsip :
Portal Software : May.2006
Committed to the richest set ofApplication services
SOA & Oracle
오라클은 제품이 아닌 생존 전략 및 전사적인 제품 통합의 비전으로 SOA 를 지향하고 있음.
Page 52
Page 52
Q & A
![Redefining Business Ownership. [2]CONFIDENTIAL Insert Your Picture Here Insert your Picture Here Insert Your Picture Here You must have Microsoft Powerpoint](https://img.pdfslide.tips/doc/110x75/56649e0e5503460f94af8f27/redefining-business-ownership-2confidential-insert-your-picture-here-insert.jpg)
