The server side

In ORB terminology, a server is an application that makes one of its implemented objects available through an ORB instance.

Servant implementation
The implementations of the remote object can either inherit from javax.rmi.PortableRemoteObject, or implement a remote interface and use the exportObject() method to register themselves as a servant object. In both cases, the servant has to implement the Sample interface. Here, the first case is described. From now, the servant is called SampleImpl.
Tie generation
You must put an interfacing layer between the servant and the ORB code. In the old RMI (JRMP) naming convention, skeleton was the name given to the proxy that was used on the server side between ORB and the object implementation. In the RMI-IIOP convention, the proxy is called a Tie.
Servant binding
The steps required to bind the servant are described.
Processing a request
The server ORB uses a single listener thread, and a reader thread for each connection or client, to process an incoming message.

Parent topic: How the ORB works