Jini Services Manager

Abstract

On January 25, 1999, Sun launched JINITM technology with a global event in San Francisco including a number of partner announcements. Based on this technology, I have been assigned the task of implementing a JINI Service Manager. This project basically has three main players i.e., a client for each service, a service registering service, and core distributed services. These three players are used in a distributed environment using JINI architecture. JINI architecture requires services be registered with a lookup service (provided by JINI). On request, for a particular service, from the remote client, lookup service gets activated and returns a proxy object (stub) of that service. Once the client gets the stub, it can call any of the methods of the service. These methods are executed remotely where they are registered. The client invokes those methods and passes input arguments (if any) to them. In return the remote client can get the data returned by the method. This architecture helps us start and stop services remotely, which are accessible by the distributed clients. The nitty gritty of the networking, security and transactional services are handled by JINI.