Meaning of RMI

Definition of RMI in networking and aplication

---

RMI is an extension of the local method invocation that allows an object that lives in one process to invoke the method object in another process. (George Coulouris p. 166). RMI is a remote method call technique which more is generally better than RPC. RMI uses object-oriented programming paradigm (Object Oriented Programming). RMI allows us to send the object as a parameter of the remote method. With the permissibility of a Java program to call methods on remote objects, RMI allows users to develop distributed Java applications on the network. RMI applications often consist of two separate programs of server and client. Application servers typically make some sort of remote objects, provide references to those objects that can be accessed, as well as client waiting menginvoke / invoke method of remote objects. Remote client application to get a reference to one or more remote objects in the server and run method of the object. RMI provides the mechanism by which the server and client communicate danmemberikan mutual information. Such applications are often called distributed object applications.

Standard Java RMI system architecture with local RMI registries in FMC notation (www.fmc-modeling.org).

• RMI server object (re)binds itself to the local RMI registry running on the same machine—(re)binding to a remote RMI registry is prohibited (AccessException).
• RMI clients lookup the specific RMI registry to get a remote reference (a client stub), to the server object. 
• RMI client invokes methods on the remote server object via the client stub.

2. Concept

Distributed object applications often do the following:

• locating remote objects: Applications can use one of two mechanisms to obtain references to remote objects. Applications can register a remote object with the RMI naming facilities (naming facility) that is rmiregistry or her application can pass and return remote object references as part of normal operation.

• Communicate with remote objects: Details of communication between remote objects are handled by the RMI, the programmer remote communication looks like a standard Java method invocation.

• Call (load) in the bytecode for object-pass: Because RMI allows a caller () to pass to object to a remote object, RMI objects provide the mechanisms required to load the object code, as well as transmit data 

The following illustration describes the RMI distributed application that uses the registry to obtain references to remote objects. Server calls registry to associate (bind) a name with the remote object. Client looking for a remote object with its name on the registry server and to invoke a method of the object. This illustration also shows the RMI systems using the Web server to call the class bytecodes, from server to client and from client to server, for objects that are needed.

======================================= Don't forge Like us And Give Comment

Your support is valuable to me
Searching for