1. CROSS - X The Cross Platform Explorer By: E. Susheel Chandar M. Guna Sekaran CROSS - X Internal Guide Mr.T. Ravi.,M.E. Cross -X

2. Introduction Objective To develop a tool that is capable of accessing file systems of Heterogeneous Platforms in a network Existing Systems All existing systems are used to access or share files between particularly any two platforms For Example, SAMBA SERVICE, is used to share the files of a Linux System in a windows system Proposed System The proposed system is intended to break this drawback of sharing between any two specific platforms and gives a solution that gives access to any file system from any platform Introduction

3. System Data Flow Model Server RMI Reg @ 3030 Client 192.168.0.2 RMI Reg @ 2020 User: usr1 Client 192.168.0.3 RMI Reg @ 2020 User: usr2 Client 192.168.0.3 RMI Reg @ 2020 User: usr3 a)Looks for the ObjectLooks for the Object b)Gets the Remote ObjectGets the Remote Object c)Calls Fn to Register itself to ServerCalls Fn to Register itself to Server The Domain Server with the RMI Registry is started at port no 3030 Gets the no of Registered clients using the Remote Object 1)Looks for JNDI ObjectLooks for JNDI Object 2) Gets the Remote Object Gets the Remote Object 3)Authenticates using API (Windows API “ Logon User”)Authenticates using API (Windows API “ Logon User”) XML Data Transfer System Data Flow Model

4. System Architecture Three Tier Architecture GUI TIERBUSINESS TIERINTEGRATION TIER FORM OBJECTS FORM ACTION VALUE OBJECTS BUSINESS DELEGATE FACTORY BUSINESS DELEGATE OBJECTS REMOTE INTERFACE UNICAST OBJECTS DAO OBJECTS DAO FACTORY REMOTE OBJECTS System Architecture

5. Modules  SERVER MANAGEMENT MODULE  AUTHENTICATION MODULE  EVENT MODULE  HAND OVER MODULE Modules

6. Server Management Module The functionalities of this module is To maintain the particulars of the clients that are currently active in the network To allow a client to register itself to the server To inform the registration of a new client or the removal of a client to all the active clients that are connected to the server. Server Management Module

7. Authentication Module The functionality of this module is To do remote system authentication before entering into the other machine This can be done using APIs that allows for the verification of system usernames and Passwords, “User Logon” is an Win32 API that allows us to check for the existence of a particular username and password in a windows system Authentication Module

8. Event Module The Functionality of this module is To Contact the client systems and place a request for the access of the files when an call event occurs in the local machine. The file information are transformed in the form of XML data between the systems The Mapping of remote files to appropriate applications Event Module

9. Hand Over Module The functionality of this module is To transfer the information of the files requested by another client system via the Event Module. The Hand Over module in the client system gets the XML data and parses it to get the appropriate data. Hand Over Module

10. Modules Interconnectivity SERVER MANAGEMENT MODULE Class CrossXServer Interface ClientRegister Class ClientRegisterImpl AUTHENTICATION & HAND OVER MODULE Class CrossXClient Interface ClientAcceptor Class ClientAcceptorImpl Class AuthenticateUser AuthenticateUser.h AuthenticateUser.cpp JNI Modules Interconnectivity

11. Class CrossXClientBD Class CrossXClientFactory Class CrossXEventBD Class FileSystemFactory Class FileSystemDAO Class ClientOpenFrame Class CleitnOpenEvent Class FilesPanel Class FolderPanel Class FolderPanelEvent Class FilesPanelEvent EVENT MODULE Modules Interconnectivity

12. Percentage of Completion Finished the Phases of Analysis and System Design. Implementation of Server and Authentication Module in Process. Covered nearly 40 – 50 % of the Overall Project. Percentage of Completion

13. Thanks You Thank You