The Use of OGSA-DAI with DB2 Content Manager  in the eDiaMoND Project M Oevers , B Collins, A Knox, J Williams
Overview <ul><li>eDiaMoND the project </li></ul><ul><li>Strategies for Virtualisation </li></ul><ul><li>How DB2 and CM are...
eDiaMoND Partners
eDiaMoND Functional Model
Strategies for Virtualisation Use II & II4C Expose through OGSA-DAI Investigate DQP
Virtualisation – things to remember <ul><li>Each Breast Care Unit (BCU) to operate independently from others </li></ul><ul...
Query Service Persistent OGSA-DAI Service Persistent Data Layer Grid Layer Grid Layer Client Layer Administration Client S...
How OGSA-DAI is used with DB2 and CM <ul><li>DB2 stores the non-image data in a structured form </li></ul><ul><ul><li>DICO...
CM Grid enablement – What it means <ul><li>Driver Class, e.g.   </li></ul><ul><ul><li>com.ibm.db2.jcc.DB2Driver   </li></u...
The OGSA-DAI Experience <ul><li>OGSA-DAI is extensible </li></ul><ul><ul><li>enough to allow the grid enablement of a data...
Thank You Manfred Oevers [email_address]
Upcoming SlideShare
Loading in …5
×

PPT

439 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
439
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Modalities are CT, MRI, Ultrasound, …
  • PPT

    1. 1. The Use of OGSA-DAI with DB2 Content Manager in the eDiaMoND Project M Oevers , B Collins, A Knox, J Williams
    2. 2. Overview <ul><li>eDiaMoND the project </li></ul><ul><li>Strategies for Virtualisation </li></ul><ul><li>How DB2 and CM are used </li></ul><ul><li>OGSA-DAI enablement of CM </li></ul><ul><li>The OGSA-DAI Experience </li></ul>
    3. 3. eDiaMoND Partners
    4. 4. eDiaMoND Functional Model
    5. 5. Strategies for Virtualisation Use II & II4C Expose through OGSA-DAI Investigate DQP
    6. 6. Virtualisation – things to remember <ul><li>Each Breast Care Unit (BCU) to operate independently from others </li></ul><ul><ul><li>Individual organisations coming together to for a Virtual Organisation </li></ul></ul><ul><li>Data loaded locally in each BCU </li></ul><ul><ul><li>Data is “owned” by the BCU </li></ul></ul><ul><li>Enable read access across all BCUs seamlessly </li></ul><ul><ul><li>Replication or Federation </li></ul></ul><ul><ul><li>DB2 II & II4C </li></ul></ul><ul><li>Remember it’s got to be a Grid (eScience project) </li></ul><ul><ul><li>OGSA-DAI </li></ul></ul><ul><ul><li>Distributed Query Processing (QDP) over OGSA-DAI </li></ul></ul>
    7. 7. Query Service Persistent OGSA-DAI Service Persistent Data Layer Grid Layer Grid Layer Client Layer Administration Client Screening Workflow Viewer Client Worklist Service Transient 1. Query 2. Worklist Create 3. Worklist Consume 4. Retrieve 1 2 3 DB2 Instance Patient ID DICOM ID Content Manager Instance DICOM ID URL – DICOM ID Retrieve Service Persistent OGSA-DAI Service Persistent 4
    8. 8. How OGSA-DAI is used with DB2 and CM <ul><li>DB2 stores the non-image data in a structured form </li></ul><ul><ul><li>DICOM describes an ER model Patient – Study – Series – Image </li></ul></ul><ul><ul><li>Flexible to allow for multiple modalities </li></ul></ul><ul><ul><li>Allow flexibility of data modelling/access control/query rewrite </li></ul></ul><ul><li>CM is used to store and manage the (large 30MB) DICOM files </li></ul><ul><ul><li>Files contain both non-image data and image data </li></ul></ul><ul><ul><li>Identified by DICOM SOP Instance UID </li></ul></ul><ul><ul><li>Flat CM data model (Customer Requirement) </li></ul></ul><ul><li>Both exposed as OGSA-DAI services </li></ul>DICOM – Digital Imaging and Communications in Medicine
    9. 9. CM Grid enablement – What it means <ul><li>Driver Class, e.g. </li></ul><ul><ul><li>com.ibm.db2.jcc.DB2Driver </li></ul></ul><ul><li>Driver URI, e.g. </li></ul><ul><ul><li>jdbc:db2://localhost:50000/SAMPLE </li></ul></ul><ul><li>Connection </li></ul><ul><ul><li>DriverManager.getConnection() </li></ul></ul><ul><li>Metadata </li></ul><ul><ul><li>Table Schema for SQL </li></ul></ul><ul><ul><li>XML schema for XML DB </li></ul></ul><ul><li>Mapping of Grid Certificates to DB user and password </li></ul><ul><li>Datastore object, e.g </li></ul><ul><ul><li>com.ibm.mm.sdk.server.DKDatastoreICM </li></ul></ul><ul><li>Data store name, e.g. </li></ul><ul><ul><li>ICMNLSDB </li></ul></ul><ul><li>Connected Datastore </li></ul><ul><ul><li>Datastore.connect() </li></ul></ul><ul><li>Metadata </li></ul><ul><ul><li>ItemTyes and Attributes </li></ul></ul><ul><ul><li>Could it be treated as an XML DB? </li></ul></ul><ul><li>Mapping of Grid Certificate to CM user and password </li></ul>It was possible to map CM concepts to corresponding JDBC concepts that are exposed in OGSA-DAI configuration files 2 XML files to edit and 2 Java classes to write OGSA-DAI conf/ext points Mapping to CM
    10. 10. The OGSA-DAI Experience <ul><li>OGSA-DAI is extensible </li></ul><ul><ul><li>enough to allow the grid enablement of a datasource that does not quite fit into the relational/XML paradigm </li></ul></ul><ul><ul><li>Chaining of activities, user defined activities </li></ul></ul><ul><li>OGSA-DAI improves developer productivity </li></ul><ul><ul><li>Focus on writing activities </li></ul></ul><ul><ul><li>We have not tried the client toolkit yet </li></ul></ul><ul><li>OGSA-DAI does change </li></ul><ul><ul><li>Some of our code broke due to low level XML issues when upgrading to the latest release </li></ul></ul><ul><li>Will OGSA-DAI support WS-transaction? </li></ul><ul><ul><li>Standard stuff, but important in the real world, compensation is not always an option </li></ul></ul>
    11. 11. Thank You Manfred Oevers [email_address]

    ×