SOA Connectivity and Integration Strategic Vision 24 March 2010
•Télécharger en tant que PPT, PDF•
2 j'aime•1,321 vues
Présentation déroulée par Hubert Lalanne au Study Tour SOA du 24 mars, à Hursley.
![Agenda ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
SOA Connectivity and Integration Strategic Vision 24 March 2010
- 1. Connectivity and Integration Strategic Vision Hubert Lalanne DE – Technical Executive IBM SWG France Study Tour Connectivity, Hursley, 24th March 2010
- 6. Connectivity is a matter of Architecture Business Processes Connectivity Layer New tool or application New Business Partner New Package Coverage of application or packages Interfaces Integration Logic Other Applications, Tools or Systems inside or outside of the scope of the business process Isolation Layer Control and reconfiguration point Observation point
- 8. Enterprisewide Connectivity Is Multiowned and Multilayered Enterprise Connectivity Domain Connectivity Domain Connectivity Domain Connectivity Domain "A" SOA Domain "B" Domain "C" Domain Registry Domain Registry Domain Registry Enterprise Registry Private service = consumed by one application Local service = consumed by more applications in the same SOA domain Public service = consumed by more applications from multiple SOA domains Public Services Local Services Local Services Local Services Domain SOA COE Domain COE Domain COE EnterpriseCOE
- 15. Combining ESB Technologies: The “Hybrid Bus” Legacy Client-Server Back office / Call Centre Intranet / Extranet / Internet Portals Legacy / System Z Data Stores WMB - built for universal connectivity and transformation in heterogeneous IT environments WESB - optimized with WAS for an integrated SOA platform and BPM WDP - purpose-built hardware for simplified deployment and hardened security ESB
- 16. The Connectivity ‘Ecosystem’ Service Monitoring Tivoli CAM for SOA Publish Find Enrich Govern Manage Service Registry WebSphere Services Registry and Repository WebSphere MQ messaging backbone MQI Java JMS XMS for .NET C# XMS for C/C++ Messaging Backbone for SOA WebSphere MQ WebSphere Process Server Service Orchestration and BPM Universal Transformation WebSphere Transformation Extender Service Security Tivoli Security Products Business Rules WebSphere iLog JRules WebSphere Business Event
- 19. Many Defined Patterns for ESB-based Solutions http://www.ibm.com/developerworks/wikis/display/esbpatterns/ Service Enablement Gateway OR OR OR Message-based Integration File Processing Event-driven Integration Service Virtualization
- 20. Patterns & Templates Vision Flows, Subflows, Modules, Schema, WSDL, Maps, ESQL etc 1. Capture ‘pattern’ ESB Runtime: Deployed artefacts 3. Discover and apply ‘pattern’ 5. Manage deployed ‘pattern’ 2. Share ‘pattern’ Pattern ‘library’ (repository) Solutions, fragments, etc Development artefacts - or – Deployment artefacts 4. Deploy ‘pattern’ IBM Confidential
- 22. Patterns-Based Development Accelerate development productivity Select pattern… … Configure… … Generate flow! Discover, Interact , Optimize WebSphere Message Broker V7 and WebSphere Integration Developer V7
- 25. Extend the reach of the Universal Messaging Backbone Qualities-of-Service Delivery Styles Transactional Persistent At-least-once Best-Effort Fire-and-Forget Request-Reply Replay Guaranteed At-Most-Once Client-Server Backbone Point-to-Point Peer-to-Peer Publish/Subscribe Grid Bus Fastest speed Multicast Lowest Latency Unicast Skills Languages Mindsets Orientations COBOL, C/C++, RPC Java, JEE, JMS .NET, C #, VB, WCF AJAX, Perl, Python… Service Batch File Message Resource… WSDL, XML, WS-* REST, MEST, KISS End-Points Vendor Platforms Applications Operating Systems Devices Web services Web 2.0 JEE, .NET, etc Exploitation & Support SAP, Siebel, etc… Mobile, Wireless, PoS, Sensor, Actuator, RFID… Appliances HTTP, AJAX, REST,… SOAP, WSDL, WS-RM, WS-N…
- 28. Connection of Services … not Service Bus Delegation Delegation Federated Service Registry A’ A’’ A A’ A’ A A’’
- 33. Contract / SLA Enforcement Pattern (3) The ESB checks that Consumer X has an SLA with Provider Y Service WebSphere Service Registry and Repository Governance Audit Repository Message (1) A message is received from Consumer X SLA Consumer X Provider Y (2) ESB for Provider Y retrieves valid SLAs Message (5) ESB routes to service endpoint with suitable SLD SLD (4) ESB retrieves the specific SLA policies SLA policies Application SLA Compliance (6) ESB records SLA Metrics in a database for later analysis
- 35. Connectivity for Hybrid Clouds Off-Premise outside the Enterprise On-Premise within the Enterprise “ How can I quickly and easily integrate my new off-premise solution with my existing on-premise applications?” Public Clouds Technologies Packaged Applications Databases, Web services, Messaging, App Servers, … E - Business Suite
- 36. Connectivity Cloud Scenarios Private Clouds Traditional Apps On-Premise within the Enterprise Off-Premise outside the Enterprise Public Clouds
- 37. 02/02/10
Notes de l'éditeur
- Tactical Guideline: In large organizations with semiautonomous business units and subsidiaries, a "federated" approach to SOA is the most effective in overcoming political, organizational and technical hurdles.
- We have identified 4/5 generic use cases (in order of priority): Discovery – how would the user discover the patterns that are available and applicable at the relevant scope level. Application – now that the user has discovered a pattern, how would the authoring tools guide the user in the realization of the patterns. Capture – the initial capturing of patterns or partially configured patterns. Sharing – once the pattern is captured, how can a pattern be shared and categorized for later discovery. There are also different sharing scope: within a project, within a team, within an organization, etc. Management – can a pattern be managed as an aggregate during deployment and runtime administration. e.g. should a solution-level pattern like Service Gateway be managed directly as a “service gateway” concept in the runtime administration console or be managed as its individual set of mediation primitives/nodes.
- *IBM Confidential* IBM Software Group Page of 14
- Patterns Based Development Create top-down, parameterized connectivity solutions e.g. Web Service façades, Message oriented processing, Queue to File IBM pre-supplied patterns Simplifies creation of most common scenarios according to best practices Complements existing bottom-up constructional approach for bespoke connectivity Patterns Explorer Inventory of key patterns available for solution generation Each Pattern contains clear help to explain context and applicability Pattern Generation Enables simple creation of flows and related artifacts from pre-supplied pattern Pattern Properties allow configuration of behaviour Design time properties affect structure of flow, e.g. number of WSDL operations Runtime properties affects behaviour of flow during processing
- Speaker Notes: This slide describes the IBM approach to Federated Connectivity, which brings together Federated Registry, Management, and Security to provide a holistic solution. The objectives on the right hand side (purple box) list out the multiple considerations that need to be taken into account when providing a complete solution to this problem - and the IBM approach provides the “model”, “console”, and “protocol” to achieve all of these (grey box at the bottom) requirements.
- Service Federation Management is supported by an integrated solution across WSRR (console UI and registry) and the ESB family to enable service re-use across enterprise domains. What is Service Federation Management? Industries are moving to service-oriented architectures (SOA) to give them increased business agility. SOA is about the services that allow an enterprise to achieve its business goals. Service re-use and flexibility are key factors in the success of SOA. Service Federation Management is concerned with maximizing service re-use across heterogeneous enterprise domains. The reality of modern enterprises Most modern enterprises are not single entities, but have multiple business units. Each business unit encapsulates services reused within the business unit boundaries via its connectivity infrastructure. These business units are often unconnected and autonomous - they are effectively islands of SOA, or service domains . In this environment, there may be specific triggers driving the requirement to share services between service domains. These may be a result of a merger or acquisition, the creation of inter-enterprise hosted services, or as a result of multi-enterprise collaboration. Sharing services on a case-by-case basis is possible, but can be complex and, hence costly. This cost can be reduced by bridging connectivity across domain boundaries. A federated approach Service Federation Management is focused on sharing services between domains, rather than federating the underlying connectivity infrastructure. This is supported by a federation model, protocol and console: The federation model provides a unifying view of federation relevant content: A view of connectivity abstracted from product details Contains just what is needed for federation tasks A Web 2.0-based protocol to access the service connectivity and registry components supporting a domain Discovery of those components Creation or copying of service references Creation and monitoring of service proxies A Web 2.0-based console for controlling service domains Definition of a service domain Definition of the 'visibility' of services in that domain Discovery of connectivity components that are capable of hosting mediation functions such as proxies Enabling the creation of proxies to provide control points for access to services What Service Federation Management is NOT Service Federation Management is not going to solve all connectivity problems, but it will enable easy configuration of best practice patterns for service sharing. Service Federation Management doesn't support transformation (to map between different interface requirements), or the requirement to share services within a specific domain (it is inter- rather than intra-domain).
- Speaker Notes: Here is where we can introduce (or elude to) some technology that IBM is working on to solve that problem (SilverLining), although we cannot mention it by name. The question in the green speech bubble in the center is the key, showing how your enterprise with its packaged, home-grown applications and technologies need to be integrated in a first-class way to the multitude of Cloud delivered technologies. IBM is working on a solution which is suitable for all sizes of enterprise, with a wide range of skills (ranging from little to deep technical skills) – i.e. a highly consumable and user-friendly solution which allows you to quickly and easily integrate your off-premise solutions with your existing enterprise or “across and beyond the enterprise” solution