FIPA Abstract Architecture London FIPA meeting January 24-29, 2000 from: TC-A members.

Slides:



Advertisements
Similar presentations
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
Advertisements

Web Service Architecture
Siebel Web Services Siebel Web Services March, From
Overview of Web Services
An Introduction to Web Services Sriram Krishnan, Ph.D.
General introduction to Web services and an implementation example
SOAP.
CIS 375—Web App Dev II SOAP.
Web Services Darshan R. Kapadia Gregor von Laszewski 1http://grid.rit.edu.
Web Services Nasrullah. Motivation about web service There are number of programms over the internet that need to communicate with other programms over.
Virtual Ticketing Agents using Web Services and J2EE Advisor: Dr. Chung-E-Wang Date: 05/06/03 Naveen Repala.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
Latest techniques and Applications in Interprocess Communication and Coordination Xiaoou Zhang.
PAWN: A Novel Ingestion Workflow Technology for Digital Preservation
An Agent-Oriented Approach to the Integration of Information Sources Michael Christoffel Institute for Program Structures and Data Organization, University.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
GFIPM Web Services Concept and Normative Standards GFIPM Delivery Team Meeting November 2011.
Secure Systems Research Group - FAU Web Services Standards Presented by Keiko Hashizume.
SOAP, WSDL, UDDI. Service Broker Basic SOAP Message Exchange Service Consumer Service Provider http transport SOAP message WSDL describing service SOAP.
Requirements for DSML 2.0. Summary RFC 2251 fidelity Represent existing directory protocols with new transport syntax Backwards compatibility with DSML.
EAD: A Technical Introduction Julie Hardesty, Metadata Analyst June 3, 2014.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
An Introduction to Software Architecture
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
JADE - A FIPA-Compliant Java Agent Development Framework Andrei Dancus Spring 2002.
Introduction to MDA (Model Driven Architecture) CYT.
What is Service Oriented Architecture ? CS409 Application Services Even Semester 2007.
1 HKU CSIS DB Seminar: HKU CSIS DB Seminar: Web Services Oriented Data Processing and Integration Speaker: Eric Lo.
Web Services Description Language CS409 Application Services Even Semester 2007.
1 Technologies for distributed systems Andrew Jones School of Computer Science Cardiff University.
What is MOF? The Meta Object Facility (MOF) specification provides a set of CORBA interfaces that can be used to define and manipulate a set of interoperable.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Module 7 Active Directory and Account Management.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
Web Services Standards. Introduction A web service is a type of component that is available on the web and can be incorporated in applications or used.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Distributed Information Retrieval Using a Multi-Agent System and The Role of Logic Programming.
Web Services. ASP.NET Web Services  Goals of ASP.NET Web services:  To enable cross-platform, cross- business computing  Great for “service” based.
Random Logic l Forum.NET l Web Services Enhancements for Microsoft.NET (WSE) Forum.NET ● October 4th, 2006.
Chapter 10 Intro to SOAP and WSDL. Objectives By study in the chapter, you will be able to: Describe what is SOAP Exam the rules for creating a SOAP document.
Copyright © 2013 Curt Hill SOAP Protocol for exchanging data and Enabling Web Services.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
SKOS. Ontologies Metadata –Resources marked-up with descriptions of their content. No good unless everyone speaks the same language; Terminologies –Provide.
Supporting FIPA Interoperability for Legacy Multi-Agent Systems Christos Georgousopoulos 1 Omer F. Rana 1 ( ) 2.
Kemal Baykal Rasim Ismayilov
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
Agent Overview. Topics Agent and its characteristics Architectures Agent Management.
Simple Object Access Protocol
Quality of Service Models for Web Services Eric Montrym 2/18/05.
Globus: A Report. Introduction What is Globus? Need for Globus. Goal of Globus Approach used by Globus: –Develop High level tools and basic technologies.
BEA position on W3C ‘Web Services’ Standards Jags Ramnarayan 11th April 2001.
Foundation For Intelligent Physical Agents FIPA Abstract Architecture Specification Presented by Michal Zaremba DERI.
1 G52IWS: Web Services Description Language (WSDL) Chris Greenhalgh
OWL Web Ontology Language Summary IHan HSIAO (Sharon)
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
Beginning 자바 웹 서비스 SOAP 강미란 Cyber-Infrastructure Research Lab Konkuk University.
XML and Distributed Applications By Quddus Chong Presentation for CS551 – Fall 2001.
Real-Time Systems Laboratory Seolyoung, Jeong JADE (Java Agent DEvelopment framework )
A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
Sabri Kızanlık Ural Emekçi
CORBA Alegria Baquero.
CORBA Alegria Baquero.
ELECTRONIC MAIL SECURITY
ELECTRONIC MAIL SECURITY
Session 2: Metadata and Catalogues
AGENT FRAMEWORK By- Arpan Biswas Rahul Gupta.
Presentation transcript:

FIPA Abstract Architecture London FIPA meeting January 24-29, 2000 from: TC-A members

Overview b Introduction b Describe the architecture b Interoperability b Next steps

Goals of abstract architecture b Provide end-to-end message interoperability Where there may be heterogeneous systems b Describe common elements and relationships b Do this without linking to a particular implementation

Other Goals b Model work on common distributed computing systems Java, CORBA b Facilitate re-use of existing systems Previous FIPA work, existing directory, management, transport and security systems b For info on Goals, see Appendix A- D of the Architecture Document

Mapping Abstract to Concrete b Abstract architecture moves to realized implementations

Abstract to Concrete b Whole set or one element b Promote reusability b Add elements needed to for that particular concrete version

Abstracting one element A concrete version of directory services shared by several implementations

Mandatory and Optional b If an element is mandatory at the abstract level, it must be included at the concrete level b If an element is optional at the abstract level, it can be mandatory at the concrete level b At the concrete level, the authors can add new mandatory and optional elements

Abstract architecture can’t do it all! b Some things cannot be modeled abstractly Management and Lifecycle Much of security Mobility b Some things need more work Gateways, domains and policy Conversation policy

Relationship to current FIPA specs b Very close to FIPA 99 work b Some differences with FIPA 97 work - see doc for details b Doesn’t cover the application domain specs

FIPA Abstract Architecture b Agents and directory b Message & Message Encoding b Transport b Platforms & Services b Interoperability

Agents & directory b Agents have agent-directory-entries b Agent-directory-entries registered with directory-services b Agent descriptions include Agent-name Locator (contains transport info) Agent-attributes b Search directory-services for interesting agents

Agents & directory

Key differences b Agent-name separated from addressing Gives us transport independence b Directory service Simpler than current FIPA model - suggest that there are two types Quick lookup Extensive search

FIPA-Message b Expressed in Agent Communication Language b Has content b Content is expressed in a content language, may reference ontologies b Very similar to existing models

Message Encoding b Encoding of a message happens at several levels Message content FIPA-message Transport-level b FIPA-messages are transformed to transport-message prior to transport b FIPA-messages can contain FIPA- messages

Message Transformation

Message Transform b Within FIPA-message, sender & receiver are always agent-names b FIPA-messages can be transformed to transport appropriate representations b Envelope can have transport-descriptions and other attributes Message authentication and encryption can be handled this way

Transport b Assume agents can be communicated w/ using multiple transports b Transport-description holds transport info Locator can hold multiple transport descriptions Locator is part of agent-description in the directory-service

Multiple Transports

Transport Description b Transport-description contains Transport-type: SMTP, IIOP, HTTP, etc. Transport-specific-address Transport-specific-properties b FIPA will maintain a standard set of these, but they can be extended

Key Differences b Transport address is separated from agent-name b Message-transport-service* is optional, not mandatory b Extensible model for expanding transports, transport properties * Though most systems will probably implement it

Platforms and Services b Agent-platform is a collection of services b Agent-Platform is optional, not mandatory* b Basic services Directory-service Message-transport-service * Though most systems will probably implement it

Interoperability b Details still in discussion b Basic model is via gateways b Gateways can do logical transforms From one representation to another Java objects -> IDL XML -> tag/string b Gateways can do transport transforms

Gateways b Can be standalone, or part of other elements in system b Can be addressable or “hidden”

Interoperability b As realizations of the architecture occur, need to create interoperability profiles: what can the system interoperate with under what conditions

Next Steps b Review of Abstract Architecture Incorporate comments Go to draft status b Add gateway work b Write Interoperability Guidelines b Write workplans for concrete instantiations

Summary b Abstract architecture designed for end to end messaging interoperability Compatible with FIPA 99 work b Must be mapped to concrete specifications Concrete specification will contain elements that could not be modeled abstractly b Ready to start creating concrete specifications