DCE for the HP e3000 (B3821-90003)

49
6 Introduction to RPC
This version of DCE/3000 is based on the OSF DCE version 1.2.1 source
code. It provides the Remote Procedure Call component of the core
services of OSF DCE.
Remote Procedure Call: supports the development of distributed
applications by making requests to remotely networked machines as if
they were local. RPCs also implement network protocols used by clients
and servers to communicate with each other.
The different components of RPC product are:
RPC Runtime Library:
This is the shared library, which provides the
functionality of different RPC APIs. It maintains and
manages memory for the RPC application. Runtime
basically is the transparent layer, which manages the
communication with a remote machine in the network.
Along with the help of IDL, runtime makes the RPC
protocol possible on a heterogeneous network. The data
sent across the network are “Marshalled” before being
sent and “Unmarshalls” the incoming data. The
functions to do these activities are present in the
runtime library.
RPCD:
This is the RPC endpoint mapper daemon. RPCD is a
process that provides services for the local host, and is
also the server used by remote applications to access
these host services. The endpoint mapper service
maintains a database called the local endpoint map,
which allows DCE clients to find servers, individual
services provided by servers, and objects managed by
services on the host. The endpoint mapper service maps
interfaces, object UUIDs, and protocol sequence
registrations to server ports (endpoints). Servers
register their bindings with the local endpoint mapper,
and the endpoint mapper service on each host uses the
local endpoint map to locate a compatible server for
clients that do not already know the endpoint of a
compatible server.