1 / 17

Using Agent Technology as a Support for an Enterprise Service Bus

Using Agent Technology as a Support for an Enterprise Service Bus. Paola Mordacci, Agostino Poggi, Carmelo Giovanni Tiso, Paola Turci {paola.mordacci,carmelo.giovanni.tiso} @studenti.unipr.it {poggi,turci}@ce.unipr.it. Service Oriented Architecture. Features. HTTP. CORBA. Web

yardley
Download Presentation

Using Agent Technology as a Support for an Enterprise Service Bus

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Agent Technology as a Support for an Enterprise Service Bus Paola Mordacci,Agostino Poggi, Carmelo Giovanni Tiso,Paola Turci {paola.mordacci,carmelo.giovanni.tiso}@studenti.unipr.it {poggi,turci}@ce.unipr.it

  2. Service Oriented Architecture Features HTTP CORBA Web Application Legacy SW A baseline of concepts and principles and a strategic vision have emerged Logical view • A service is an abstracted, logical view of actual programs, databases, business processes Message orientation • A service is defined in terms of the messages exchanged between the parts Description orientation • A service is described by machine-processable meta data Granularity • Services tend to use a small number of operations with relatively large and complex messages Platform neutral • Messages are sent in a platform-neutral, standardized format (XML) RMI ODBC Java Application SOA Data Base JCA .NET REMOTING .NET Application ERP, CRM Definition • There is no one recognized definition of SOA • SOA is an architectural style that supports service orientation • Service orientation is a way of thinking in terms of services and service-based development.

  3. Service Oriented Architecture HTTP CORBA Web Application Legacy SW Problems • Rely on static syntactical description of service interfaces • They guarantee services binding at design time • Do not address service selection based on a dynamic assessment of nonfunctional attributes • They guarantee syntactic interoperability, but they fail to provide semantic operability RMI ODBC Java Application SOA Data Base JCA .NET REMOTING .NET Application ERP, CRM Open issues • How to efficiently discover Web services • Semantic annotations • Federations and peer-to-peer discovery • How to allow and facilitate their composition • Semantic annotations • Workflow technologies • AI techniques

  4. Multi-AgentSystems for EAI HTTP CORBA Web Application Legacy SW RMI ODBC Java Application ? Data Base JCA .NET REMOTING .NET Application ERP, CRM MAS Interesting Features • Sociability • ACL • Cooperation and negotiation • FIPA specifications • Integration ability • Legacy systems • Web services and other SOA technologies • Workflow technologies • Semantic Web technologies

  5. Multi-AgentSystems&EAI Web Application LegacySW HTTP CORBA ODBC Java Application RMI Data Base SOA JCA .NET REMOTING ERP, CRM .NET Application MAS

  6. Multi-AgentSystems&EAI Web Application LegacySW HTTP CORBA ODBC Java Application RMI Data Base MAS JCA .NET REMOTING ERP, CRM .NET Application

  7. Multi-AgentSystems&EAI Web Application LegacySW HTTP CORBA ODBC SOA Java Application RMI Data Base MAS JCA .NET REMOTING ERP, CRM .NET Application

  8. Our Vision Web Application Web Application LegacySW LegacySW Web Application LegacySW SOA SOA SOA Java Application Java Application Java Application Data Base Data Base Data Base ERP, CRM ERP, CRM ERP, CRM .NET Application .NET Application .NET Application MAS MAS MAS

  9. Our Work JADE ServiceMix Integration • Development of an ACL – ESB normalized message bridge • Definition of agent based services for the realization intra and inter ESB composed services • Experimentation in a real scenario

  10. ESB ESB ESB On-line Book Selling

  11. Best Price

  12. Our Goal Web Application LegacySW HTTP CORBA SOA ODBC Java Application RMI Data Base MAS JCA .NET REMOTING ERP, CRM .NET Application Semantic layer

  13. Future Work OWL Based Semantic Software Layer • Representation • Efficient object-oriented representation • Full DL support • Efficient management • Reasoning • Both “open world” and “closed world” semantics • Efficient reasoning algorithms • Services discovery and composition • SAWSDL • Distributed AI planning techniques • Testing and development tools

  14. Thank you for your kind attention! Paola Mordacci,Agostino Poggi, Carmelo Giovanni Tiso,Paola Turci {paola.mordacci,carmelo.giovanni.tiso}@studenti.unipr.it {poggi,turci}@ce.unipr.it

  15. SOA vs. JBI/ESB • SOA and ESB Are More Than Different Answers to the Same Problem • ESB is designed assuming a world of horizontal layers - such as database, application logic, … SOA is designed for a world of vertical slices through the IT infrastructure - such as ordering, fulfillment, billing, etc. Computerworld 2005

  16. SOA vs. JBI/ESB • JBI is a Java standard for structuring business integration systems along SOA lines. It defines an environment for plug-in components that interact using a services model based directly on WSDL 2.0. Using JBI for Service-Oriented Integration (SOI) Ron Ten-Hove, Sun Microsystems January 27, 2006 • The ESB as a Pattern for SOA The Role of the Enterprise Service Bus W. Mark Richards Senior IT Architect and SOA Thought Leader - IBM Corporation October, 23, 2006

  17. Multi-Agent Systems&SemanticWeb

More Related