260 likes | 315 Vues
Service Oriented Architecture. Lecture 5: High Level Reference Architecture Part 2. 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.
E N D
Service Oriented Architecture Lecture 5: High Level Reference Architecture Part 2 Master of Information System Management
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 (S3) 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. Master of Information System Management
Outline • Enterprise view • IT Systems View • Middleware view • Solution stack view • SOMA 3.1 Master of Information System Management
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 Master of Information System Management
Enterprise View Master of Information System Management
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 information Master of Information System Management
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 Master of Information System Management
IT Systems View Master of Information System Management
Reference Architecture Middleware View (1) • Business Application Services are at the core (fundamental & repeatable business tasks & identified by SOMA) • Tool support for this layer: WebSphere app server JBOSS, Glassfish, etc… Master of Information System Management
Reference Architecture Middleware View (2) • Access Services Layer Dedicated to integrating existing applications and functions into an SOA. • Tool Support of this layer: WebSphere Adapters BEA adapters Sun SeeBeyond Adapters,… • Adapters implemented with J2EE Connector Architecture (JCA) Master of Information System Management
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. Master of Information System Management
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. Master of Information System Management
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 WebSphere Portal Server JBOSS Portal Vignette (industry leading implementation of JSR-168 Web Services for Remote Portlet WSRP) Apache JetSpeed, JSF, Spring Framework, etc… Master of Information System Management
Reference Architecture Middleware View (5) • Process Services Layer Captures process flows and business rules. • Tool Support: - IBM WebSphere 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 Master of Information System Management
Business Process Using a Rules Engine Business Process Rules centralize Flow knowledge Decision Service Facts Rules Management SDK Results Rules Engine Rules Repository Master of Information System Management
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 DB2 Apache Derby MySQL Ingres DBMS (open source) Master of Information System Management
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 WebSphere ESB TIBCO ActiveMatrix JBOSS ESB Apache ServiceMix, etc… • Registries are included in this layer. • Tools include: IBM WebSphere Service Registry and Repository BEA AquaLogic Registry and Repository UDDI) etc… Master of Information System Management
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 (J2EE, Ruby,..) BEA workshop for WebLogic Jboss developer suite, etc… • BPEL Source Editors IBM WebSphere Integration Developer Eclipse BPEL designer plug-in Netbeans, etc. Master of Information System Management
Reference Architecture Middleware View (9) • IT Services Management Layer monitors and manages deployed services. • Tools include: IBM WebSphere Business Monitor BEA AquaLogic BPM Sun SeeBeyond, 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 AquaLogic Enterprise Security Sun Java System Access Manager Master of Information System Management
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 eDirectory (LDAP-compliant) OpenLDAP, etc… Master of Information System Management
Reference Architecture Middleware View (11) Business Innovation & Optimization Services Layer Business design tools Tools include: IBM WebSphere Business Modeler Model to UML or BPEL Microsoft Visio MagicDraw Sun SeeBeyond eInsight Process manager Business rules management Tools include: IBM Websphere process server Drools Jboss Rules, etc.. Master of Information System Management
Middleware View Master of Information System Management
Solution Stack View Master of Information System Management
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 Master of Information System Management
SOMA 3.1 Service Oriented Modeling and Architecture Master of Information System Management