1 / 8

NPM Mediator JRA4 F2F, Edinburgh, 12-13 July 2005

NPM Mediator JRA4 F2F, Edinburgh, 12-13 July 2005. Alistair K Phipps (A.Phipps@ed.ac.uk) University of Edinburgh. About this presentation. Architecture and interface discussed previously, so focus on design Objectives: Agree on mediator design

barny
Télécharger la présentation

NPM Mediator JRA4 F2F, Edinburgh, 12-13 July 2005

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. NPM MediatorJRA4 F2F, Edinburgh, 12-13 July 2005 Alistair K Phipps (A.Phipps@ed.ac.uk) University of Edinburgh

  2. About this presentation • Architecture and interface discussed previously, so focus on design • Objectives: • Agree on mediator design • Decide if we're going to do aggregation or caching (data or discovery) - if so, when and how • Reference: • Detailed design: http://edms.cern.ch/document/606708 JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  3. Interface and mapping • Skeleton service auto-generated by Axis • mediator.service.NMWG has same operations as mediator.service.axis.NMWGSOAPBindingImpl (Skeleton), but using NM-WG object model types; same for Discovery • Service implementation uses Mapper to convert from Axis stubs into NM-WG object model, then calls into corresponding mediator.service.NMWG and mediator.service.Discovery operation JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  4. NM-WG Request • If a NM-WG request is received, the URI of the corresponding framework service must first be determined (by the mediator.service.NMWG implementation) • The DiscoveryFactory is used to create an instance of a class that implements the mediator.discoverer.Discovery interface • This interface is used to send the framework URI query to mediator.discoverer.axismapper.Discovery • This class then converts this request into one using the Axis stubs, and calls the corresponding method in mediator.discoverer.axis.Discovery • The query is then sent to the Discoverer and the URI received is returned back to mediator.service.NMWG JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  5. NM-WG Request (2) • Mediator.service.NMWG then uses the NMWGFactory to create an instance of a class that implements the mediator.framework.NMWG interface, with the specified end-point URI • This interface is used to send the NM-WG query to mediator.framework.axismapper.NMWG • This class then converts the request into one using the Axis stubs, and calls the corresponding method in mediator.framework.axis.NMWG • The return value, in Axis stub form, is converted into the NM-WG object model by mediator.framework.axismapper.NMWG and returned to mediator.service.NMWG JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  6. Discovery Request • If a Discovery request is received, the DiscoveryFactory is used by mediator.service.Discovery to create an instance of a class that implements the mediator.discoverer.Discovery interface • This interface is used to send the query to mediator.discoverer.axismapper.Discovery • This class then converts this request into one using the Axis stubs, and calls the corresponding method in mediator.discoverer.axis.Discovery • The query is then sent to the Discoverer and the return value, in Axis stub form, is converted into the NM-WG object model by mediator.discoverer.axismapper.NMWG and returned to mediator.service.Discovery JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  7. Aggregation and caching • Should we do aggregation? • Should we do caching of discovery information? • How long is it valid for? • Should we do caching of NM-WG report data? • Likely only makes sense for raw data, and if we have aggregation • Consider validity, quantity to cache, replacement algorithm JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

  8. Anything else? • Any other Mediator issues, questions, comments? JRA4: http://egee-jra4.web.cern.ch/EGEE-JRA4/

More Related