2adapt itself to the changing environment. Hence, the mobileclients usually need to have the ability to interact with variousnetworks, services, and security policies as they move from oneplace to another.In this paper, we discuss the issues involved in mobileaccess to grid services and then present grid computingenvironment architecture based on middleware which providessupport and management infrastructure for delegation of jobs tothe grid, a light-weight security model, offline processing,adaptation to network connectivity issues etc. The proposedsystem enables heterogeneous mobile devices to access gridservices in a secure manner and also suggests security policyapplications and security management infrastructure foraccessing grid resources.II.
ARCHITECTUREThe grid middleware is integrated with functions thatfacilitate the management of data mining and data transfer .We use a mobile agent environment that manages the user(mobility, profile, etc.) and the issues related with theheterogeneity of the devices. First of all, let us analyze theinterfacing between the user (wireless) and the wired zone. Afixed agent (Personal Agent) will be present in every mobiledevice (PDA, Laptop). The Personal Agent will have the task of managing the wireless device, by monitoring resources (battery,memory, CPU, display, etc.) and position (through GPS, forinstance) within the wireless area. When a user enters thewireless area, an agent (User Agent) is created in thecorresponding Access Point. This agent will represent the userwhile he/she remains connected to the network. The User Agentwill be able to communicate with the Personal Agent present inthe device, in order to obtain all the information needed. Anytime the user moves (by changing his/her Access Point) the useragent will follow him/her, by migrating to the new Access Point.The User Agent will therefore act as an intermediary betweenthe mobile device and the grid resources present in the wiredarea. As we can see in Figure 1 each node of the Grid network will consist of a three-level architecture. The lowest one is thelevel that provides the grid basic services (resource management,security, distributed access). If the Globus middleware is used,the main services will be: the Globus Resource ManagementArchitecture (GRAM), the Grid Security Infrastructure (GSI),the Grid Information Service (GIS), and the Globus Access toSecondary Storage (GASS).
Discovery is the process of finding Web services with agiven capability. In general, discovery requires that Webservices advertise their capabilities with a registry, and thatrequesting services query the registry for Web services withparticular capabilities. The role of the registry is both to storethe advertisements of capabilities, and to perform a matchbetween the request and the advertisements. In this section, wewill describe how Ontology Web Language for Services (OWL-S) can be used to add capability matching to UniversalDescription, Discovery and Integration (UDDI), the de-factostandard discovery registry for Web Services. The autonomicmiddleware which enables mobile devices to access gridservices is managed by employing a Universal Description,Discovery and Integration, or UDDI  registry whose goal isto create an Internet wide network of registries of Web services.The composition of the current web services may not providesufficient facilities to represent an autonomic behavior or tointegrate them seamlessly with other autonomic components.but with the advent of semantic web service technologies likeOntology Web Language for Services, or OWL-S , itbecomes possible to provide a fundamental framework forrepresenting and relating devices and services with their policiesand describing about their functionalities and capabilities.As the middleware service is in place and information isexposed, other devices would be able to discover and providesupport to use the API in the UDDI specification (UDDI version3.0.2)  which is defined in XML, enclosed in a SOAPenvelope and sent over HTTP. SOAP is fundamentally astateless, one-way message exchange paradigm, but applicationscan create more complex interaction patterns (e.g.,request/response, request/multiple responses, etc.) by combiningsuch one-way exchanges with features provided by anunderlying protocol and/or application-specific information.SOAP is silent on the semantics of any application-specific datait conveys, as it is on issues such as the routing of SOAPmessages, reliable data transfer, etc. However, SOAP providesthe framework by which application-specific information maybe conveyed in an extensible manner. Also, SOAP provides afull description of the required actions taken by a SOAP node onreceiving a SOAP message (SOAP Version 1.2 Part 0) .
(IJCSIS) International Journal of Computer Science and Information Security,Vol. 8, No. 1, April 2010239http://sites.google.com/site/ijcsis/ISSN 1947-5500