JBoss Enterprise SOA Platform JBoss Application Platform for Portal

1. JBoss Enterprise SOA PlatformJBoss Application Platform for Portal 임형준(hyungjun25@cnu.ac.kr) 충남대학교 컴퓨터공학과 데이터베이스시스템 연구실 2014년 9월 7일 일요일

2. 목차 • JBoss Application Platform • 상태 복제 (State Replication) 부연 설명 • SOA (Service-Oriented Architecture) • JBoss Enterprise SOA Platform • SOA Redefined • Components • Strategy • JBossESB (Enterprise Service Bus) • JBoss Application Platform for Portal

3. 상태 복제 (State Replication)

4. 상태 복제 (State Replication) • 서비스접근 시 응답속도의 항상성 유지 • 클러스터 내의 모든 노드들이 상태 접근 가능 • 하나의 노드가 장애 시 다른 노드에서 클라이언트와 통신하여 서비스 제공

5. State Replication 방법 • Fine-Grained State Replication • TreeCache의 Object 변경 시 field level의 변경 사항만을 복제 • Buddy Replication & Data Gravitation for HTTP Session • 상태정보를 하나 이상의 buddy node (backup server)에만 복제 • HTTP 요청이 오면 해당 노드는 cluster에서 상태 정보를 복제 • Failover일 경우, HTTP 요청이 반드시 buddy node로 전달되지는 않음 • Sticky load-balancing (session affinity) 사용 • Synchronous VS. Asynchronous • 상태 복제를 동기화할 경우, 노드 장애 시 항상 상태 정보를 최신으로 유지할 수 있으나 성능은 떨어짐 • 어느 정도의 상태 정보 손실이 발생해도 문제가 없다면 상태 정보 복제를 비동기화해서 성능을 개선 (동기화 주기 설정 가능)

6. Service-Oriented Architecture

7. SOA, Service-Oriented Architecture • 느슨히 결합된 서비스를 이용하여 애플리케이션 기능을 제공하는 분산 시스템을 구현하기 위한 접근방법 • 서비스의 재사용 고려 • 개방 표준의 이용 극대화 • 비즈니스 신속성을 개선하는데 초점 • 기업 내외부의 비즈니스 서비스 효율성 극대화 • 애플리케이션 기능과 상호작용하기 위한 표준화된 방법 제공 • 기존 컴포넌트로부터 애플리케이션을 조합하고, 신규 생성하는데 초점

8. 이상적인 기업환경 • IT 인프라를 구성하고 있는 컴포넌트 사용의 극대화 • 컴포넌트: • Hardware • Storage • Bandwidth • Applications • Digital Assets • People

9. SOA: Where most customers are today – Web Applications • 이점 • 확장 용이성, 산재된 시스템 연계 용이성 • 표준 API를 사용하여 애플리케이션 컴포넌트 재사용 극대화 • “서비스”가 여러 애플리케이션에 의해 호출, 상호 호환적 사용 • 이슈 • 연계가 밀접하게 결합되며, 쉽게 단절됨 • 비즈니스 프로세스 변화 요구에 신속한 대처가 어려움 • 중앙 집중화된 관리 부족

10. SOA: Where some customers are today – Basic SOA • 이점 • Wrapper는 표준 API로 애플리케이션 컴포넌트에 적용되어 컴포넌트 간 통신 및 재사용을 가능케 함 • .NET, Java, COBOL 등 • 이슈 • 표준 API로 wrapping 되면, “서비스”는 상호 호환적으로 사용되며 다수의 애플리케이션에 의해서 호출 가능 • 불필요한 비용 중복이 발생하지 않음

11. SOA: Where many customers are going – Service Integration & Orchestration • 이점 • 느슨하게 결합된 서비스가 생성되면, 다수의 분야에서 재사용 가능 • “composite applications” 의 조합을 통해서 신규 서비스 연계 플랫폼 구축 • 변경에 따른 비용 및 위험 요소 최소화 • 유지비용 최소화 • 비즈니스 변화 요구에 신속한 대응

12. JBoss Enterprise SOA Platform

13. SOA Redefined • Red Hat is the Simple, Open and Affordable way to modernize your legacy infrastructure • Simple: • Easy-to-consume SOA portfolio • Enterprise-class Stability & Performance • Industry-leading Support • Open: • Unparalleled Flexibility & Control of Open Source • Open standards-based • Affordable: • Significantly Lower Total Cost of Ownership • Re-focus resources on the things that differentiate your business

14. JBoss Enterprise SOA Platform • Enables Business Process Automation by integrating and orchestrating application components and services running on JBoss Enterprise Middleware and/or any other standards-based AS • Single distribution that integrates JBoss ESB, jBPM, Rules, Hibernate, Clustering and Seam • Combines SOA integration, BPM, EDA and CEP technologies to automate business processes to improve business productivity • Certified Platform for Service Integration & Orchestration • Simple, Flexible, & Scalable • Light footprint, simple installation • Scalable clustering to support high transaction volumes • Customizable footprint via microkernel architecture

15. Components • JBoss jBPM • 비즈니스 프로세스 자동화 및 워크플로우 엔진 • JBoss Rules • 비즈니스 룰 정의 및 관리 시스템 • JBoss ESB (Enterprise Service Bus) • 이기종 시스템 사이의 메시지 전달, 변환, 라우팅 기능을 제공하는 서비스 연계 시스템 JBoss Enterprise SOA Platform JBoss jBPM JBoss Rules JBoss ESB Transformation, Routing, Registry, Repository JBoss Enterprise Application Platform JBoss Microkernel Java Virtual Machine Operating System Windows, Unix, Other Linux

16. JEMS & Java EE Architecture

17. Stages of Adoption • Design/Determination • Should everything be a service? • Enablement (Java EE, .NET, various) • Infrastructure (Registry, Management, ESB) • Orchestration/Composition • BPEL • Transformation • Routing • Integration: Data, Application, Information, Process • Dynamic Discovery and Real-Time Governance • Event-Driven (EDA) • Self-aware software components that dynamically orchestrated themselves into composite applications that meet all policies and SLAs automatically

18. JBoss SOA Platform Strategy • Bring an SOA integration and process platform to mass market in an easy to consume and affordable package • Build core platform from existing components • Customers/Community –Registry, repository, JMS transport, and EJB endpoints • JBoss Enterprise Middleware –e.g., microcontainer, Messaging, JBossWS, Seam • Other OSS projects –e.g., Smooks for transformation • Extend to a Business Process Platform • Leverage jBPM and Rules mass adopted run time engines • SCA (Service Component Architecture) • Expand audience and improve productivity with tools • Leverage Eclipse for visual designer and plug-ins –SOA lifecycle tools • Open up opportunities for Integration and SOA partners • Connectors, B2B Gateways, SOA Governance, Business Services

19. Enterprise Service Bus

20. JBossESB Aims • To provide the standard OSS infrastructure for SOA • SOA principles first and foremost • Use SOA principles internally as well as externally • Everything is (conceptually) be considered as a service • Every service can be replaced • Standards compliant • Though requirements live longer • JBossESB is not tied to one particular standard

21. Enterprise Service Bus • Enterprise Service Bus is a “narrowing” of the concepts in SOA • A concrete implementation of SOA principles

22. JBossESB • Plug and replace any component • EJB3 & Seam: State of art service component models • Maximum flexibility for partners, ISVs and community

23. JBossESB 4.0 Provide • Message delivery • JMS (JBossMQ, JBoss Messaging, ActiveMQ, MQSeries) • (S)FTP, HTTP, email, database, shared file system • Transformations • Smooks, XSLT • Content-based routing • JBoss Rules, XPath • Repository • JAX-R based • UDDI support out-of-the-box (Scout and jUDDI) • Gateways • Extensive examples and documentation

24. ESB-aware and ESB-unaware

25. JBossESB 5.0 Provide • Process orchestration • Change management (hot deployment, versioning, lifecycle management) • Quality of service (transactions, failover) • Message encryption, security • Management/governance

26. JBossESB Conclusions • JBossESB architecture is key to flexibility and future proofing • Forms the backbone of our SOA strategy • JEMS components are the flesh • SOA internally as well as externally • Best-of-breed approach • Interoperability with other ESBs is important

27. JBoss Application Platform for Portal

28. Portals JBoss Application Platform for Portal • 산재된 정보에 접근하기 위한 포탈 서비스로 컨텐츠 수집, 표현, 정보의 개인화 서비스 제공 • http://portal.demo.jboss.com/portal/default/default JBoss Enterprise Application Platform for Portals JBoss Portal JBoss Enterprise Application Platform JBoss Microkernel Java Virtual Machine Operating System Windows, Unix, Other Linux

29. Features • Improved user productivity • A framework for centralized and secure access to applications and information, which fosters collaboration, streamlines business processes, and reduces costs • Interoperability and open standards • Based on open standards, it can incorporate components into the portal as standardized and reusable portlets • Reliability and scalability • Based on the market-leading JBoss Application Server, so access to dynamic information is simple • Improved ROI (Return on investment) • Increasing return on investment of IT assets and reducing the need for new application and integration development