Torsten Winterberg OPITZ CONSULTING GmbH Bernd Trops SOPERA Concepts in Comparison SOA Symposium, Oktober 2010 What is an ESB?
The Team: Masons-of-SOA www.soa-spezial.de www.soa-community.com Bernd Trops (Sopera) Berthold Maier (Oracle Consulting) Clemens Utschig-Utschig  (Böhringer-Ingelheim) Hajo Normann (HP) Torsten Winterberg (OPITZ CONSULTING) Jürgen Kress (Oracle Corp.)
Agenda It‘s all about architecture… Motivation Definition of an ESB – a try SOA as a platform? Chosen concepts out of the  area SOA-platform/ESB
1 It‘s all about architecture …
It‘s all about architecture…
Building the enterprise: Vision Infrastructure (The „Grid“) Applications Process Management Storage Middleware Database Services Workflow/BPM/BAM ESB/EDA/BRE Processcontrolling Processdesign Processoptimization Process Implementation Service Request Service Delivery Process Monitoring
The Paradigm: Service Orientation The eight service orientation design principles
2 Motivation
Motivation If this is the only requirement, then  we do have a PROBLEM! S. O. S. My Boss said  we need an ESB
Know your requirements Process Oriented  Management System
Know your requirements Business benefits Enterprise requirements Increase efficiencies Integration of new business areas Better cooperation with partners customer supplier Decrease costs Analyze business processes Automate business processes
Project context Department 1 Department 2 Department 3
Domain concept
Domain concept evaluation capture results Relationship coordination Development DM-Campagne Data-analysis Customerdata management Service (…) Service (…) Service (…) Service (…) Service (…) Service (…) Product Contract Accounting Customer contact Customer Ordermanagement Service management
3 Definition of an ESB – a try
There is no standard definition for an ESB Commentators disagree over whether to define an enterprise service bus as an  architectural style , a  software product , or a  group of software products . While use of an ESB certainly implies adherence to a particular architecture, the term "enterprise service bus" almost always denotes the software infrastructure that enables such an architecture, and in essence, the  ESB is considered a platform to realize a service oriented architecture . An Enterprise Service Bus (ESB) brings flow-related concepts such as  transformation and routing  to a service oriented architecture. An ESB can also provide an  abstraction for endpoints . This promotes  flexibility in the transport layer  and  enables loose coupling  and easy connection between services. Source: wikipedia engl.
Why a Service Bus: A few examples …
Example: Location Transparency
Example: Backwards Compatibility
Example: Service Enablement
Canonical Data Format
The ESB as a translator ESB APP 2 Enrich Transform Validate V alidate  E nrich  T ransform and  O perate  Umwandlung der Daten vom Common Modell in das Proprietäre – visa versa Data Sources EBS Privater EntityService APP 3 Business Entity Service Öffentlicher  Service Kontrakt (WSDL) Generierter  Service Kontrakt (WSDL) APP 1
Core tasks of an ESB Routing Transformation of messages Protocol transformation Standard based integration Distributed and highly scalable integration platform Independent and distributed deployment for service components Implementation of enterprise integration pattern Quality of Services Security
What is an ESB? Security Author. Authent. LDAP Encryption Repository Livecycle Maintenance Administration Deployment HA Flow control Alerting System monitoring Monitoring  Exception management Routing Transformation Message Broker FTP AQ transport protocols and conversion SMTP HTTP/S SOAP JMS File JMS/XA Tux Enrichment SSO SLAs Directory
4 SOA as a platform?
SOA Suite Blueprint BPM / Workflow Rich Client Web Client Business Activity Monitoring (BAM) Application  Server Governance Registry Rules … View Layer Enterprise Service Bus (ESB) Service Service Service Service Service System X System Z System Y
Is an ESB enough? Could a suite be an option? A suite includes all established concepts I don‘t need everything a suite offers me YAGNI  “You Ain’t Gonna Need It”,  This comes out of extreme programming. The principle means that you should only develop what you really need. Programming should be concentrated on the application problems and not on infrastructure Somebody has already built it    just use it First Rule of developing your own framework: Don't do it! Suite provides innovation and stability Suite will be continuously improved  It is expensive  Not really, there are alternatives like open source suites
SOPERA’s products based on open source packages and cover all major SOA and integration aspects Integration Data Integration SAP Netweaver Di Integration MS BizTalk Integration SAG WM Integration Security Identity Management Authentification Authorisation Key Management System & Service Management. System Monitoring System Management Activity Monitoring Mgmt. Dashboard BPM & BAM Workflow/ Human Interaction Process Management Composite Service Devel. BAM Service Governance Service Lookup Policy Management Service Versioning Application Development Code Generation Simulation Test Packaging ESB Dynamic Mediation Java/ .Net-Support Distributed Architecture Openness/ Extensibility
SOPERA Suite is built out of open source  packages SOPERA DI SOPERA ASF SOPERA BPM Enterprise Business Process Management Enterprise Service Bus Enterprise Data &  Application Integration
UNTERTITEL SOPERA is technology and vendor independent Business applications Legacy integration SAP integration Gateway to  3rd party ESB Eclipse Swordfish ensuring integration and exchangeability of SOA components Messaging ActiveMQ JORAM Registry Nsure OpenUDDI Security Eclipse  Higgins BPEL engine Apache ODE Intalio WebSphere MQ TIBCO EMS Centrasite Evidian Access Master HP Select View Oracle BPEL MS BizTalk System Mgmt. Hyperic Nagios DI/EAI Talend HP Open View IBM Tivoli WebSphere TX MS BizTalk Commercial Plug-Ins Open Source Plug-Ins Service Integration
SOPERA ASF is built of  “ world-class ”  components SOPERA DI Tooling for SOA Eclipse SOPERA ToolSuite Intelligent Deployment ARIS Business Architect Other UML Modeling Tools XMI Import Excel Require- ment mgmt tools Runtime Platform (JSE, JEE, .net, SAP) Custom Services .NET Applications Legacy Systems Service Registries/ Repositories SOA  Security Services Messaging/ Transport  Services Orchestration & Workflow Server Distributed Service Bus SOPERA ESB Runtime Framework SBB Service Manage- ment SOPERA  HQ Manage- ment &  Monitoring Operations Delivery Design & Development Analysis Requirements  engineering Model-driven Architecture  DevBox Code Gen Service Editor Policy Editor Service Implementation DI Tools BPM Tools AdminTools SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA Advanced Services Factory SOPERA Advanced Services Factory0 Plug-Ins (Delivered with SOPERA) Third Party Components
Oracle SOA Suite - Service Plattform Farben und Linien als Kopiervorlage A A A A A A A J2EE Application Server (Oracle AS, JBoss, WebLogic, WebSphere) Messaging Metadata Repository Apps Adapters   B2B   SES RFID Partners DB Legacy CONNECTIVITY Routing Transform Data Quality ETL & Replication Data Integrator ESB Mediation ROUTING & DATA SERVICES Native BPEL Business  Rules Human  Workflow BPEL Process Manager ORCHESTRATION GOVERNANCE UDDI Discovery Policies WS Policies Security Web Services Manager Registry System  Monitoring Enterprise Manager Events Business Monitoring BAM Business Intelligence Analytics MANAGEMENT & MONITORING Application Development Framework Analyst Tools BPA Suite JDeveloper
Oracle SOA Suite – Service Platform Unified Runtime Policy Manager Optimized binding Human Workflow (+AMX, AG, Orgn) Business Rules Oracle Service Bus Common JCA-based connectivity infrastructure Repository EM console +BPMN Screens BAM B2B Mediator Workspace MS Office  BPM Studio  (Business & IT views) Shared BPMN Model BPA BPMN 2.0,  BPEL Rich End User Interaction Web-based customization Process Composer Process Analytics Proc Cubes Process Portal (WC spaces) Process Core BPEL BPMN
JBossESB – Reliable SOA infrastructure Quelle: http://www.jboss.org/jbossesb/
Or do I really like to build my own suite? Quelle: Thilo Frotscher
You need a solid base
All components have to work together
Know your requirements Business Benefits Enterprise requirements Increase efficiencies Integration of new business areas Better cooperation with partners customer supplier Decrease costs Analyze business processes Automate business processes
Requirements for a suite ( derived from business requirements) Communication requirements Transport definition (http, jms) Transformation requirements Security Monitoring Staging … To choose the right suite is time consuming To build it by yourself as well …
Example – cost utility analysis  Seite  (-) nicht vorhanden / unzureichend  (o) Workaround (+) gute Unterstützung  (++) sehr gute Unterstützung
Example – cost utility analysis cont. Seite  (-) nicht vorhanden / unzureichend  (o) Workaround (+) gute Unterstützung  (++) sehr gute Unterstützung
Example – cost utility analysis cont. Seite  (-) nicht vorhanden / unzureichend  (o) Workaround (+) gute Unterstützung  (++) sehr gute Unterstützung
Example – cost utility analysis cont. Seite  (-) nicht vorhanden / unzureichend  (o) Workaround (+) gute Unterstützung  (++) sehr gute Unterstützung
Buy / build / open source Buy:  Garanty, support, integration, innovation, ... Build:  My Product, my features, only the minimum features... Open Source:  A mix out of buy and build: Garanty and flexibility, you can build your own extension: professional open source
5 SOA Platform / ESB concepts
Hub- and Spoke versus distributed bus Bottleneck due to limitation of message throughput Linear scalable based on distributed architecture   Distributed Service Bus Hub
Quality of Service Policy Trading at Runtime Service Provider SOA Integration Infrastructure Service Registry Administrator look-up provider for service with quality Administrator Provider Description Quality of Service (provided) Binding Information register Agreed Policy Agreed Policy send response Service Consumer invoke service operation Quality of Service (requested) configure requested QoS
SCA as a concept C 1 C 2 wire component composite service reference S R S S R R properties Java interface WSDL portType Binding: SOAP JMS JCS …
Event Delivery Network (EDN) Seite
End-to-End Instance Tracking BPEL Human Workflow Routing Business Rules External Service
SOPERA ASF Policies
Global policy management: Oracle WSM Policy Manager Service Infrastructure Policy Manager Mediator BPEL Human Task Web Service Interceptor: Authentication Authorization Message Integrity & Confidentiality (signatures, encryption/decryption) Publish security requirements as WS-Policy in WSDL Service Component  Interceptors: Authorization HTTP/SOAP  message 2 3 4 5 1 HTTP/SOAP  message Web Service Interceptor: User token insertion (such as SAML) Integrity & Confidentiality (signatures, encryption/decryption) Clearly separates process logic from security concerns Secures endpoints Sets and propagate identity Seite  SOAP SOAP SSO (Oracle Access  Manager & 3 rd -Party) DB LDAP File Java Platform Security
6 Methodology
SOA Maturity Models What is my status regarding SOA YASOAMM
Top down SOA Business Capabilities  Technical Infrastructure Business Application Business Processes Domain Service Layer sample process sample orchestration Legacy ERP CRM A B
Rapid SOA is scalable SOA.zip SOA Reactor Anwendungsprozesse Autom. Funktionalität Daten & Speichersysteme SOA Governance Rapid SOA Rapid SOA Rapid SOA Rapid SOA enforces the SOA Reactor to achieve a Zipped SOA umfassende unternehmensweite SOA Rapid SOA Rapid SOA Rapid SOA Business- IT-Alignement IT-Department Bussiness Geschäftsprozesse Business Capabilities Domain Model Rapid SOA Projekt Efford time Disziplinen Prozess Governance Service Governance Domain Governance
Summary
Summary The right tool for the right purpose What are your requirements? Platform /Tools not automatically bring  you a SOA It‘s all about architecture  The key is to understand service orientation Design for change
Kontakt: Torsten Winterberg Director Strategy & Innovation  Head of Competence Center SOA Oracle ACE Director OPITZ CONSULTING GmbH Kirchstr. 6, 51647 Gummersbach, Germany Phone: +49 2261 6001 0 [email_address]
Kontakt: Bernd Trops Director Professional Service SOPERA GmbH Strässchensweg 10, 53113 Bonn, Germany [email_address]

What is an ESB? OPITZ CONSULTING - Winterberg - Trops

  • 1.
    Torsten Winterberg OPITZCONSULTING GmbH Bernd Trops SOPERA Concepts in Comparison SOA Symposium, Oktober 2010 What is an ESB?
  • 2.
    The Team: Masons-of-SOAwww.soa-spezial.de www.soa-community.com Bernd Trops (Sopera) Berthold Maier (Oracle Consulting) Clemens Utschig-Utschig (Böhringer-Ingelheim) Hajo Normann (HP) Torsten Winterberg (OPITZ CONSULTING) Jürgen Kress (Oracle Corp.)
  • 3.
    Agenda It‘s allabout architecture… Motivation Definition of an ESB – a try SOA as a platform? Chosen concepts out of the area SOA-platform/ESB
  • 4.
    1 It‘s allabout architecture …
  • 5.
    It‘s all aboutarchitecture…
  • 6.
    Building the enterprise:Vision Infrastructure (The „Grid“) Applications Process Management Storage Middleware Database Services Workflow/BPM/BAM ESB/EDA/BRE Processcontrolling Processdesign Processoptimization Process Implementation Service Request Service Delivery Process Monitoring
  • 7.
    The Paradigm: ServiceOrientation The eight service orientation design principles
  • 8.
  • 9.
    Motivation If thisis the only requirement, then we do have a PROBLEM! S. O. S. My Boss said we need an ESB
  • 10.
    Know your requirementsProcess Oriented Management System
  • 11.
    Know your requirementsBusiness benefits Enterprise requirements Increase efficiencies Integration of new business areas Better cooperation with partners customer supplier Decrease costs Analyze business processes Automate business processes
  • 12.
    Project context Department1 Department 2 Department 3
  • 13.
  • 14.
    Domain concept evaluationcapture results Relationship coordination Development DM-Campagne Data-analysis Customerdata management Service (…) Service (…) Service (…) Service (…) Service (…) Service (…) Product Contract Accounting Customer contact Customer Ordermanagement Service management
  • 15.
    3 Definition ofan ESB – a try
  • 16.
    There is nostandard definition for an ESB Commentators disagree over whether to define an enterprise service bus as an architectural style , a software product , or a group of software products . While use of an ESB certainly implies adherence to a particular architecture, the term "enterprise service bus" almost always denotes the software infrastructure that enables such an architecture, and in essence, the ESB is considered a platform to realize a service oriented architecture . An Enterprise Service Bus (ESB) brings flow-related concepts such as transformation and routing to a service oriented architecture. An ESB can also provide an abstraction for endpoints . This promotes flexibility in the transport layer and enables loose coupling and easy connection between services. Source: wikipedia engl.
  • 17.
    Why a ServiceBus: A few examples …
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
    The ESB asa translator ESB APP 2 Enrich Transform Validate V alidate E nrich T ransform and O perate Umwandlung der Daten vom Common Modell in das Proprietäre – visa versa Data Sources EBS Privater EntityService APP 3 Business Entity Service Öffentlicher Service Kontrakt (WSDL) Generierter Service Kontrakt (WSDL) APP 1
  • 23.
    Core tasks ofan ESB Routing Transformation of messages Protocol transformation Standard based integration Distributed and highly scalable integration platform Independent and distributed deployment for service components Implementation of enterprise integration pattern Quality of Services Security
  • 24.
    What is anESB? Security Author. Authent. LDAP Encryption Repository Livecycle Maintenance Administration Deployment HA Flow control Alerting System monitoring Monitoring Exception management Routing Transformation Message Broker FTP AQ transport protocols and conversion SMTP HTTP/S SOAP JMS File JMS/XA Tux Enrichment SSO SLAs Directory
  • 25.
    4 SOA asa platform?
  • 26.
    SOA Suite BlueprintBPM / Workflow Rich Client Web Client Business Activity Monitoring (BAM) Application Server Governance Registry Rules … View Layer Enterprise Service Bus (ESB) Service Service Service Service Service System X System Z System Y
  • 27.
    Is an ESBenough? Could a suite be an option? A suite includes all established concepts I don‘t need everything a suite offers me YAGNI “You Ain’t Gonna Need It”, This comes out of extreme programming. The principle means that you should only develop what you really need. Programming should be concentrated on the application problems and not on infrastructure Somebody has already built it  just use it First Rule of developing your own framework: Don't do it! Suite provides innovation and stability Suite will be continuously improved It is expensive Not really, there are alternatives like open source suites
  • 28.
    SOPERA’s products basedon open source packages and cover all major SOA and integration aspects Integration Data Integration SAP Netweaver Di Integration MS BizTalk Integration SAG WM Integration Security Identity Management Authentification Authorisation Key Management System & Service Management. System Monitoring System Management Activity Monitoring Mgmt. Dashboard BPM & BAM Workflow/ Human Interaction Process Management Composite Service Devel. BAM Service Governance Service Lookup Policy Management Service Versioning Application Development Code Generation Simulation Test Packaging ESB Dynamic Mediation Java/ .Net-Support Distributed Architecture Openness/ Extensibility
  • 29.
    SOPERA Suite isbuilt out of open source packages SOPERA DI SOPERA ASF SOPERA BPM Enterprise Business Process Management Enterprise Service Bus Enterprise Data & Application Integration
  • 30.
    UNTERTITEL SOPERA istechnology and vendor independent Business applications Legacy integration SAP integration Gateway to 3rd party ESB Eclipse Swordfish ensuring integration and exchangeability of SOA components Messaging ActiveMQ JORAM Registry Nsure OpenUDDI Security Eclipse Higgins BPEL engine Apache ODE Intalio WebSphere MQ TIBCO EMS Centrasite Evidian Access Master HP Select View Oracle BPEL MS BizTalk System Mgmt. Hyperic Nagios DI/EAI Talend HP Open View IBM Tivoli WebSphere TX MS BizTalk Commercial Plug-Ins Open Source Plug-Ins Service Integration
  • 31.
    SOPERA ASF isbuilt of “ world-class ” components SOPERA DI Tooling for SOA Eclipse SOPERA ToolSuite Intelligent Deployment ARIS Business Architect Other UML Modeling Tools XMI Import Excel Require- ment mgmt tools Runtime Platform (JSE, JEE, .net, SAP) Custom Services .NET Applications Legacy Systems Service Registries/ Repositories SOA Security Services Messaging/ Transport Services Orchestration & Workflow Server Distributed Service Bus SOPERA ESB Runtime Framework SBB Service Manage- ment SOPERA HQ Manage- ment & Monitoring Operations Delivery Design & Development Analysis Requirements engineering Model-driven Architecture DevBox Code Gen Service Editor Policy Editor Service Implementation DI Tools BPM Tools AdminTools SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA SOPERA Advanced Services Factory SOPERA Advanced Services Factory0 Plug-Ins (Delivered with SOPERA) Third Party Components
  • 32.
    Oracle SOA Suite- Service Plattform Farben und Linien als Kopiervorlage A A A A A A A J2EE Application Server (Oracle AS, JBoss, WebLogic, WebSphere) Messaging Metadata Repository Apps Adapters B2B SES RFID Partners DB Legacy CONNECTIVITY Routing Transform Data Quality ETL & Replication Data Integrator ESB Mediation ROUTING & DATA SERVICES Native BPEL Business Rules Human Workflow BPEL Process Manager ORCHESTRATION GOVERNANCE UDDI Discovery Policies WS Policies Security Web Services Manager Registry System Monitoring Enterprise Manager Events Business Monitoring BAM Business Intelligence Analytics MANAGEMENT & MONITORING Application Development Framework Analyst Tools BPA Suite JDeveloper
  • 33.
    Oracle SOA Suite– Service Platform Unified Runtime Policy Manager Optimized binding Human Workflow (+AMX, AG, Orgn) Business Rules Oracle Service Bus Common JCA-based connectivity infrastructure Repository EM console +BPMN Screens BAM B2B Mediator Workspace MS Office BPM Studio (Business & IT views) Shared BPMN Model BPA BPMN 2.0, BPEL Rich End User Interaction Web-based customization Process Composer Process Analytics Proc Cubes Process Portal (WC spaces) Process Core BPEL BPMN
  • 34.
    JBossESB – ReliableSOA infrastructure Quelle: http://www.jboss.org/jbossesb/
  • 35.
    Or do Ireally like to build my own suite? Quelle: Thilo Frotscher
  • 36.
    You need asolid base
  • 37.
    All components haveto work together
  • 38.
    Know your requirementsBusiness Benefits Enterprise requirements Increase efficiencies Integration of new business areas Better cooperation with partners customer supplier Decrease costs Analyze business processes Automate business processes
  • 39.
    Requirements for asuite ( derived from business requirements) Communication requirements Transport definition (http, jms) Transformation requirements Security Monitoring Staging … To choose the right suite is time consuming To build it by yourself as well …
  • 40.
    Example – costutility analysis Seite (-) nicht vorhanden / unzureichend (o) Workaround (+) gute Unterstützung (++) sehr gute Unterstützung
  • 41.
    Example – costutility analysis cont. Seite (-) nicht vorhanden / unzureichend (o) Workaround (+) gute Unterstützung (++) sehr gute Unterstützung
  • 42.
    Example – costutility analysis cont. Seite (-) nicht vorhanden / unzureichend (o) Workaround (+) gute Unterstützung (++) sehr gute Unterstützung
  • 43.
    Example – costutility analysis cont. Seite (-) nicht vorhanden / unzureichend (o) Workaround (+) gute Unterstützung (++) sehr gute Unterstützung
  • 44.
    Buy / build/ open source Buy: Garanty, support, integration, innovation, ... Build: My Product, my features, only the minimum features... Open Source: A mix out of buy and build: Garanty and flexibility, you can build your own extension: professional open source
  • 45.
    5 SOA Platform/ ESB concepts
  • 46.
    Hub- and Spokeversus distributed bus Bottleneck due to limitation of message throughput Linear scalable based on distributed architecture Distributed Service Bus Hub
  • 47.
    Quality of ServicePolicy Trading at Runtime Service Provider SOA Integration Infrastructure Service Registry Administrator look-up provider for service with quality Administrator Provider Description Quality of Service (provided) Binding Information register Agreed Policy Agreed Policy send response Service Consumer invoke service operation Quality of Service (requested) configure requested QoS
  • 48.
    SCA as aconcept C 1 C 2 wire component composite service reference S R S S R R properties Java interface WSDL portType Binding: SOAP JMS JCS …
  • 49.
  • 50.
    End-to-End Instance TrackingBPEL Human Workflow Routing Business Rules External Service
  • 51.
  • 52.
    Global policy management:Oracle WSM Policy Manager Service Infrastructure Policy Manager Mediator BPEL Human Task Web Service Interceptor: Authentication Authorization Message Integrity & Confidentiality (signatures, encryption/decryption) Publish security requirements as WS-Policy in WSDL Service Component Interceptors: Authorization HTTP/SOAP message 2 3 4 5 1 HTTP/SOAP message Web Service Interceptor: User token insertion (such as SAML) Integrity & Confidentiality (signatures, encryption/decryption) Clearly separates process logic from security concerns Secures endpoints Sets and propagate identity Seite SOAP SOAP SSO (Oracle Access Manager & 3 rd -Party) DB LDAP File Java Platform Security
  • 53.
  • 54.
    SOA Maturity ModelsWhat is my status regarding SOA YASOAMM
  • 55.
    Top down SOABusiness Capabilities Technical Infrastructure Business Application Business Processes Domain Service Layer sample process sample orchestration Legacy ERP CRM A B
  • 56.
    Rapid SOA isscalable SOA.zip SOA Reactor Anwendungsprozesse Autom. Funktionalität Daten & Speichersysteme SOA Governance Rapid SOA Rapid SOA Rapid SOA Rapid SOA enforces the SOA Reactor to achieve a Zipped SOA umfassende unternehmensweite SOA Rapid SOA Rapid SOA Rapid SOA Business- IT-Alignement IT-Department Bussiness Geschäftsprozesse Business Capabilities Domain Model Rapid SOA Projekt Efford time Disziplinen Prozess Governance Service Governance Domain Governance
  • 57.
  • 58.
    Summary The righttool for the right purpose What are your requirements? Platform /Tools not automatically bring you a SOA It‘s all about architecture The key is to understand service orientation Design for change
  • 59.
    Kontakt: Torsten WinterbergDirector Strategy & Innovation Head of Competence Center SOA Oracle ACE Director OPITZ CONSULTING GmbH Kirchstr. 6, 51647 Gummersbach, Germany Phone: +49 2261 6001 0 [email_address]
  • 60.
    Kontakt: Bernd TropsDirector Professional Service SOPERA GmbH Strässchensweg 10, 53113 Bonn, Germany [email_address]

Editor's Notes

  • #6 Nach Thomas Erl: a vision that defines a target state a formal paradigm that defines a method for achieving the target state technology innovation that improves the benefit potential of the target state technology architecture capable of realizing the target state formal practices and patterns that support the creation and evolution of the target state
  • #10 Das ist das problem
  • #11 Nicht nur tolles tool
  • #12 Business ist im vordergrund
  • #13 Mehrwert kann im department passieren Mehrwert wird wahrscheinlich eher übergreifend end-to-end aufgesetzt -> it muss das enablen
  • #14 Wie reden diese Domainen miteinander Modern ESB - Embrace heterogenicy Story for modern vs traditional
  • #20 Event pattern heraussuchen
  • #27 Botschaft: egal was du mal brauchst, das ist dann halt in der SUite Botschaft: du brauchst es nicht nutzen Botschaft: du keine Suite, dann pass auf, dass du upgradefähig bleibst.
  • #28 Esb is part of a suite Modern environments need more then the core ESB functionality You should not concentrate on plattform integration
  • #33 Standardfolie Idealerweise 5-7 Hauptpunkte oder 3 Hauptpunkte mit Unterpunkten GGf. Hauptpunkte untereinander horizontal abgrenzen (Menu Format / Zeilenabstand / Abstand vor einem Absatz = 1 Zeile bei den Zeilen mit Hauptpunkten!)
  • #44 OSB: 16 MULE: 7 SM: 3
  • #49 SCA terminology: Composite : deployment unit Service : entry-point into composite Component : provides logic Reference : refers to external services Wire : connects services, components and references – no special semantic. Bindings: Access interactions with outside a composite Vereinfacht die Entwicklung in Service Orientierten Architekturen Entwicklung konzentriert sich auf Implementierung der Geschäftslogik, SCA Umgebung regelt bzw. vereinfacht die technische Integration Vereinheitlichung / Standardisierung Technologie-abstrahierend, Integration, Wiederverwendung, Loose Kopplung Modulare Komposition von Komponenten, die in verschiedenen Implementierungssprachen umgesetzt sein können Trennung von Geschäftslogik, Middlewareabhängigkeiten und nichtfunktionalen Aspekten Wiederverwendung von Implementierungen in unterschiedlichen Konfigurationen
  • #51 Can follow the message through all of components. With Search! Execution Context Identifier (ECID) is used by several other Oracle products, such as Oracle Portal
  • #53 OPS4J = Oracle Platform Security For Java (JPS implementation) used for authentication and authorization. Upon entering Service Infra, a Java Subject is attached to the message and is used to propagate identity and other properties.