How to start rmi registry in windows

RMI registry is a namespace on which all server objects are placed. Each time the server creates an object, it registers this object with the RMIregistry (using bind() or reBind() methods). At that time, the client fetches the object from the registry using its bind name (using lookup() method).

A remote object registry is a bootstrap naming service that is used by RMI servers on the same host to bind remote objects to names. The registry is typically used to locate the first remote object on which an application needs to invoke methods.

The RMI registry is a simple server-side name server that allows remote clients to get a reference to a remote object. It typically is used to locate only the first remote object an RMI client needs to talk to. Then, that first object in turn, provides application-specific support getting references for other objects.

RMI Example. In the rmi application, both client and server interacts with the remote interface. The client application invokes methods on the proxy object, RMI sends the request to the remote JVM. The return value is sent back to the proxy object and then to the client application.

An RMI server is a program that hosts remote objects. An RMI registry is a separate program that binds remote object names to instances. An RMI server makes remote objects accessible to clients by registering them in the registry; clients then obtain access via that same registry.

(Remote Method Invocation) A standard from Sun for distributed objects written in Java. RMI is a remote procedure call (RPC), which allows Java objects (software components) stored in the network to be run remotely.

A typical client program obtains a remote reference to one or more remote objects on a server and then invokes methods on them. RMI provides the mechanism by which the server and the client communicate and pass information back and forth. Such an application is sometimes referred to as a distributed object application.