RMI

Remote Method Invocation (RMI) is the process of activating a method on a remotely running object. RMI offers location transparency in the sense that it gives the feel that a method is executed on a locally running object.

RMI has at least three protocol implementations:

Java Remote Method Protocol(JRMP), Internet Inter ORB Protocol(IIOP), and Jini Extensible Remote Invocation(JERI). These are alternatives, not part of the same thing, All three are indeed layer 6 protocols for those who are still speaking OSI reference model.

The RMI architecture is based on one important principle: the definition of behavior and the implementation of that behavior are separate concepts. RMI allows the code that defines the behavior and the code that implements the behavior to remain separate and to run on separate JVMs.

The RMI is built on three layers.

a. Stub and Skeleton layer

This layer lies just beneath the view of the developer. This layer intercepts method calls made by the client to the interface reference variable and redirects these calls to a remote RMI service.

b. Remote Reference Layer.

This layer understands how to interpret and manage references made from clients to the remote service objects. The connection is a one-to-one (unicast) link.

c. Transport layer

This layer is based on TCP/IP connections between machines in a network. It provides basic connectivity, as well as some firewall penetration strategies.

Exports the remote object to make it available to receive incoming calls, using the particular supplied port. If port not specified receives calls from any anonymous port.

Java RMI-IIOP provides a mechanism to narrow the the Object you have received from from your lookup, to the appropriate type. This is done through the javax.rmi.PortableRemoteObject class and, more specifically, using the narrow() method.

The UnicastRemoteObject class provides support for point-to-point active object references using TCP streams. Objects that require remote behavior should extend UnicastRemoteObject.

RMI uses a layered architecture, each of the layers could be enhanced or replaced without affecting the rest of the system. The details of layers can be summarised as follows:

1. Application Layer: The client and server program

2. Stub & Skeleton Layer: Intercepts method calls made by the client/redirects these calls to a remote RMI service.

3.Remote Reference Layer: Understands how to interpret and manage references made from clients to the remote service objects.

4.Transport layer: Based on TCP/IP connections between machines in a network. It provides basic connectivity, as well as some firewall penetration strategies.

JRMP(java remote method protocol)

a. MalFormedURLException

b. NotBoundException

c. RemoteException

Using list method of Naming Class.

Yes. Those methods behave as normal java methods operating within the JVM.

An RMI "service" could well be any Java method that can be invoked remotely. The other service is the JRMP RMI naming service which is a lookup service.

AlreadyBoundException is thrown by bind(String name) method when a remote object is already registered with the registry with the same name.

Note: rebind method doesn't throw AlreadyBoundException because it replaces the existing binding with same name.

Binding is a process of associating or registering a name for a remote object that can be used at a later time to look up that remote object. A remote object can be associated with a name using the Naming class's bind or rebind methods.

The Naming class provides methods for storing and obtaining references to remote objects in the remote object registry.

bind method(String name) binds the specified name to a remote object while rebind(String name) method rebinds the specified name to a new remote object,any existing binding for the name is replaced.

1099

The Remote interface serves to identify interfaces whose methods may be invoked from a non-local virtual machine. Any object that is a remote object must directly or indirectly implement this interface. Methods that are to be invoked remotely must be identified in Remote Interface. All Remote methods should throw RemoteException.

Yes. The JDK 1.2 support the dynamic class loading.