The REGNET Demonstration Trial service D10

1
The REGNET Demonstration (Trial service) D10
2
Contents

• Scope
• Integration design patterns
• Broker and Connector

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.valtec
  h.fr8080/jetspeed

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.

6
Integration architecture design patterns
7
Document exchange EDI
Partner A
Partner B
Back end Application 2
Translation Tier
Partner Tier
1N
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
8
Exposed Application MOM
Partner A
Partner B
Partner Tier
1N
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
9
Exposed Business Services Web Services
Partner A
Partner B
Back end Application 2
N1
Exposed Business Services Tier
Partner Tier
1N
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
10
Managed public processes ebXML
Partner A
Partner B
Back end Application 2
N1
Public Process Rules Tier
Partner Tier
1N
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
11
Managed Public and Private Processes
Partner A
Partner B
Public Process Rules Tier
Private Process Rules Tier
Back end Application 2
N1
N1
asynch sync
1N
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
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

14
REGNET Broker
Implements getCatalogs() storeCatalog() listCa
talog() getItem() storeItem()
GUI
EShop
TextML connector
PCM connector
PCM
REGNET Broker
Data Entry
SOAP
SOAP
SOAP
MySQL
TextML
Z39.50 server
15
Updated technical architecture
Portal JetSpeed
SOAP
Ontology
Product Catalogue mgt
Cultural Heritage Data mgt
Connector
TextML Server
dbXML
MySQL