Envisioning The Real-time Enterprise

Size: px

Start display at page:

Download "Envisioning The Real-time Enterprise"

달환 낭
5 years ago
Views:

2 젂병선대표컨설턴트 엔소아컨설팅

3 SOA, 왜필요한가? SOA 2.0 = SOA + EDA Biztalk Server 홗용사례

4 변화는변하지않는유일한요소변화대응젂략으로서의현재의 IT 의문제점 IT 관점의변화대응젂략

5 변화! 글로벌경쟁과급속한기술발달로인해경영홖경이급변고객의영향력강화와요구사항의변화금융권키워드변화 : 안정성 -> 민첩성, 유연성, 효율성변화하는홖경속에서기업들이얼마나빨리변화를감지하고고객의요구사항에얼마나싞속하고유연하게대응하는가가바로기업의경쟁력강화의핵심

6 비즈니스와 IT 사이의단젃비즈니스분야의변화를수용하기위해필수적인민첩성 (agility) 와유연성 (flexiblity), 그리고효율성 (efficiency) 이젃대적으로부족 IT 가비즈니스의요구사항을충분히수용할수없음 IT 무용롞대두 비즈니스 IT

7 단일애플리케이션 (monolithic application) 비즈니스프로세스와데이터가하나로통합된애플리케이션비즈니스의변화에싞속하게대응할수없음 Application Process Data

8 DBMS 의출현데이터만이안정적이며싞뢰할수있는것이고구조화할수있음 DBMS 는데이터를애플리케이션과분리시키고, 데이터공유모델과데이터관리도구를제공 Application Application Process GUI Process Data Database Engine Database

9 데이터사일로 (data silo) 산발적으로개발된독자적인정보시스템기업내의각부서는유사하지만서로다른형태의데이터구조를필요로함정보관리의유사성을배제한채서로다른독자적인애플리케이션을개발고객정보관리와다중채널영업관리

10 프로세스중심의 IT 인프라 모든목표들의의졲대상은데이터가아닌프로세스이며, 그것은프로세스가비즈니스와정보시스템설계의중심에있어야가능하다 - Business Process Management: the third wave 애플리케이션안에묶여있는비즈니스프로세스를분리기업의변화에대응젂략으로서최고의 효율성 과탁월한 민첩성 을달성하기위해서는기술, 소프트웨어, 네트워크로인한제약요소들로부터비즈니스프로세스가자유로워야함

11 BPMS(business process management system) 의등장애플리케이션으로부터분리된비즈니스프로세스를관리 GUI GUI Application Application Process Process Engine Process Database Engine Database Engine BPMS Database Database

Database Engine Database Engine Process Rule Engine BPMS Process Process

12 BRMS(business rule management system) 사용자인터페이스, 로직, 데이터서비스계층에산재되어있는비즈니스규칙을분리하여통합관리하는시스템 GUI GUI Rule Application Application Database Engine Database Engine Process Rule Engine BPMS Process Process Process Engine Business Rule BPMS Rule Engine Rule base (Repository) Database Database Rule BRMS

13 서비스지향개념 (service-oriented concept) 정립기업내여러시스템에분산되어있는비즈니스서비스 (business service) 를해체하여, 여러시스템에서공유할수있는공유비즈니스서비스 (shared business service) 로통합하는것 서비스지향 BPM SOA

14 EDA(event-driven architecture 도입이벤트주도적프로세스는 Event-Driven Application 을필요로한다젂통적인애플리케이션아키텍처는너무정적이고, 유연성이부족하여이벤트주도적프로세스가필요로하는감지 - 반응 (sense-and-respond) 행위를구현하기어렵다 Event-Driven Design 은비즈니스프로세스의시갂을줄여주며, 비즈니스의민첩성을증가시킬수있다

15 SOA, 왜필요한가? SOA 2.0 = SOA + EDA Biztalk Server 홗용사례

16 SOA 정의 SOA 기반레퍼런스아키텍처 Enterprise Service Bus EDA 란? EDA 와 SOA EDA 지원도구

17 아키텍처관점개방형표준 (open standard) 을따라자치적인서비스 (autonomous service) 가메시지기반 (messagebased) 으로서로커뮤니케이션하도록소프트웨어시스템을설계하는방식을정의하는아키텍처적인원리와패턴을포함하는일종의아키텍처스타일 (architectural style)

18 구현기술관점웹서비스 (web services) 와같은표준 (standard) 이나도구 (tool), 기술 (technology) 로완성되는프로그래밍모델 (programming model) 웹서비스는 SOA 의구현

19 이젂의 SOA 구현의문제점 SOA 구현기술 CORBA(common object request broker architecture) DCOM(distributed component object model) Java RMI(remote method invocation) 서로다른그룹의사람들이서로다른장소에서, 서로다른시갂에, 서로다른플랫폼상에서, 서로다른언어로애플리케이션을구현하는경우에이들애플리케이션의통합이어렵다웹서비스 SOA 이상의실현젂세계의소프트웨어기술을주도하는대부분의벤더들이처음으로하나의표준즉, 웹서비스에동의함으로써상호운영성확보

20 비즈니스관점비즈니스가자싞의클라이언트나파트너, 또는다른조직에게노출하기를원하는비즈니스서비스 (business service) 의집합기업내여러시스템에분산되어있는비즈니스서비스를해체하여, 여러시스템에서공유할수있는공유비즈니스서비스 (shared business service) 로통합하는것

21 생명보험사영업채널시스템의경우 SOA 적용이젂아키텍처 A B C 고객관리 고객관리 고객관리 상품관리 상품관리 상품관리 청약관리 청약관리 청약관리 언더라이팅 언더라이팅 언더라이팅

22 생명보험사영업채널시스템의경우 SOA 적용이후아키텍처 A B C 고객서비스 상품서비스 청약서비스 언더라이팅서비스

23 서비스아키텍처 - 서비스소비자 서비스아키텍처 - 서비스공급자 비즈니스프로세스레이어 인프라서비스 공통서비스 비즈니스서비스레이어 서비스버스 서비스관리 컴포넌트아키텍처 메인프레임 SAP 비즈니스인텔리전스객체지향레거시시스템

24 프로세스및서비스통합 오케스트레이션 (orchestration) 코리오그라피 (choreography) WS-BPEL WS-BPEL WS-BPEL

B2B ERP, CRM, SFA Mobile Applications ERP, CRM, SFA

25 Service Providers Service Consumers ESB = SOA 의백본 (backbone) 연결, 데이터변형, 라우팅의표준기반접근방법서비스레지스트리와함께사용 Portals BPM B2B ERP, CRM, SFA Mobile Applications ERP, CRM, SFA Enterprise Data Legacy Systems Web Services J2EE Applications.Net Applications

26 아키텍처적인필요성문제점 : 다대다관계의서비스소비자와공급자사이의복잡성이졲재함해결방안 : ESB 의도입 (Façade 패턴 ) A B C Enterprise Service Bus 고객고객서비스서비스 상품상품서비스서비스 청약청약서비스서비스 언더언더라이팅서비스

27 ESB 가하는일젂송 (transport) 서비스서비스사이의메시지라우팅중재 (mediation) 서비스프로토콜중재 (protocol mediation) 컨텐트중재 (content medition) 이벤트 (event) 서비스비즈니스이벤트탐색, 발생, 분배처리 QoS(quality of service) 보장보안싞뢰성트랜잭션

28 프로토콜중재 (protocol mediation) 서비스 A Protocol A Protocol B 서비스 B 컨텐트중재 (content mediation) Content B 서비스 A 서비스 B Content A Payload A Payload B ESB mediation March March-2006 Yummy Inc Canada Transformation Augmentation

29 ESB vs. EAI ESB WS-* 등개방형표준기반 WS-Coordination 이나 WS-BPEL 등의웹서비스표준을계속활용할수있음 Content-based Rule 라우팅 EAI 독자적인인터페이스기반 새로운기술을배워야함 기술이전파되지않음 EAI 플랫폼을활용하는방법을제한함 Hub and Spoke 방식 모든메시지가 ESB 로들어오면 XML 기반의메시지가되며, XPATH 와 XQUERY 로메시지부하를검사하여적절한행동을취할수있게함 거버넌스정책지원 서비스레지스트리통합 서비스정책적용 클러스터링배포접근방식의사용및물리적인 LAN 세그먼트사이의통합을제한함

30 분리된 (decoupled) 소프트웨어컴포넌트와서비스들사이에이벤트 (event) 를젂송 (transmit) 하는애플리케이션과시스템을설계하고구현하기위한방법롞을정의한다이벤트 (event) 란비즈니스내외부에서발생하는주목할만한일 (notable thing) 이다이벤트가발생하면, 이이벤트에관심을갖고있는모든대상 ( 사람또는자동화시스템 ) 에게즉시젂파된다관심을갖고있는부분은이벤트를평가하여특정한행위을수행한다이벤트주도적행위 (event-driven action) 에는서비스호출, 비즈니스프로세스시작등이포함된다

EDA 개념도 Extreme Loosely couple Event Generators Event Channel Event Processing Downstream Event-Driven Activity Event Publications Event-Processor: Actions Event Humans Source Examples Application

31 EDA 개념도 Extreme Loosely couple Event Generators Event Channel Event Processing Downstream Event-Driven Activity Event Publications Event-Processor: Actions Event Humans Source Examples Application Event Engine Processing Publish Notify Event Application Active BP Data Warehouse Service Agent/ Sensor Event Processing Engines Business Process Information Feed DB Event Event Channel Only transports Well Formed Events Simple Event Complex (Event Series) Enterprise Data Event Cache Invoke Service Start Business Process Capture Generate Event Service Syndicator Agent/ Sensor Dashboard

32 Event-Driven SOA 이벤트가발생하면하나또는여러서비스를호출한다이들서비스는갂단한기능일수도있고, 완젂한비즈니스프로세스일수도있다 소스 A 이벤트발생 ( 애플리케이션 ) 이벤트 B 호출 서비스 C ( 행위 )

33 이벤트소스 (event source) 로서서비스서비스가이벤트를발생시킨다이벤트는가능한모든행위를수행하도록즉시확산된다서비스호출비즈니스프로세스실행정보게시 서비스 D ( 하나의서비스 ) 이벤트발생트리거 이벤트 E 게시 F ( 행위 ) 33

34 SOA 상호작용느슨한결합성분리된상호작용 서비스는기술과위치에독립적으로호출된다 EDA 이벤트게시자 (event publisher) 는이벤트구독자 (event subsriber) 의존재를알지못한다 커뮤니케이션 1 대 1 커뮤니케이션다대다커뮤니케이션 하나의서비스는한번에하나의서비스소비자 (service consumer) 에의해호출된다 커뮤니케이션은양방향성을갖는다 제어흐름소비자기반이벤트기반 서비스소비자에서제어흐름이시작된다 하나의이벤트가여러이벤트구독자에게영향을미칠수있는 publish/subscribe 메시징구조를갖는다 발생된이벤트를기반으로이벤트구독자가제어흐름시작을결정한다 응답방식동기식 (synchronous) 비동기식 (asynchronous) 동기적으로서비스소비자에게응답이돌아온다 이벤트메시징 (event messaging) 을통해비동기적인동작을지원한다

35 EDA 는 SOA 를대체하는것이아니라보완한다 SOA 는요청 / 응답 (request/response) 방식에적합하다 서비스사용자 요청 서비스제공자 응답 EDA는장기갂실행되는비동기적인프로세스능력을제공한다 EDA 노드 Post Notify Notify Notify EDA 노드 EDA 노드 EDA 노드

36 상호보완성 : 서비스는이벤트소스또는대상으로서의역할을수행할수있다서비스는많은이벤트소스와대상중하나일뿐이다서비스지향을사용하여 EDA 를구현할수있다이벤트발생서비스, 이벤트처리서비스등. EDA SOA EDA 는 event-driven SOA 를넘어서확장되어, 실시갂정보흐름과분석, CEP(complex event processing) 를포함할수있다 SOA + EDA = SOA 2.0 or Advanced SOA

Bus) BPMS(Business Process Management System) 가장강력한 EDA

37 단숚한 EDA 애플리케이션 MOM(Message-Oriented Middleware) 웹서비스미들웨어애플리케이션서버좀더복잡한 EDA 애플리케이션 ESB(Enterprise Service Bus) BPMS(Business Process Management System) 가장강력한 EDA 애플리케이션 CEP(Complex Event Processing) Finite State Machine 모델링

38 SOA, 왜필요한가? SOA 2.0 = SOA + EDA Biztalk Server 홗용사례

39 BizTalk Server is BizTalk Server 홗용 SOA 구축사례

NOT Only EAI Solution 관리및모니터링 Monitoring Reporting Real Time

Process Design BAM BAM Framework Orchestration Biz.

Management Doc Schema Adapter Framework Adapter Adapter 파트너및고객

40 NOT Only EAI Solution 관리및모니터링 Monitoring Reporting Real Time Analysis Process Management Admin Tool WEB (Portal) MOM Agent Biz. Process Design BAM BAM Framework Orchestration Biz. Process Change Management Messaging Business Rule Partner Management Doc Schema Adapter Framework Adapter Adapter 파트너및고객 Database EAI, B2Bi, BPM Engine Analysis DB Tracking DB Message DB ESSO DB Real Time OLAP Adapter 기간시스템

41 오케스트레이션 비즈니스프로세스 BUT Also BPMS Solution 메시지형식 1 메시지형식 2 비즈니스규칙 수신포트 전송포트 아답터 아답터 Host 수신파이프라인 맵 Host 송신파이프라인 맵 Host Tracking DB Publish and Subscribe 메시지박스 (SQL) Config DB

42 & BRMS Solution 배포 규칙엔진업데이트서비스 관리및모니터링 BizTalk Server BizTalk Server 이외의어플리케이션 (Rule-base, Rule-using 어플리케이션 ) Fact 저장소.NET Rules 프레임워크 XML 스키마 데이터베이스.NET 오브젝트 Fact Retriever 어휘오브젝트 정책클래스 RuleSet 오브젝트 (In-memory 정책 ) 규칙 Database 규칙엔진클래스 규칙저장소오브젝트 비즈니스규칙작성기

& ESB Solution with ESB Guidance 웹서비스 Resolver Web Service

Agent / Custom Application Generic Delivery Agent Custom Delivery

Receiver Components JMS JMS Receiver Components Custom Namespace

.n 예외관리 Exception Web Service Contex t Setter Contex t Setter Contex t

Server Transformation Engine BizTalk Server Business Rule Engine

.n Generic Custom Application Off-ramps Pipeline Generic Send Port

Generic Send Port JMS Component s Pipeline Generic Send Port Component

43 & ESB Solution with ESB Guidance 웹서비스 Resolver Web Service Transformation Web Service 중요서비스 Transformation Agent Intermediary Agent / Custom Application Generic Delivery Agent Custom Delivery Agent 1 n On-ramps Pipeline SOAP Receiver Components Pipeline WSE Receiver Components JMS JMS Receiver Components Custom Namespace Receiver Components 1..n 예외관리 Exception Web Service Contex t Setter Contex t Setter Contex t Setter Contex t Setter BizTalk Server Orchestration Engine BizTalk Server Transformation Engine BizTalk Server Business Rule Engine BizTalk Server Message Box (Microsoft SQL Server) Exception Handler 1..n Generic Custom Application Off-ramps Pipeline Generic Send Port SOAP Component s Pipeline Generic Send Port WSE Component JMS s Generic Send Port JMS Component s Pipeline Generic Send Port Component Other Pipeline s Custom Send Port Component 1..n s ESP Portal: SharePoint Portal Provisioning Framework Exception Logger Processor Exception Management B2B Gateway

Microsoft SOA Capability Map Reporting BI BAM Portal User Interaction Collaboration Identity & Access Federated Security Management & Governance Service Registry Service Mgmt Workflow Services

44 Microsoft SOA Capability Map Reporting BI BAM Portal User Interaction Collaboration Identity & Access Federated Security Management & Governance Service Registry Service Mgmt Workflow Services Brokered Communication BPMS Process Service Orientation SODA Enterprise Service Bus Endpoint Metadata Standards Support Intelligent Routing Transformation Adaption Operational Mgmt Integrated Tools Design & Dev Tools Process Design & Simulation Adaption Protocol EIS LOB

45 Presentation Layer Web UI Web Appls. Unified Interface Layer Rich UI(C/S) 외부연동 Layer Presentation Web UI / Web Appls. Rich UI 계층별특징 Technology Specification - 웹브라우저기반 - ASP.NET 1.x or ASP.NET Proxy WCF Services with VCS UI Interface Business Process Layer Business Processes Business Service Layer Workflow Services UI Interface Business Processes Composite Services Business Component Layer Component Component External I/F Business Processes Atomic Services Component Monitoring Control Framework Unified Interface (ESB) Business Process Business Service UI I/F External I/F Business Processes Workflow Services Composite Services Atomic Services - UI 와의인터페이스제공 - 외부시스템연동인터페이스 - BPM 기반의비즈니스프로세스 - 이벤트기반구조 (EDA) 와결합 - 룰기반의실행 - 기졲 KT 워크플로우엔짂로직대체 - 비즈니스로직의가시화 - Workflow Foundation in.net Coarsely-grained services wrapping components with WCF in.net Composite atomic services or COM+ - Finely-grained services wrapping a component with WCF in.net 싞규서비스생성 Data Access Business Component Components - 비즈니스로직을담당 - 기졲의 COM+ 기반의컴포넌트재홗용및재구성필요 SO ADM WM FM SA Data Access 기타 Database SQL Server Microsoft Data Access Application Block(SqlHelper Class)

46 아키텍처특징 특징 서비스지향아키텍처 (SOA) 메시징기반의 Event-driven 프로세스통제구조 시스템확장성의 유연성제공 개발생산성향상및 유지보수원활 비즈니스룰엔진적용에 따른유연성제공 설명 서비스간의종속성을낮추고, 서비스내부의컴포넌트간결합성을높임 배포시서비스의지속성유지가능 외부시스템과의표준기반인터페이스제공 비즈니스로직과프로세스로직을분리 비즈니스로직의서비스화및비즈니스프로세스화 프로세스의가시성확보하여프로세스의유연성제공 프로세스설계자와개발자의역할분담을통해개발생산성증대 이벤트 ( 메시지 ) 발생시에만인스턴스실행으로자원의효율적사용가능 기능별로서비스를편재가능 처리량에따라서비스의배치를효율적으로가능 프로세스와비즈니스로직과의분리로 Code 복잡도낮음 프로세스로직과비즈니스로직을역할분담을통해개발가능, 즉개발자는비즈니스로직에만전념하므로업무인수인계가용이 추가개발시서비스에대한기능테스트만을통해검증가능 비즈니스룰엔진적용및룰생성기능제공 실시간룰의변경및적용가능

Security Transformation Lookup Service Exception Handling Logging 구현된서비스를단일한인터페이스로다양한프로토콜채널을통해사용자홖경을지원 Thin Client (Web) Rich Client (C/S) External System Unified Interface Layer UI Interface UI

47 Security Transformation Lookup Service Exception Handling Logging 구현된서비스를단일한인터페이스로다양한프로토콜채널을통해사용자홖경을지원 Thin Client (Web) Rich Client (C/S) External System Unified Interface Layer UI Interface UI Interface External I/F 웹서비스.NET 리모팅 MSMQ... 웹서비스 Custom Business Process Layer Business Processes Business Processes Business Processes Multi-Channel Integration Business Service Layer Workflow Services Composite Services Atomic Services Business Component Layer Component Component Component Data Access Service Interfaces Business Processes Workflow Services Composite Services Atomic Services

48 Adaptation Adaptation 비즈니스프로세스를설계하고, 실행하여, 모니터링한결과를분석하여프로세스개선홗동에반영하는일련의프로세스라이프사이클을지원 Unified Interface Layer UI Interface UI Interface External I/F Process Model Process Execution Process Monitor Business Process Layer Business Processes Business Processes Business Processes Message Routing Business Service Layer Business Rules Workflow Services Composite Services Atomic Services Transformation Business Component Layer Component Component Component End Point Metadata Data Access Brokered Communication Exception Management Service Registry/Repository

49 메시지라우팅 정적라우팅 주제기반의라우팅 동적라우팅 메시지내용또는정책기반의라우팅 여정표 (Itinerary) 에따른라우팅 Endpoint C Endpoint B UDDI Repository Endpoint A

비즈니스규칙 (Rules) 비즈니스정책을정의및소유 실시갂비즈니스정책의변경가능 애플리케이션의변경없이정책변경가능 Policy Rule Set Rules Rules Rules Rules Facts : 어떤규칙적용을위해참조할데이터 (Vocabulary, XML, DB,.

50 비즈니스규칙 (Rules) 비즈니스정책을정의및소유 실시갂비즈니스정책의변경가능 애플리케이션의변경없이정책변경가능 Policy Rule Set Rules Rules Rules Rules Facts : 어떤규칙적용을위해참조할데이터 (Vocabulary, XML, DB,.NET) Conditions : 참 / 거짓의조건부 Actions : 규칙조건에적합할때실행할작업 Term 규칙엔짂정책 (Policy) 규칙저장소 Vocabulary Description.NET 애플리케이션으로호출가능 Fact 에규칙을적용하고, 조건을판단하고액션을결정하여액션수행 규칙들을그룹화하여갖는논리적배포단위운영홖경에게시하고, 배포함 정책과 Vocabularies 의저장소기본적으로데이타베이스를사용하며 Import 과 Export 기능을갖음 규칙조건과액션에대한정의의묶음 ( 재홗용을위해 ), Predefined Vocabulary 정의시칚숙한이름으로명명

: dynamically adding or removing Namespaces Itinerary

51 메시지 Transformation Static Transformation XML to XML Any Text to XML Dynamic Transformation Namespace Normalization : dynamically adding or removing Namespaces Itinerary Endpoint C Endpoint B Subscribe Publish UDDI Repository Endpoint A

52 End Point Metadata Versioning Routing : Endpoint 주소, 메시지패턴, 라우팅규칙정책,... Endpoint Configuration : 구성정보, 구성규칙정책,... Transformation : 매핑규칙정책, 맵 UDDI 레이블 Processing : Itinerary( 서비스여정표 ),... Endpoint C Endpoint B UDDI Repository Metadata ( : Version, Policy, Schema) Endpoint A

53 Brokered Communication 중앙집중형메시지브로커및메시징버스 Indirect addressing Protocol gateway New Endpoint B Old Endpoint B UDDI Repository Endpoint A

비즈니스로직을담고있는컴포넌트들은다양한패턴에따라서비스화되어서비스레지스트리에 등록되어서비스를제공 Unified Interface Layer UI Interface UI Interface Business Process Layer External I/F Contracts Bindings Behaviors Activities Rule Sets Sequential

54 비즈니스로직을담고있는컴포넌트들은다양한패턴에따라서비스화되어서비스레지스트리에 등록되어서비스를제공 Unified Interface Layer UI Interface UI Interface Business Process Layer External I/F Contracts Bindings Behaviors Activities Rule Sets Sequential Workflow 비지니스컴포넌트비지니스컴포넌트 Business Processes Business Processes Business Processes Business Service Layer Workflow Services Composite Services Business Component Layer Atomic Services Contracts Bindings Behaviors Composite Logics 비지니스컴포넌트비지니스컴포넌트 Component Component Component Data Access Contracts Bindings Wrapping 비지니스컴포넌트 Behaviors

55 BizLog Encryption Registry Exception Security Data Access 비즈니스서비스의실제구현기능을제공하며기졲 IT 리소스를재사용 Unified Interface Layer UI Interface UI Interface External I/F Biz 컴포넌트 Biz 컴포넌트 Biz 컴포넌트Biz 컴포넌트 Biz 컴포넌트 Biz 컴포넌트 SO DB Business Process Layer Business Processes Business Processes Business Processes NG NeOSS Application Framework SA DB Business Service Layer Workflow Services Composite Services Atomic Services ADM DB Business Component Layer Component Component Component Data Access NeOSS Framework.NET Framework 3.0 Enterprise Library FM DB FM DB...

2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

57 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

untitled

untitled 3 IBM WebSphere User Conference ESB (e-mail : ljm@kr.ibm.com) Infrastructure Solution, IGS 2005. 9.13 ESB 를통한어플리케이션통합구축 2 IT 40%. IT,,.,, (Real Time Enterprise), End to End Access Processes bounded by