Remote Method Invocation in Java: Bennie Lewis EEL 6897

Remote Method Invocation in Java
Bennie Lewis
EEL 6897
AGENDA
• Introduction
• What is RMI
• The Goals of RMI
• The RMI system architecture
• How RMI works
• Distributed garbage collection
• Security
• Conclusion
• Questions
Introduction
RMI
Java’s RMI is an alternative to low level sockets. A remote method
invocation is a form of the RPC that is available on other systems.
Instead of creating objects on local machines you create some of
the objects on other machines an you communicate with those
objects as you would normally would with local objects
WHAT IS RMI
• RMI is a core package of the JDK 1.1 and above that can be used to
develop distributed application.
• It enables software developers to write distributed applications in

which the methods of remote objects can be invoked from other JVMs
The Goals of RMI
• Support seamless remote invocations on objects in different java
virtual machines.
• Support callbacks from servers to clients.
• Integrate the distributed object model into the Java language in a
natural way while retaining most of the Java language’s object
semantics.
• Make differences between the distributed object model and the local
java object model apparent.
• Make writing reliable distributed applications as simple as possible.
• Preserve the safety provided by the java sun real time environment.
The RMI system architecture
• The RMI system is built in three layers
• The stub/skeleton layer
• The remote reference layer
• The transport layer

The stub/skeleton layer
• The stub/skeleton layer is the interface between the application layer

and he rest of the system. When a server application is developed.
Stubs and skeletons are generated using the RMI’ rmic compiler, which
generates proxy classes from the servers bytecodes The stub/skeleton
layer transmits data to the remote reference layer via the abstraction of
marshal streams which use objects serialization. Therefore. This layer
does not deal with the specifics of any transport.
The remote reference layer
• The remote reference layer is a middle layer between the stub/skeleton

layer and the transport layer. This layer is responsible for providing the
ability to support varying remote reference or invocation protocols
independent of the client stubs and server skeletons.
The Transport layer
• The transport layer is the low-layer that ships marshal streams between
different address spaces. The transport layer is responsible for setting
up connections to remote address spaces, managing connections,
listening for incoming calls, maintaining a table of remote objects that
reside in the same address space, setting up a connections to this
dispatcher.
How RMI works
• When a client invokes an object implementation from the server the

three layers of RMI come in the play. The most important layer to the
programmer is the stub/skeleton layer. RMI comes with an rmic
compiler that generates stubs and skeletons from user defined remote
interfaces. Basically, stubs are client proxies and skeletons are server-
side entities. Stubs will allow clients to communicate with the other
layers of the system. This is done automatically as you will have to in
inherit from RMI classes.
Example
• package RMI.hello;
• import java.rmi.Naming;
• import java.rmi.RemoteException;
• import java.rmi.RMISecurityManager;
• import java.rmi.server.UnicastRemoteObject;
• public class RMIserver extends UnicastRemoteObject implements Hello

• {
• public RMIserver() throws RemoteException
{
• super();
• }
• public String sayHello()
• {
• return "Bennie Lewis Hello World!";
• }
• public static void main(String args[])
• {
• if(System.getSecurityManager() == null)
• {
• System.setSecurityManager(new RMISecurityManager());
• }
• try
• {
• RMIserver obj = new RMIserver();
• Naming.rebind("//localhost/HelloServer",obj);
• System.out.println("HelloServer bound in registry");

• }
• catch(Exception e)
• {
• System.out.println("RMIserver err: " + e.getMessage());
• e.printStackTrace();
• }
• }
• }
Example cont.
• import java.applet.Applet;
• import java.awt.Graphics;
• import java.rmi.Naming;
• public class RMIclient extends Applet

• {
• String message = "blank";

• Hello obj = null;
• public void init()
• {
• try
• {
• obj = (Hello)Naming.lookup("//" + getCodeBase().getHost() + "/HelloServer");
• message = obj.sayHello();
• }
• catch(Exception e)
• {
• System.out.println("HelloApplet exception:" + e.getMessage());
• e.printStackTrace();
• }
• }
• public void paint(Graphics g)
• {
• g.drawString(message,25,50);
• }
• }
Example cont.
• import java.rmi.Remote;
• public interface Hello extends Remote

• {
• String sayHello() throws RemoteException;
• }
Distributed Garbage Collection
• When stand-alone applications are developed using java, objects that

are no longer referenced by any client are automatically deleted. This
is a desirable feature when developing distributed applications. The
RMI system provides a distributed garbage collector that automatically
deletes remote objects that are no longer referenced by any client.
Security
There are a number of security issues that you should be aware of
when developing mission-critical systems in RMI.
• There is no authentication; a client just requests and object (stub), and

the server supplies it. Subsequent communication is assumed to b from
the same client.
• There is no access control to the objects
• There are no security checks on the RMI registry itself; any caller Is
allowed to make request.
• There is no version control between the stubs and the skeletons,

making it possible for client to use a down-level stub to access a more
recent skeleton breaking release-to-release binary compatibility
Conclusion
• RMI is an alternative to low level sockets
• RMI is a core package of the JDK 1.1 and above that can be used to
develop distributed application.
• The RMI system is built in three layers The stub/skeleton layer, The
remote reference layer, The transport layer
References
• Qusay H. Mahmoud,(1999). Distributed Programming with Java.

Greenwich CT: Manning Publications Co.
• http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp
Questions

Remote Method Invocation in Java: Bennie Lewis EEL 6897

Uploaded by

Copyright:

Available Formats

Remote Method Invocation in Java: Bennie Lewis EEL 6897

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Remote Method Invocation in Java: Bennie Lewis EEL 6897

Uploaded by

Copyright:

Available Formats

Remote Method Invocation in Java

• The Goals of RMI

• The RMI system architecture

• How RMI works

• Distributed garbage collection

• It enables software developers to write distributed applications in

• The RMI system is built in three layers

• The stub/skeleton layer

• The remote reference layer

• The transport layer

• The stub/skeleton layer is the interface between the application layer

• The remote reference layer is a middle layer between the stub/skeleton

• When a client invokes an object implementation from the server the

• public class RMIserver extends UnicastRemoteObject implements Hello

• System.out.println("HelloServer bound in registry");

• public class RMIclient extends Applet

• String message = "blank";

• public interface Hello extends Remote

• When stand-alone applications are developed using java, objects that

• There is no authentication; a client just requests and object (stub), and

• There is no access control to the objects

• There is no version control between the stubs and the skeletons,

• Qusay H. Mahmoud,(1999). Distributed Programming with Java.

You might also like