1 / 49

Tutorial on XML and Peer-to-Peer Technologies -- Introduction

NCSA Alliance May 8 2002. Tutorial on XML and Peer-to-Peer Technologies -- Introduction. PTLIU Laboratory for Community Grids Geoffrey Fox, Bryan Carpenter, Marlon Pierce Computer Science, Informatics, Physics

connieking
Télécharger la présentation

Tutorial on XML and Peer-to-Peer Technologies -- Introduction

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. NCSA Alliance May 8 2002 Tutorial on XML and Peer-to-Peer Technologies -- Introduction PTLIU Laboratory for Community Grids Geoffrey Fox, Bryan Carpenter, Marlon Pierce Computer Science, Informatics, Physics Indiana University, Bloomington IN 47404http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02 gcf@indiana.edu uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  2. Overview and Motivation I • XML is the universal language of the information age • XML will be used to describe the structure of “everything” • XML need not be used to instantiate everything • XML may not be so efficient but universality and expressivity are typically more important than performance • XML is powerful and is supported by a growing number of tools • XML defines entities as objects and not as tables, arrays … • This puts pressure on SQL (relational databases), Fortran etc. which do not naturally express objects uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  3. What is a Virtual XML Interface • We can specify interfaces in XML but we are not required to implement in XML. • Example 1:We aren’t likely to change syntax of mailReply-to:Geoffrey Fox <gcf@indiana.edu>To: Geoffrey Fox <gcf@grids.ucs.indiana.edu>Subject: A Test for TutorialA simple mail messageGeoffrey Fox gcf@indiana.edu FAX 8128567972Phones Cell 315-254-6387 Home 812323919 • But we could specify and indeed store in XML with transport done using conventional SMTP. • So conventional mail is easy to give a virtual XML specification for withname:value becoming<name>value</name> but this is not only way uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  4. Mail in XML • <mailasxmluri=“gxos://mail/users/gcf/sent/2002/february/290” ><smtpheaders><reply-toemail=“gcf@indiana.edu”>Geoffrey Fox</reply-to><toemail=“gcf@grids.ucs.indiana.edu” >Geoffrey Fox</to><subject>A Test for Tutorial</subject></smtpheaders><smtpbody><messagewhitespace="collapse"> A simple mail message</message><signature personuri=“ssn://123/45/6789”whitespace=“preserve” > Geoffrey Fox gcf@indiana.edu FAX 8128567972 Phones Cell 315-254-6387 Home 812323919 </signature></smtpbody></mailasxml> • Such an interface could be used by “User Messaging as a Web service” which could perhaps integrate News Groups, e-mail, text chat, instant messenger, voicemail uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  5. Overview and Motivation II • Peer-to-peer networks were popularized by applications like Napster and Seti@home but are generally important as they express a democratic model of computers and people linked together • Classic imperious computing model (as in Grid Client-Server ..) is a humble client accessing all knowing central servers • Of course the right solution has a mix of both classic Grid and P2P for that is how society works • This is Peer-to-Peer Grid • We will focus on a technology JXTA from Sun has it has a clear architecture and is illustrative of other P2P systems uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  6. Rival Estimate MainlyDigital Video Cohen’s Grid/P2P Use of Internet I ROBERT B. COHEN, PH.D. COHEN COMMUNICATIONS GROUP bcohen@bway.net 212-986-7720 Global Grid Forum Toronto Feb 18 2002 uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  7. S2S Server to Server Digital Video“on demand” Grid/P2P Use of Internet II uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  8. References • Peer-to-peer Computing: • Peer-to-Peer: Harnessing the Power of Disruptive Technologies by Andrew Oram, Nelson Minar, Clay Shirky, Tim O'Reilly (March 15, 2001, O'Reilly & Associates; ISBN: 059600110X) • http://www.openp2p.com from the O'Reilly group and • http://www.peer-to-peerwg.org/ as an industry working group that has linked to Grid Forum • Many XML books – choose one that is later than May 2001 XML Schema specification • http://www.w3c.org • http://www.xml.com/ uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  9. General XML Issues • XML has instances (.xml) and specification of instance structure (equivalent to class in Java) as a Schema (.xsd) • Ignore previous specification of structure as a DTD (data Type Definition) • There are editors (XML Spy) • Parsers (Xerces) • Transformers (XSLT) • Mappings from XML to C++/Java (Castor) • Databases (GoXML, Oracle, Tamino(SAG)) • Specific tools for particular XML dialects uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  10. XML as an Document or Object • Originally XML was designed for “documents” • XML specifies “true content” of document • HTML specifies rendering for information for display in a browser • Either stylesheets or XSLT specified mapping of “true content” into rendering • This is important but not covered here • Rather XML evolved to describe all objects – not just “documents” and it is this application which is driving widespread adoption of XML • E.g. WSDL describes both methods and data structures in XML – you can program in it uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  11. Where is XML Used in Science • Science inherits many capabilities from general world and has some specific to field • XML for technical (W3C) infrastructure • Schema XLink XQuery DOM SOAP WSDL RDF • XML for community infrastructure • XHTML SVG Dublin Core RSS XGSP SMIL WAI (Accessibility) … • XML for computing and Grids • “GatewayML” “JXTAML” “GlobusML(RSL)” • XML for generic scientific disciplines • MathML XSIL XDMF “XML for Sensors” • XML for particular scientific disciplines • GML(Geography) CML(Chemistry) .,…. • XML for education • ADL and IMS Standards uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  12. Some General XML Technology • Schema: uses XML to allow one to specify general (class) structure of an XML dialect • Xlink: uses XML to specify “link structure” (address) of XML fragment (subset of a document) • XQuery: uses XML to query a “pile of XML instances” (XML’s answer to SQL) • DOM: describes an XML instance as a tree with parent-child-sibling structure and events associated with tree elements (add, remove, mouseover …) • SOAP: Describe a message with an XML envelope and an XML or general body • WSDL: Define a Web Service with input and output ports (equivalent to remote software program (method) with input and output data • RDF: Specify statements like A has a property B with a value C uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  13. Some Community XML • XHTML is HTML redone in an XML syntax • SVG: Scalable Vector Graphics is general 2 dimensional vector graphics (X3D is 3 dimensional) • Dublin Core: bibliographic meta-data for documents such as author title … • RSS: simple way of specifying information nuggets as in News Groups • XGSP: Audio-video conferencing session definition including SIP and H323 • SMIL: Multimedia document specification including timelines uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  14. XML for Computing and Science • MathML specify either rendering or semantic meaning of equations (“Latex done in XML”) • XSIL: proposal from Caltech for specifying scientific data including tables, time series, storage • XDMF: proposal from ARL for “XML coupling” for scientific codes including mesh structure of PDE’s • GML: proposal from openGIS consortium for Geography meta-data as used in GIS (Geographical Information Systems) • CML: Define molecules and other chemistry specific objects uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  15. XML for Education • http://www.imsproject.net IMS (academic/industry) Consortium (ex-Educause) • http://www.adlnet.org Advanced Distributed learning from DoD - Sharable Content Object Reference Model (SCORM) • Curriculum Structure as a tree (removed?) • Objectives, Prerequisites, Completion Requirements • Quizzes and Tests (very complete) • Learning Meta-data – generalize Dublin core to education with “interactivity” “cost” etc. • Enterprise Properties – link to people and organization • Start of Learning Information (Competencies, Grades etc.) uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  16. General XML for Science Issues • The XML for Science “hierarchical definition” corresponds to • Science as a Web service defined hierarchically in a service model for web (Grid) applications • XML is very easy (“too easy?”) to define and modify • Compare difficulties in changing Java to be compatible with science by adding “complex” and “Fortran arrays” • Need strong community involvement to define the need standards or one might get a “Tower of XML Babel” • Can use XSLT to transform between different related XML dialects • Schemas “stored forever” define structure for prosperity uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  17. What is Everything • Everything is a distributed Object • Everything is a resource • Everything is a Service • You do not set up the Supercomputer or Learning Center (hardware centric); you offer the supercomputer or learning services • Everything is labeled by one or more URI’s yourworld://top/notsotop/…/nearbottom/leaf • Everything is described in XML • Everything communicates by messages (which are themselves specified in XML) • All computers and all data sources are linked together and to all people • All software has to be rewritten uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  18. Data Information Knowledge • So there are many definitions and these terms are used with little agreement as to meaning. • Here is Douglas W. Oard from University of Maryland • Data is the raw stuff – bits from the sensor or the computer program • Information is data in context • Databases contain data and produce information • Information Retrieval systems contain and provide information • Knowledge is a basis for making decisions • Use data-mining on information (data), simulations • Reason (AI) • Knowledge often controversial as requires interpreting information uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  19. RawData WS WS WS WS Web Service View • Distinguishing Information and Knowledge could be counter-productive as one builds a bunch of Web Services which accept some set of Information/Knowledge and give out another version of Information/Knowledge • If one is wise in choosing which web services to use then hopefully quality of information and knowledge will increase as one moves from left to right Data InformationKnowledge Increasing Knowledge Increasing Information uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  20. RawData WS WS WS WS WS WS WS WS Web Services II • Actually it is more complicated than this with a patchwork quilt of web services • Note it requires knowledge to know which web services to link together to make D into I into K WS WS WS WS WS WS WS WS uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  21. The Application Service Model • There are generic Grid system services: security, collaboration, persistent storage, universal access • OGSA (Open Grid Service Architecture) is implementing these as extended Web Services • An Application Web Service is a capability used either by another service or by a user • It has input and output ports – fed by devices or other services • A service “is a component” and is a replacement for a library in case where performance allows • Services (components) are a sustainable model of software development – each service has documented capability with standards compliant interfaces • XML defines interfaces at several levels • WSDL at Service interface level and XSIL or equivalent for scientific data format • A service can be written as Perl, Python, Java Servlet, Enterprise Javabean, CORBA (C++ or Fortran) Object … • Communication protocol can be RMI (Java), IIOP (CORBA) or SOAP (HTTP, XML) …… uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  22. Sensor Web Service Distributed Sensor Web Service Out Web Service portsUniversal sensor accessfor people/computers In Web Service portsDifferent formatSensor Data uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  23. Prog1WS Prog2WS Filter1WS Filter2WS Filter3WS Build as multiple interdisciplinaryPrograms Build as multiple Filter Web Services Data Analysis WS Data Analysis WS Sensor Data as a Webservice (WS) Simulation WS Simulation WS Visualization WS Visualization WS Sensor ManagementWS Application Web Services • Note Service model integrates sensors, sensor analysis, simulations and people • An Application Web Service is a capability used either by another service or by a user • It has input and output ports – data is from users, sensors or other services • Big services built hierarchically from “basic” services Data Management WS SLE (space Link Extension) as a WS uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  24. What is a Web Service I • A web service is a computer program running on either the local or remote machine with a set of well defined interfaces (ports) specified in XML (WSDL) • In principle, computer program can be in any language (Fortran .. Java .. Perl .. Python) and the interfaces can be implemented in any way what so ever • Interfaces can be method calls, Java RMI Messages, CGI Web invocations, totally compiled away (inlining) but • The simplest implementations involve XML messages (SOAP) and programs written in net friendly languages like Java and Python • Web Services separate the meaning of a port (message) interface from its implementation • Enhances/Enables Re-usable component model of ANY electronic resource uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  25. Web Service (WS) WS WS WS WS WS WS RawResources Raw Data Raw Data (Virtual) XML Data Interface WS WS etc. XML WS to WS Interfaces (Virtual) XML Knowledge (User) Interface Render to XML Display Format (Virtual) XML Rendering Interface Clients uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  26. Database Database Classic Grid Architecture Resources Content Access Composition Middle TierBrokers Service Providers Netsolve Security Collaboration Computing Middle Tier becomes Web Services Clients Users and Devices uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  27. PaymentCredit Card WSDL interfaces Security Catalog Warehouse shipping WSDL interfaces What is a Web Service II • Web Services have important implication that ALL interfaces are XML messages based. In contrast • Most Windows programs have interfaces defined as interrupts due to user inputs (see WSIA and W3C DOM) • Most software have interfaces defined as methods which might be implemented as a message but this is often NOT explicit uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  28. UDDI or WSIL WSFL WSDL SOAP or RMI HTTP or SMTP or IIOP or RMTP TCP/IP Physical Network Details of WSDL Protocol Stack • UDDI finds where programs are • remote( (distributed) programs are just Web Services • WSFL links programs together(under revision?) • WSDL defines interface (methods, parameters, data formats) • SOAP defines structure of message including serialization of information • HTTP is negotiation/transport protocol • TCP/IP is layers 3-4 of OSI • Physical Network is layer 1 of OSI uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  29. Examples of Web Services I • OGSA (Open Grid Service Architecture) • Integrate Web Service and Grid Concepts and allows Globus to be implemented as Web Services • Audio-Video Conferencing as a Web Service • Integrates H323, SIP, JXTA (etc.) protocols by mapping to single XML Interface • Provides VRVS reflector model from Messaging Web Service • Messaging or Event Web Service provides intelligent routing and buffering of messages • Computing as a Web service • Job submittal, status, composition, data services, visualization • Performance WS allows access to distributed monitoring data, analysis, models, and final benchmarks with interoperable XML interfaces uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  30. Examples of Web Services II • Education as a Web Service • One of easiest to do as object standards well defined (IMS) and little performance issues • Grading, Homework submission, registration, assessment etc. • Universal Access and Web Services • As Web Services allow multiple implementation of a particular interface, one can adjust to needs of particular clients (PDA v. versus, impaired sight etc.). See WSRP • Can build custom implementations of certain web services for particular communities but re-use others • Collaborative Web Services • As interfaces all message based, much easier to share Web Services than other applications (PowerPoint interface is NOT message based and harder to share than server app) uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  31. Education as a Web Service • Can link to Science as a Web Service and substitute educational modules • “Learning Object” XML standards already exist from IMS/ADL http://www.adlnet.org – need to update architecture • Web Services for virtual university include: • Registration • Performance (grading) • Authoring of Curriculum • Online laboratories for real and virtual instruments • Homework submission • Quizzesof various types (multiple choice, random parameters) • Assessment data access and analysis • Synchronous Delivery of Curricula • Scheduling of courses and mentoring sessions • Asynchronous access, data-mining and knowledge discovery • Learning Plan agents to guide students and teachers uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  32. XMLSkin XMLSkin Data base e-Science is XML Specified Resourcesconnected by XML specified messages Message Or Event Based InterConnection Software Resource Software Resource Implementation of resource and connection may or may not be XML uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  33. Biased History of Computing • In almost the beginning, there was Fortran and formats (6I5, 5F10.4) for data • ………………………….. • 1993-1997: HTML came along for Web Pages • 1998-…: XML was developed to define information in documents while HTML defining rendering • But soon it became used for specifying all data and their format • 2001: Web Services allowed XML to specify methods (subroutines) as well as data • Java, C++, Python, Perl, .. Fortran are now “just” the insides of XML specified programs uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  34. How do we organize all this • As everything is a resource implemented as a Web Service, we need a common description framework for • back end supercomputers and a petabyte data • Microsoft PowerPoint and this file • Grids tend to organize large back end resources but peer to peer (P2P) technology more natural for the digital equivalent of the scraps of information in each of the multiple sub-communities in a “virtual organization” • JXTA describes “Peer Groups” which are communities • Grids and P2P approaches can be integrated by building both in terms of Web Services with different implementations of core services such as discovery, and event or message transport/filter ….. • Gives a Peer-to-Peer Grid uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  35. Database Database Event/MessageBrokers Event/MessageBrokers Integrate P2P and Grid/WS Peer to Peer Grid JXTA Web Service Interfaces Web Service Interfaces JXTA A democratic organization Peer to Peer Grid uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  36. Database e-Science is just a pile of XML • Each leaf is a piece of XML either defining a nugget of information or a Service and/or containing links to other XML or “raw resources” uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  37. XML (RSS) Specification of Information Nuggets • <itemrdf:about="http://xml.com/pub/2000/08/09/xslt/xslt.html"> • <title> Processing Inclusions with XSLT </title> • <link>http://xml.com/pub/2000/08/09/xslt/xslt.html</link> • <description> • Processing document inclusions with general XML tools can be problematic. </description> • </item> • <item rdf:about="http://xml.com/pub/2000/08/09/rdfdb/index.html"> • <title> Putting RDF to Work </title> • <link>http://xml.com/pub/2000/08/09/rdfdb/index.html</link> • <description> • Tool and API support for the Resource Description Framework is slowly coming of age. </description> • </item> • </rdf:RDF> Example of XML meta-data in the “pile”pointing to other (outside) resources Links are essential as much meta-data willNOT be co-located with resource uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  38. Distributed Information Actually the XML is distributed all around in a dynamic Grid uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  39. Note XML specifiesboth internal andexternal nodes of tree root escience://root/one/two/bottom one two bottom Tree Structured Information • Roughly current organization of Web (Grid) So hierarchy blurs distinction between meta-data and information uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  40. root escience://root/one/two/mess one two mess “mess” can be multiple levels of tree Unstructured and Structured XML • Peer to Peer natural for unstructured “mess” (local broadcast) • Get a Grid of P2P organized communities uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  41. Database Database Grid Middleware Grid Middleware Grid Middleware Grid Middleware MP Group MP Group MP Group MP Group A Grid of Peer Groups MP=Middleware Peer uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  42. Audio Video Conferencing as a Web Service • We can use openh323 as core of a web service for audio video conferencing • We have designed XGSP as a common XML session protocol including SIP and H323 capabilities • We add additional commands to extend web service to support heterogeneous clients and new fault tolerance and audio mixing options • Will support traditional (H323, SIP) or new generationclients with native XML (JXTA) • Event Service must support UDP and Real-time constraints • WSDL must “bind” to RTP transport used in A/V field • Include Internet Audio (NetMeeting, HearMe SIP ….), Polycom (H323), Voice over IP Phones, and Access Grid (MBONE) uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  43. New TechXGSP A/V Conferencing Web Services Event/MessageService JXTAGateway SetupSession JXTA SIP SIPGateway MediaServer H323Gateway H323 MixAudio AGGateway ConvertCodec AccessGrid uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  44. XML General Session Protocol I <xs:complexType name="SessionDes"> <xs:sequence> <xs:element name="SessionName" type="xs:string"/> <xs:element name="SessionID" type="SessionID"/> <xs:element name="SessionCreator" type="UserURL"/> <xs:element name="SessionInfo" type="xs:string"/> <xs:element name="SessionTime"> <xs:complexType> <xs:sequence> <xs:element name="StartTime" type="xs:dateTime"/> <xs:element name="EndTime" type="xs:dateTime"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SessionURI" type="xs:anyURI"/> <xs:element name="SessionParticipants" maxOccurs="unbounded"> <xs:complexType> <xs:complexContent> <xs:extension base="UserURL"/> </xs:complexContent> </xs:complexType> </xs:element> <xs:element name="ContactInfo" type="UserURL"/> </xs:sequence> </xs:complexType> “random”fragment uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  45. XML General Session Protocol II <xs:complexType> <xs:sequence> <xs:element name="MediaCodec" type="xs:string"/> <xs:element name="CodecParam"> <xs:complexType> <xs:choice> <xs:element name="H.261" type="xs:H.261"/> <xs:element name="H.263" type="xs:H.263"/> <xs:element name="G.711" type="xs:G.711"/> <xs:element name="G.722" type="xs:G.722"/> <xs:element name="G.723" type="xs:G.723"/> <xs:element name="G.728" type="xs:G.728 "/> <xs:element name="G.729" type="xs:G.729"/> <xs:element name="GSM" type="xs:GSM"/> </xs:choice> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  46. A Typical SIP Message • REGISTER sip:registrar.biloxi.comVia: SIP/2.0/UDP 10.4.1.4:5060To: Bob (sip:bob@biloxi.com)From: Bob (sip:bob@biloxi.com);tag=456248Call-ID:843817637684230@phone21.boxesbybob.comCSeq: 1826 REGISTERContact: (sip:bob@10.4.1.4)Expires: 7200Contact-Length: 0 • Initially build a wrapper that accepts such messages and converts to XGSP uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  47. EarthScope CSIT Strategy • Make a list of resources with a hierarchical arrangement • People, Places, Results (Publications, meeting archives, Simulation Output), Activities, Sensors (Instruments), Data (raw and processed), Earth features, Computers, Software • Decide on component (Web Service) model and URI labelling (earthscope://devices/satellites/year/label …) • Respect performance requirements • Design so modules can be re-used, re-arranged and replaced for outreach (education) • Study related CSIT architectures of other fields • Grid Forum, PACI, ASCI for computing issues • W3C Web Consortium for basic IT infrastructure • openGIS XMML for related fields • IMS for Education uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  48. EarthScope HPCC Strategy • Decide what services are well enough understood and useful enough to be encapsulated as application Web Services • Parallel FEM Solvers • Visualization • Parallel Particle Dynamics • Access to Sensor Data • Image Processing • Make services as small as possible – smaller is simpler and more sustainable but with higher communication needs • Compose large services from smaller ones • Design Portals and portal components that allow one to manipulate services – set parameters, compose, invoke • Implement chosen System Web Services (job submit, performance, queue) on central machines and local clusters • Make certain infrastructure supports compute, data, middleware needs • Set necessary hardware/software meta-data uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

  49. EarthScope IT Strategy • Design an internal EIF (EarthScope Internal Framework) defining architecture and interface standards of internal Web Services and data structures • Design EEF (EarthScope External Framework) which maps external raw data into sensor web services • Choose some appropriate (mix of) middleware frameworks • .net, IBM, BEA, Sun, Oracle • Look at special requirements for key system services • Hardware/Data systems (new and legacy issues) • Security • Collaboration including Audio/Video conferencing • Peer-to-peer networking • Develop necessary meta-data wizards uri="http://grids.ucs.indiana.edu/ptliupages/presentations/ncsamay02" email="gcf@indiana.edu"

More Related