280 likes | 397 Views
A Uniform Access to Metacomputing File System. Fajin Wang TTU SORCER Lab. Agenda. 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation. 1. Problem. 1.1) Two file systems in SORCER 1.1.1) SORCER. Service Registry. Discovery Lookup.
E N D
A Uniform Access to Metacomputing File System Fajin Wang TTU SORCER Lab
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation
1. Problem 1.1) Two file systems in SORCER 1.1.1) SORCER Service Registry Discovery Lookup Discovery Publish Service Requestor Service Provider Bind Execute SOA
1. Problem Service Service Service Service Service 1.1) Two file systems in SORCER 1.1.1) SORCER Federated S2S environment to ... Build new services Convert legacy apps to dynamic SORCER services (J2EE™ technology) Assemble SORCER services together (RMI, Jini, Rio, JXTA, WS technologies) Create modern clients accessing services
1. Problem 1.1) Two file systems in SORCER 1.1.2) SILENUS User Interface Metadata Store SORCER Optimizer Byte Store WebDAV Adapter
1. Problem 1.1) Two file systems in SORCER 1.1.3) FileStore SORCER FileStore User Interface DBMS Servlet Engine Browser
1. Problem 1.2) Two file systems in SORCER 1.2.1) Four different user agents are available: FileStore: Web-based document manager SILENUS: Service UI, SILENUS MIDP user agent, SILENUS NFS adapter; both: Programmatic API 1.2.2) No single direct access point and friendly user interface to the both files systems.
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Shedule 5. Benefits 6. Thesis validation
2 Objective A uniform access to shared file systems in the SORCER environment
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation
3 Methodology 3.1) Approach requirements 3.1.1) Distributed 3.1.2) Interoperable 3.1.3) Support authoring/versioning 3.2) Approaches 3.2.1) WebDAV protocol 3.2.2) Service provider with Service UI
3 Methodology 3.3) WebDAV protocol 3.3.1) Web-based Distributed Authoring and Versioning - Goal: “Define the HTTP extensions necessary to enable distributed web authoring tools to be broadly interoperable, while supporting user needs” - Make the web a writable, collaborative medium - Create an Internet File System - Enable interoperability of tools for distributed web authoring
3 Methodology • 3.3) WebDAV protocol • 3.3.2)Server • Microsoft: IIS 5/6, Exchange 2000, Sharepoint • Apache: mod_dav , Jakarta Slide • Oracle: Internet File System • Adobe: InScope • W3C: Jigsaw • IBM: DAV4J (DeveloperWorks) • …… • Client • Remote File Access: • Apple: Mac OS X webdavfs • Microsoft: Windows Web Folders • DAV Explorer • Application Software: • Microsoft: Office 2000/XP (Word, Excel, PowerPoint, Publisher) • Adobe: Photoshop 6, Illustrator 10, Acrobat 5, In Design 2 • Web Site Authoring:Adobe: Go Live 5; Macromedia: Dreamweaver 4 • XML editors:Documentor, XML Spy, XMetal • ……
3 Methodology 3.3) WebDAV protocol 3.3.3) Design DAV Explorer Slide Server SILENUS WebDAV Adapter FileStore
3 Methodology 3.4) Service UI 3.4.1) A user interface - "attached" to a Jini technology service, using a loosely coupled architecture. - interfaces with the backend service through the service's proxy. Service Registry Service Requestor Service UI UI Factory Service Provider Proxy
3 Methodology 3.4) Service UI 3.4.2) Design - Use cases
3 Methodology 3.4) Service UI 3.4.2) Design - Components
3 Methodology 1 Browse 3.4) Service UI 3.4.2) Design Communication diagram - Browse dfs:DocumentFileStore mds:MetadataStore ui:SorcerExplorer 1.1.2a expandNode(Msuid):Map 1.1.2b getDirectories( DocumentDescriptor) : DocumentDescriptor 1.1.3 getDirectoryContent( DocumentDescriptor) : DocumentDescriptor 1.1 expandNode(Uri):Map 1.1.1 expandNode(Uri):Map adapter:SorcerExplorerAdapter proxy:SorcerExplorerFacade Figure 2 Communication diagram for Use Case "Browse"
3 Methodology 3.4) Service UI 3.4.2) Design Communication diagram - Download 3 download 3.1.2a.1 openInputFileChannel( ) :ReadByteChannel explorer:SorcerExplorer accessor:FileChannelAccessor 3.1.2a.2 openReadable(Bsuid) :InputFileChannelAccessor 3.1.2b.1 read(File):void 3.1 download(Uri):Object (InputFileChannelAccessor/InputStreamProxy) bs:ByteStore dfs:DocumentFileStore adapter:SorcerExplorerAdapter 3.1.1 download(Uri):Object (InputFileChannelAccessor/InputStreamProxy) 3.1.2b getInputDescriptor (DocumentDescriptor) :DocumentDescriptor 3.1.2a download(Msuid) :InputFileChannelAccessor proxy:SorcerExplorerFacade coord:Coordinator
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation
Schedule Accomplished Literature review Review and analyze Jini Network Technology, service UI, WebDAV, SILENUS façade, and SORCER FileStore service; Developed uniform access methodology and relevant use cases for accessing metacomputing file system; Built a prototype to verify the concept of uniform access methodology; Feasibility implementation of WebDAV adapter, Service UI for SILENUS
Schedule 02/08/07 Proposal presentation 02/11/07 Design of WebDAV adapter 02/14/07 Design of Service UI 02/18/07 Model Verification 02/20/07 Implementation of WebDAV adapter 03/01/07 Implementation of Service UI 03/20/07 Validation of use cases 03/25/07 Deploy in SORCER 03/29/07 Defense
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation
Benefits 1. Friendly and intuitive graphical user interface; 2. Non confusing single access point to both file systems; 3. Reduction of effort-time-cost through work simplification; 4. Improved file access quality through work simplification; 5. WebDAV enables distributed web authoring tools to be broadly interoperable; 6. Service UI offers Zero - install; 7. Framework is extensive.
Agenda 1. Problem statement 2. Objective 3. Methodology 4. Schedule 5. Benefits 6. Thesis validation
Proposed Methodology 1. WebDAV 2. Service UI Service requestor WebDAV Client SILENUS Sorcer Explorer WebDAV Adapter SorcerExplorer Facade WebDAV Server FileStore Service Registry
Thesis Validation 1. Upload a file from the WebDAV client, check this file on Service UI; Download it, check if data has been changed. 2. Upload a program (e.g. proth), check if it can be picked up by a Caller