1 / 15

The REGNET Demonstration (Trial service) – D10

The REGNET Demonstration (Trial service) – D10. Contents. Scope Integration design patterns Broker and Connector. Scope of task 4.2. Objectives. Integrate into the REGNET system feedback coming from the validation activity : Components improvement Internationalisation (going on)

cranford
Download Presentation

The REGNET Demonstration (Trial service) – D10

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. The REGNET Demonstration (Trial service) – D10

  2. Contents • Scope • Integration design patterns • Broker and Connector REGNET Final Project Review

  3. Scope of task 4.2

  4. Objectives • Integrate into the REGNET system feedback coming from the validation activity: • Components improvement • Internationalisation (going on) • Components integration: Data Entry, Product Catalogue Management/eShop, Z39.50 servers through Broker • Implementation of collaborative process • REGNET hub hosting: http://garonne.toulouse.valtech.fr:8080/jetspeed REGNET Final Project Review

  5. Outputs • Deliverable D10 “REGNET – Demonstration (Trial Service)” • Regnet prototype: new version of the REGNET system integrating all modification done during the work-package • Report about new functionalities • Full installation and user manual. REGNET Final Project Review

  6. Integration architecture design patterns

  7. Document exchange: EDI Partner A Partner B Back end Application 2 Translation Tier Partner Tier 1:N Back end Application 1 Asynchronous, mutually agreed message format Private and Public processes Application node containing new or modified code Read-write data Transient data Applications whose characteristics are unspecified REGNET Final Project Review

  8. Exposed Application: MOM Partner A Partner B Partner Tier 1:N Exposed Application 2 Asynchronous Exposed Application 1 Private and Public processes Application node containing new or modified code Read-write data Applications whose characteristics are unspecified REGNET Final Project Review

  9. Exposed Business Services: Web Services Partner A Partner B Back end Application 2 N:1 Exposed Business Services Tier Partner Tier 1:N Asynchronous synchronous Back end Application 1 Asynchronous, mutually agreed message format Private and Public processes Application node containing new or modified code Read-write data Read only data Applications whose characteristics are unspecified REGNET Final Project Review

  10. Managed public processes: ebXML Partner A Partner B Back end Application 2 N:1 Public Process Rules Tier Partner Tier 1:N Asynchronous synchronous Back end Application 1 Asynchronous, server-specified or mutually agreed message format Public processes Private processes Read-write data Application node containing new or modified code Transient data Applications whose characteristics are unspecified Read only data REGNET Final Project Review

  11. Managed Public and Private Processes Partner A Partner B Private Process Rules Tier Public Process Rules Tier Back end Application 2 N:1 N:1 asynch sync 1:N Partner Tier Back end Application 1 Asynchronous, server-specified or mutually agreed message format asynch sync Public processes Private processes Read-write data Application node containing new or modified code Transient data Applications whose characteristics are unspecified Read only data REGNET Final Project Review

  12. REGNET Broker and Connector

  13. Need for integration • Look and feel • Integration of REGNET components based on Web Services: • TextML (CH data) • PCM (eBusiness data) • Procurement • Each component implement a generic interface: getCatalogue, storeCatalogue, getItem, storeItem, listCatalog • Search tool manage a CSC centralised repository containing basic information + references about all products REGNET Final Project Review

  14. Z39.50 connector Generic connector REGNET Broker Implements { getCatalogs(); storeCatalog(); listCatalog(); getItem(); storeItem(); } GUI EShop TextML connector PCM connector PCM REGNET Broker Data Entry SOAP SOAP SOAP MySQL TextML Z39.50 server REGNET Final Project Review

  15. eShop Broker Procurement Search & Retrieval Linux Linux Updated technical architecture Portal JetSpeed SOAP Ontology Product Catalogue mgt Cultural Heritage Data mgt Connector TextML Server dbXML MySQL REGNET Final Project Review

More Related