Scribd
Upload
4 views4 pages

java_rmi

Java RMI (Remote Method Invocation) allows objects in different Java Virtual Machines (JVMs) to communicate and invoke methods on each other, facilitating the development of distributed applications. An RMI application consists of a server program that creates remote objects and a client program that invokes methods on these objects via a registry. Key components include the transport layer, stub, skeleton, and remote reference layer, which manage requests and responses between the client and server, while also handling parameter marshalling and unmarshalling.

Uploaded by

mishraroxx7979
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
4 views4 pages

java_rmi

Java RMI (Remote Method Invocation) allows objects in different Java Virtual Machines (JVMs) to communicate and invoke methods on each other, facilitating the development of distributed applications. An RMI application consists of a server program that creates remote objects and a client program that invokes methods on these objects via a registry. Key components include the transport layer, stub, skeleton, and remote reference layer, which manage requests and responses between the client and server, while also handling parameter marshalling and unmarshalling.

Uploaded by

mishraroxx7979
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 4

JAVA RMI Java RMI

RMI stands for Remote Method Invocation. It is a mechanism that allows an object residing
in one system (JVM) to access/invoke an object running on another JVM.

RMI is used to build distributed applications; it provides remote communication between Java
programs. It is provided in the package java.rmi.

In an RMI application, we write two programs, a server program (resides on the server) and
a client program (resides on the client).

Inside the server program, a remote object is created and reference of that object is
made available for the client (using the registry).

The client program requests the remote objects on the server and tries to invoke its
methods.

The following diagram shows the architecture of an RMI application.

4
Java RMI

Let us now discuss the components of this architecture.

Transport Layer This layer connects the client and the server. It manages the
existing connection and also sets up new connections.

Stub
the client system; it acts as a gateway for the client program.

Skeleton stub communicates


with this skeleton to pass request to the remote object.

RRL (Remote Reference Layer)


made by the client to the remote object.

The following points summarize how an RMI application works:

When the client makes a call to the remote object, it is received by the stub which
eventually passes this request to the RRL.

When the client-side RRL receives the request, it invokes a method called invoke() of
the object remoteRef. It passes the request to the RRL on the server side.

The RRL on the server side passes the request to the Skeleton (proxy on the server)
which finally invokes the required object on the server.

The result is passed all the way back to the client.

Whenever a client invokes a method that accepts parameters on a remote object, the
parameters are bundled into a message before being sent over the network. These
parameters may be of primitive type or objects. In case of primitive type, the parameters are
put together and a header is attached to it. In case the parameters are objects, then they are
serialized. This process is known as marshalling.

At the server side, the packed parameters are unbundled and then the required method is
invoked. This process is known as unmarshalling.

5
Java RMI

RMIregistry 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). These are registered using a unique name known as bind name.

To invoke a remote object, the client needs a reference of that object. At that time, the client
fetches the object from the registry using its bind name (using lookup() method).

The following illustration explains the entire process:

Following are the goals of RMI:

To minimize the complexity of the application


To preserve type safety

6
Java RMI

Distributed garbage collection


Minimize the difference between working with local and remote objects

You might also like