Eldas 1.0 Enterprise Level Data Access Services Design Issues, Implementation and Future Development Davy Virdee

2 Contents 1.Introduction 2.Design Issues and Considerations 3.Current Eldas Implementation 4.Future Eldas Functionality 5.Summary and Contacts

3 Introduction: Motivation DAIS-WG –Grid Data Service Specification –Data: relational dbs; XML dbs; file systems Service Creation SOAP / HTTP Source 1 Factory Client 1 Client 2 Client 3 Client n Service 1 Service n Service 2 Service 3 Source 2 Source 3 Source n API Interactions

4 Introduction: Standards Web Services –Industry standards OGSI/OGSA –Grid Service enabled using GT3 WSRF –Replacement for GT3

5 Introduction: Web vs Grid Services Web Services –services exposed via platform and language independent interfaces –interface described using WSDL –communication via SOAP/HTTP Grid Services –Web Services plus identity, state and lifetime

6 Eldas Server Introduction: User View Simplified non Grid-specific user view API Interactions Source 1 Client 1 Client 2 Client 3 Client n Source 2 Source 3 Source n SOAP / HTTP

7 Design Issues and Considerations For user adoption of Eldas –Ease of Use –Robustness –Extensibility –Multiple Data Access –Machine Independence –Interface Independence

8 Current Eldas Implementation Eldas 1.0 –Easy to Use –Robust –Extensible –Multiple Data Access –Machine Independent –Interface Independent Tooling/Client Effort Extensive TestingModular DesignJ2EETiered Architecture

9 Current: Easy to Use Download Unpack Deploy and configure Run

10 Current: J2EE J2EE technologies facilitates –Robust software (uses EJBs) –Extensible designs –Machine Independence Presentation Layer JSP/ Servlets Data Layer Typically RDBMS Application or Business Layer Beans, EJBs (Web Container)(EJB Container)(External Data)

11 Current: Interface Independent Presentation layer –Web Services –Grid Services OGSA or WSRF –Other interfaces Eldas Server Eldas Core Web Services Client Data Source Web Services OGSA Grid Services WSRF Grid Services Other Interface Other Client Data Source Grid Services Client

12 Current: Data Access Eldas 1.0 –MySQL Modular Design –easy extension –e.g. DB2, SQLServer

13 Current: Clients Command Line Interfaces –Grid Services Bulk and Streaming –Web Services Graphical Query Tool –Grid Services, Bulk and Streaming

14 Summary: Current Eldas 1.0 Implementation –Easy to Use –Robust and Extensible –Machine and Interface Independent –Multiple Data Access –Multiple Clients

15 Future Eldas Functionality Data Resources –MySQL, DB2, Oracle, Postgres, SQLServer –Flat files, Binary (using BinX) Application Servers –JBoss, WebSphere, Security –GSI Message Level Security –HTTPS Data Transport Joins Stored Database Procedures Stateful Web Services WSRF

16 Summary: Contacts Website: –Eldas 1.0 available for download –Eldas 1.1 available Autumn 2004 –Eldas 2.0 (WSRF) Early 2005 Support:

17 Demonstration: Prerequisites Java JRE –Download and install Globus Toolkit –Download and unpack JBoss Application Server –Download and unpack MySQL Database Driver –Download

18 Demonstration: Server Deploy Server unpack deploy configure Run UnpackEldasServer.jarSelect unpack folder Run EldasServer.jarIdentify GT3 distributionIdentify JBoss distribution Enter db nameIdentify MySQL driverEnter db server IPEnter db server port

19 Demonstration: Clients Install clients unpack install Run UnpackEldasClients.jarSelect unpack folder Run EldasClients.jarIdentify GT3 distribution Select install folder

20 Demonstration: Client - DB local client – remote db –via local server –via remote server JDBC SOAP / HTTP Sanchez Example MySQL Database Laptop Eldas Client Laptop Eldas Server Sanchez Eldas Server

21 Demonstration: Client - DB local client – remote db –via local server –via remote server