Y
 


 


  





 



 









CONTENTS:

! Introduction
! Requirement Analysis
! System Analysis
! Block Diagram
! Working
! Applications and scope
! Conclusion
! References
Server Requirements
! GUI not available or optional.
! Ability to reconfigure and update both hardware
and software to some extent without restart.
! Advanced backup facilities to permit regular and
frequent online backups of critical data.
! Transparent data transfer between
different volumes or devices.
! Automation capabilities such as services in
Windows.
! Tight system security, with advanced user,
resource, data, and memory protection.
2obile Requirments
Requirments::
! CLDC(Connected Limited Device Configuration) is
designed for devices that have limited processing power,
memory, and graphical capability.
! 16-bit or 32-bit CPU with a clock speed of 16 2
or
higher
! At least 192 KB total RA2 available to the Java platform
! Low power consumption, often operating on battery
power
! Connectivity to some kind of network, often with a
wireless, internet connection and limited bandwidth
INTRODUCTION

SYSTE2 ANALYSIS

! General Client-Server 2odule.

! Remote 2ethod Invocation

General Client-
Client-Server 2odule

CLIENT SERVER
Õ


Õ

 

Õ





Õ








Õ


Õ





Working:
! GUI for LAN
administrator
! IP addresses of all
the clients will be
provided to the user
! IP addresses will have
options to perform
particular task on
that particular client
2odules:
! System applications: Logoff, Restart, and
Turn Off.

! File Operations: Delete, Copy, Rename.

! GetProcess list , kill process ,change.

Continued«.
Remote 2ethod Invocation(R2I)

! Remote 2ethod Invocation (R2I) allows

a Java object that executes on one
machine
to invoke a method of a Java object that
executes on another machine. This is an
important feature, because it allows you
to build distributed applications.
R2I and other technologies
! CORBA (Common Object Request Broker
Architecture) was used for a long time
- CORBA supports object transmission between
virtually any languages
- Objects have to be described in IDL (Interface
Definition Language), which looks a lot like C++
data definitions
- CORBA is complex and flaky
- CORBA has fallen out of favor
! 2icrosoft supported CORBA, then CO2,
now MNET
! R2I is purely Java-specific
- Java to Java communications only
- As a result, R2I is much simpler than CORBA 11
 What is needed for R2I
! Java makes R2I (Remote 2ethod Invocation)
_
 easy, but there are some extra steps
! To send a message to a remote ´server object,µ
- The ´client objectµ has to _
 the object
ë Do this by looking it up in a registry
- The client object then has to marshal the
parameters (prepare them for transmission)
ë Java requires Serializable parameters
ë The server object has to unmarshal its parameters, do its
computation, and marshal its response
- The client object has to unmarshal the response
! 2uch of this is done for you by special
software
12
 Terminology
! A remote object is an object on another computer
! The client object is the object making the request (sending
a message to the other object)
! The server object is the object receiving the request
! As usual, ´clientµ and ´serverµ can easily trade roles (each
can make requests of the other)
! The rmiregistry is a special server that looks up objects
by name
- opefully, the name is unique!
! rmic is a special compiler for creating stub (client) and
skeleton (server) classes

13
 jemote vs. Serializable
! A jemote object lives on another computer (such as the
Server)
- You can send messages to a jemote object and get
responses back from the object
- All you need to know about the jemote object is its
interface
- Remote objects don·t pose much of a security issue
! You can transmit a i
 of a Serializable object between
computers
- The receiving object needs to know how the object is
implemented; it needs the class as well as the interface
- There is a way to transmit the class definition
14
 Remote interfaces and class
! A jemote class has two parts:
- The interface (used by both client and server):
ë 2ust be public
ë 2ust extend the interface ava.rmi.jemote
ë Every method in the interface must declare that it
throws ava.rmi.jemoteException (other
exceptions may also be thrown)
- The class itself (used only by the server):
ë 2ust implement the jemote interface
ë Should extend
ava.rmi.server.UnicastjemoteObect
ë 2ay have locally accessible methods that are not in its
jemote interface
15
Applications
2ain Objective:

1.LAN 2onitoring

2.LAN Controlling
Scope Of System
! The Various Objectives may be pointed
as:
! The 2ain Objective of the System is to
develop a User Friendly 2anagement
System with Good 2enus, Input Screens
and Clear Reports,this would be easy to
Operate.
 Continued«
! To Save the Administrative Job of
monotring & controlling by providing him
this 2obile application.
! Giving Immediate Information of the
Various Processes.
Future Scope
! This is the future.
References
! Complete Reference for Java.
! Thinking in Java-Bruce Eckel
! Software Engineering a practitioner
Approach-Roger S. Pressman.
! www.wikipedia.com
! www.google.com