Where JINI is used?
How JINI works?
JINI is a programming model or architecture which
enables configuration and deployment of
JINI simplifies the addition of devices where each
and every devices can be plugged together to form a
community; a community which can be formed
with minimum configuration, human intervention
and device drivers.
Devices can hardware as well as software written in
java which provide their services through
distributed network interfaces. These devices in JINI
is called “Resource/Service”.
Services joined the network and make their
presence announce to the “lookup Service”.
“Client” use lookup Service to locate resource and
call them to perform their task.
Any hardware and software devices.
Any consumer appliances that can pass
digital information such as it can be a Xerox
machine, coffee machine or a washing
Three users Nabin,
Teddy, Ujjal present
in different location
but connected in a
They can easily share
the resources with
each other with the
help of JINI
The idea of the JINI system developed by Sun
cofounder Bill Joy at Sun Aspen Smallworks R&D lab
Under the leadership of Bill Joy and Jim Waldo
Ann Wollrath, the inventor and designer for Java
Remote Method Invocation (Java RMI)
Ken Arnold, the designer of JavaSpaces™
Bob Scheifler, a principal of the X Consortium and
designer of Lookup/Discovery.
On January 25, 1999, JINI was officially launched
and the technology is available for download
By September 1999, 18,000 click-thru agreement
//downloads of JINI release from Sun‟s web site
Sun currently has agreement with a wide range of
technology companies to develop JINI technology
services, both hardware and software.
Components in JINI:
▪ Are the devices which provide their
functionalities over the network to the clients.
▪ Acts as a broker between Service and Client.
▪ They use the function provided Device(i.e.
JINI is based on look up service, when a device adds
to a network it goes through a add-in protocol
called „discovery and join‟.
The device first locate the look up service and loads
a service register object which will serve as a local
proxy for the look up service.
This service register object implements the look up
service interface and the protocol is used for
communicating between the client and the look ups
The client who wants to use the service locate
the device using the look up service. A service
object representing the service is uploaded in the
requesting client by the look up service.
The Service object implements the service
interface which take care with the remote
implementation with the remote service. The
client may now use the service by invoking
methods on the local service object. Once the
connection is established the look up service is
no more required.
Install the object representing
the service to the client
directly with the
methods on the
No configuration hash less and device drivers.
Device can announce their presence in the network
Same devices and information can shared with
every one present over the network.
Seamless access to local and remote devices.