Seminar on Service Oriented Architecture High Level Reference

  • Slides: 25
Download presentation
Seminar on Service Oriented Architecture High Level Reference Architecture Part 2 SOA Seminar Material

Seminar on Service Oriented Architecture High Level Reference Architecture Part 2 SOA Seminar Material taken from IBM CMU Ref. Architecture Document 1

High Level SOA Reference Architecture • These slides outline the document provide by IBM

High Level SOA Reference Architecture • These slides outline the document provide by IBM to CMU to guide CMU’s development of a Student Service Suite (S 3) SOA. • Work on this documented was completed in March of 2008. • In this course, we will use this document as a case study in SOA design. • See Blackboard’s Course Documents section. SOA Seminar Material taken from IBM CMU Ref. Architecture Document 2

Outline • • • Enterprise view IT Systems View Middleware view Solution stack view

Outline • • • Enterprise view IT Systems View Middleware view Solution stack view SOMA 3. 1 SOA Seminar Material taken from IBM CMU Ref. Architecture Document 3

Reference Architecture Enterprise View • Business participants from both inside and outside the organization

Reference Architecture Enterprise View • Business participants from both inside and outside the organization • Delivery channels • Business services represent services the enterprise wants to expose to customers, partners and internal users (identified by SOMA) • EIS bulk of data and logic • ESB routing, protocol mediation, and transformation SOA Seminar Material taken from IBM CMU Ref. Architecture Document 4

Enterprise View SOA Seminar Material taken from IBM CMU Ref. Architecture Document 5

Enterprise View SOA Seminar Material taken from IBM CMU Ref. Architecture Document 5

Reference Architecture IT Systems View (1) • Technical overview of the architecture • Business

Reference Architecture IT Systems View (1) • Technical overview of the architecture • Business as usual elements plus SOA related elements • Gateways (security & manageability) • ESB (adapters, queues, brokers) • Registries (several types) Service registry for service metadata LDAP registry for identities, access policies, certificates, configuration Material taken from 6 information SOA Seminar IBM CMU Ref. Architecture Document

Reference Architecture IT Systems View (2) • Information services to provide information to consumers

Reference Architecture IT Systems View (2) • Information services to provide information to consumers in a standard format despite how or where it might be stored • Process Services provide the ability to compose services together and choreograph their behavior to carry out business processes • Security Services are enhanced to meet SOA requirements • SOA related development tools are important but not shown SOA Seminar Material taken from IBM CMU Ref. Architecture Document 7

IT Systems View SOA Seminar Material taken from IBM CMU Ref. Architecture Document 8

IT Systems View SOA Seminar Material taken from IBM CMU Ref. Architecture Document 8

Reference Architecture Middleware View (1) • Business Application Services are at the core (fundamental

Reference Architecture Middleware View (1) • Business Application Services are at the core (fundamental & repeatable business tasks & identified by SOMA) • Tool support for this layer: Web. Sphere app server JBOSS, Glassfish, etc… SOA Seminar Material taken from IBM CMU Ref. Architecture Document 9

Reference Architecture Middleware View (2) • Access Services Layer Dedicated to integrating existing applications

Reference Architecture Middleware View (2) • Access Services Layer Dedicated to integrating existing applications and functions into an SOA. • Tool Support of this layer: Web. Sphere Adapters BEA adapters Sun See. Beyond Adapters, … • Adapters implemented with J 2 EE Connector Architecture (JCA) SOA Seminar Material taken from 10 IBM CMU Ref. Architecture Document

Some Notes on JCA • An EIS includes ERP systems, legacy systems, mainframe database

Some Notes on JCA • An EIS includes ERP systems, legacy systems, mainframe database and transaction processing systems. • A resource adapter is written for the EIS. • The adapter must communicate with the container and clients. • JCA defines system contracts between the application server and resource adapters. • JCA defines the client API of the resource adapter. • A resource adapter is analogous to a JDBC driver. SOA Seminar Material taken from 11 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (3) • Partner Services Layer Can be viewed as a

Reference Architecture Middleware View (3) • Partner Services Layer Can be viewed as a special case of interaction services - representing the integration of external entities • Government services • Other higher education services, etc. SOA Seminar Material taken from 12 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (4) • Interaction Services Layer - Captures the logic of

Reference Architecture Middleware View (4) • Interaction Services Layer - Captures the logic of presentation to the entities external to CMU - Web Frameworks, e. g. , struts, JSF, Ruby on Rails, provide a configurable sequence flow • Tool Support for this layer: IBM Web. Sphere Portal Server JBOSS Portal Vignette (industry leading implementation of JSR-168 Web Services for Remote Portlet WSRP) Apache Jet. Speed, JSF, Spring Framework, Material taken from etc… 13 SOA Seminar IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (5) • Process Services Layer Captures process flows and business

Reference Architecture Middleware View (5) • Process Services Layer Captures process flows and business rules. • Tool Support: - IBM Web. Sphere Process Server (SCA and BPEL) - Apache Tuscany (SCA, SDO and BPEL) - Active BPEL - Glassfish - Oracle Business Rules using RETE rules engine - IBM bought ILOG and now has a rules engine - Redhat DROOLS SOA Seminar Material taken from 14 IBM CMU Ref. Architecture Document

Business Process Using a Rules Engine Business Process Flow Rules centralize knowledge Facts Decision

Business Process Using a Rules Engine Business Process Flow Rules centralize knowledge Facts Decision Service Results Rules Engine SOA Seminar Rules Management SDK Rules Repository Material taken from 15 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (6) • Information Services Layer Provide access to the persistent

Reference Architecture Middleware View (6) • Information Services Layer Provide access to the persistent data of the business Provide access to business intelligence • Tool support includes: Oracle RDBMS IBM DB 2 Apache Derby My. SQL Ingres DBMS (open source) SOA Seminar Material taken from 16 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (7) • ESB delivers all interconnectivity capabilities • Transport services,

Reference Architecture Middleware View (7) • ESB delivers all interconnectivity capabilities • Transport services, Event services and Mediation services (routing and transformation, logging, auditing) • The ESB is a silent partner, transparent to services • Tool Support includes: IBM Web. Sphere ESB TIBCO Active. Matrix JBOSS ESB Apache Service. Mix, etc… • Registries are included in this layer. • Tools include: IBM Web. Sphere Service Registry and Repository BEA Aqua. Logic Registry and Repository UDDI) Material taken from etc… SOA Seminar 17 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (8) • • • Development Service Layer Business analysts need

Reference Architecture Middleware View (8) • • • Development Service Layer Business analysts need modeling tools. Software architects need to model data, flows, and system interactions. Software developers need to build business logic. Tools include: IBM Rational Software Architect IBM Rational Application Developer Eclipse Web Tools Platform Netbeans IDE (J 2 EE, Ruby, . . ) BEA workshop for Web. Logic Jboss developer suite, etc… BPEL Source Editors IBM Web. Sphere Integration Developer Eclipse BPEL designer plug-in Netbeans, etc. SOA Seminar Material taken from 18 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (9) • • IT Services Management Layer monitors and manages

Reference Architecture Middleware View (9) • • IT Services Management Layer monitors and manages deployed services. Tools include: IBM Web. Sphere Business Monitor BEA Aqua. Logic BPM Sun See. Beyond, etc… Infrastructure Services Layer (Security, efficiency, integrity, balanced workload, etc. . ) Tools include: IBM Tivoli Composite Application Manager (ITCAM) IBM Tivoli Identity Manager (TIM) IBM Tivoli Access Manager (TAM) - security policies and authorization BEA Aqua. Logic Enterprise Security Sun Java System Access Manager SOA Seminar Material taken from 19 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (10) • Infrastrcture Services Layer (continued) User Registries: Tools Include:

Reference Architecture Middleware View (10) • Infrastrcture Services Layer (continued) User Registries: Tools Include: IBM Tivoli Directory Server (LDAP-compliant) Microsoft Active Directory (LDAP-compliant) Novel e. Directory (LDAP-compliant) Open. LDAP, etc… SOA Seminar Material taken from 20 IBM CMU Ref. Architecture Document

Reference Architecture Middleware View (11) Business Innovation & Optimization Services Layer Business design tools

Reference Architecture Middleware View (11) Business Innovation & Optimization Services Layer Business design tools Tools include: IBM Web. Sphere Business Modeler Model to UML or BPEL Microsoft Visio Magic. Draw Sun See. Beyond e. Insight Process manager Business rules management Tools include: IBM Websphere process server Drools Jboss Rules, etc. . SOA Seminar Material taken from 21 IBM CMU Ref. Architecture Document

Middleware View SOA Seminar Material taken from 22 IBM CMU Ref. Architecture Document

Middleware View SOA Seminar Material taken from 22 IBM CMU Ref. Architecture Document

Solution Stack View SOA Seminar Material taken from 23 IBM CMU Ref. Architecture Document

Solution Stack View SOA Seminar Material taken from 23 IBM CMU Ref. Architecture Document

SOMA(1) • The Service Oriented Modeling and Architecture methodology - is used to identify

SOMA(1) • The Service Oriented Modeling and Architecture methodology - is used to identify candidate services. - provides guidance on the degree of service granularity. - may be compared with the OASIS SOA Adoption Blueprint - or Microsoft Motion SOA Seminar Material taken from 24 IBM CMU Ref. Architecture Document

SOMA 3. 1 Service Oriented Modeling and Architecture SOA Seminar Material taken from 25

SOMA 3. 1 Service Oriented Modeling and Architecture SOA Seminar Material taken from 25 IBM CMU Ref. Architecture Document