One of the best-kept secrets of the JINI community is Jini Extensible Remote Method Invocation (JERI), which was released as part of JINI 2.0. JERI is really useful and effective, and comes with a lot of cool and exiting features.

JERI is Jini Extensible Remote Invocation, a new implementation of the RMI programming model. So it is on par with RMI's native JRMP protocol. It is also on par with RMI/IIOP in the sense that all of these are implementations of the Java RMI programming model. However, they all use different protocols underneath and have different protocol stacks.

The salient features of the Jeri Network Technology are:

·         Can be customized seamlessly

·         Support for integrated security and non TCP based transport

The JERI infrastructure basically has three layers.

·         The Marshalling Layer

·         The Object Invocation Layer

·         The Messaging Layer

Let us now understand what each of these layers relates to. The marshalling layer is responsible for marshaling of arguments and return values of methods. The Object Invocation Layer is responsible for identifying the remote object that will be used to make a remote call. The Messaging Layer is simply a request-response layer that is responsible for transporting the bytes.