RPC

RPC definition

Remote Procedure Call (RPC) is a method which allows We have access to a procedure
recitation That was in another computer. For CAN do Singer A Must PROVIDE SERVICES
server remote procedure. That approach was done is a Server Open the socket, then wait
clients calling for procedures recitals Provided By Server. If the client does NOT know Must
contact industrial port Which, clients can request I- showed to the matchmaker ON A port An
RPC That Remain. Matchmaker will give APA The port used by the client Requested
Procedure.

RPC hearts are still using primitive way of programming, ie using procedural programming
paradigms. It's hard when kita MAKE THAT PROVIDE Many remote procedure. RPC using
a socket for a review berkomunikasi WITH other processes. AT Systems such as SUN, RPC
operates Already standard system into the most installed,

Terms and Definitions

The following terms are associated with RPC.

Client

A process, such as a program or task, that requests a service provided by another program.
The client process uses the requested service without having to deal with many working
details about the other program or the service.

Server

A process, such as a program or task, that responds to requests from a client.

Endpoint

The name, port, or group of ports on a host system that is monitored by a server program for
incoming client requests. The endpoint is a network-specific address of a server process for
remote procedure calls. The name of the endpoint depends on the protocol sequence being
used.
Endpoint Mapper (EPM)

Part of the RPC subsystem that resolves dynamic endpoints in response to client requests and,
in some configurations, dynamically assigns endpoints to servers.

Client Stub

Module within a client application containing all of the functions necessary for the client to
make remote procedure calls using the model of a traditional function call in a standalone
application. The client stub is responsible for invoking the marshalling engine and some of
the RPC application programming interfaces (APIs).

Server Stub

Module within a server application or service that contains all of the functions necessary for
the server to handle remote requests using local procedure calls.

RPC implementation

For his process is roughly equal to the RMI. If RMI We Know Proxy And the skeleton,
known WITH THE RPC Stub (Stub Client And Server stub)

Reference secluded Module and Communication Module is ON order of the Operating

System.
Implementation example is Sun Microsystems Open Network Computing (ONC): RPC
specification, standard XDR (External Data Representation), OR UDP transport protocol
TCP. Xerox Courier: Model RPC, data representation standard, XNS (Xerox Network

Systems) SPP (Sequenced Packet Protocol) as the transport protocol, Apollo's Network
Computing Architecture (NCA), RPC protocol, NDR (Network Data Representation).

How it Works RPC

Each Procedures Called RPC hearts, then the husband Process Server Must connect WITH
ALL WITH far transmit parameter Required, Waiting Reply From Server And do the process
and then Finish. Also in the process of so-called differences WITH THE stub client side.
Meanwhile, AT Stub Process Server Side Is Waiting for each message That Contains the
request of the State Regarding Specific teaching procedures.

Above diagram provides overview Regarding the execution hearts flowing from the RPC
process. The following is a diagram Singer Which would explain the detailed Operating
Process terjadipada On Client And Server hearts instruction execution A procedure RPC:

Explanation From Above diagram:

1. Clients call the Local pilot study procedures. Stub procedure will give hearts parameters A
package to be sent to the Network. Husband process is called marshalling.

2. Network Functions ON O / S (Operating Systems - Operating Systems) will be called by a

stub message sent for review One.

3. Then Kernel singer will be a message sent Ke remote system. Singer condition OR MAY
connectionless connection-oriented Form.

4. Stub ON side will Process Server performs unmarshals Sent packet network IN pada.

5. Stub ON Server then executes the instruction procedures Local Calls.

6. IF instruction execution procedure Singer Has Been Done, then execution is given Back to
stub ON Server.
7. The server stub marshals who will process Again And your message to send feedback
value (result) Return To Network.

8. Messages will Husband Sent Back to clients.

9. The client stub message will be read Singer WITH IN functions using the Network.

10. The process unmarshalled then the message AT done Singer And Value feedback will be
taken to review then processed ON Local Process.

Above process will be repeated (recursive) hearts hearts An RPC remote execution system.
Examples of applications for review meremote ON technique RPC (Remote Procedure Call)
is using putty to review SSH do.

Advantages RPC
Relatively Easy to use

Remote procedure call NOT MUCH DIFFERENT than local procedure calling. So the
programmer concentrate CAN AT software logic, NOT Need to think low-level details such
as sockets, collate and unmarshalling.

Strong (Perfect)

Since th 1980 RPC Has Many hearts used development of mission-critical applications
Which require scalability, fault tolerance, and reliability.

weakness RPC
NOT FLEXIBLE To change

static relationship between the client and the server at run-time.

Based on the procedural / structured programming that already outdated compared Object
Oriented Proggraming
Lack location transparency

Misalnya premrogram There can only do pass by value, not passing by reference.

Client Communications Only BETWEEN 1 & 1 server (one-to-one by one).

Communication BETWEEN 1 client and several servers that require multiple connections
Yang separately.

RMI
Definition of RMI

RMI is the extension of local method invocation that allows an object that lives in one
process to invoke an object method that is in another process. (George Coulouris case 166).

RMI is a remote method invocation technique more generally better than RPC. RMI uses
object-oriented programming paradigm (Object Oriented Programming). RMI allows us to
send an object as a parameter of the remote method. By allowing for Java programs invoke
methods on remote objects, RMI allows users to develop distributed Java applications on the
network.

RMI applications are often comprised of two separate programs, namely the server and client.
Application servers typically make some sort of remote objects, provide references to those
objects that can be accessed, as well as waiting for a client invoke methods on these remote
objects. Remote client application to get a reference to one or more remote objects in the
server and invoke a method on the object.

RMI provides the mechanism by which the server and client to communicate and provide
information on a reciprocal basis. Such applications are often called a distributed object
applications.
Making Step Program to RMI

In RMI, all information about the server services are provided in a remote interface
definition. By looking at the interface definition, a method programmers can tell what can be
done by the server, the data covering what is acceptable and what data will be sent in
response.

The definition contained in the remote interface methods to determine the characteristics that
provided the server which can be seen by the client. Client programmers should be able to
know what methods are available and how to call the server directly with a view to the
remote interface. Clients get a reference to the remote object through RMI registry.

Build a distributed application using RMI includes six steps. These six steps are:

1. Define the remote interface

2. Implementation of the remote interface and the server

3. Development of the client (or applet) that uses a remote interface

4. Compile the source files and backing for the stub and skeletons

5. Getting started (start) RMI registry

6. Run the server and client

Implementation of RMI

Reference Module Remote Remote reference module is responsible for translating between
local and remote reference object and to create a remote object reference. To support this
task, reference remote modules in every process has a remote object table that records the
correspondence between local object references in the process and remote object reference
(where system-wide) (George Coulouris et al, p 176)

Module reference remote actions are as follows:

When the remote objects to be passed as arguments or results for the first time, the remote
reference module module is asked to create a remote object reference, which add tables.

When a remote object reference arrives in the request or reply to the message, the remote
reference modules are required to adjust the local object reference, which may refer to either
the proxy or to a remote object. In the case of a remote object reference does not exist in the
table, creating a new proxy RMI software and ask for a remote reference module to add to the
table.

RMI's software consists of a software layer between the object and the application level and
reeferensi remote communications module. Object middleware role are as follows:

Proxy: The role of the proxy is to make a plea metoderemot transparent to clients by acting as
a local object to invoker, but in addition to carrying out a request will be forwarded a
message to remote objects. It hides the details of the remote object references, which make
the argument, describes the results and send and receive messages from clients.

Operator / Dispatcher: A server has a single operator and the framework for each class
represents a remote object. In our example, the server has a service and a framework for
remote object class B. The operator receives the request message from the communication
module. He uses methodId to choose the appropriate method within the framework then relay
the request message. Operator and use the same proxy methodld allocation to the remote
interface methods.

Skeleton: Class distant object has a skeleton, which implements the methods in the remote
interface. They held quite different from the methods in the remote object. A framework
outlining the method arguments in the request message and call the appropriate method in a
remote object.

Example implementations of RMI include:

Avitek programming company located in the United States, making the program accounting
system for intranet that allows clients to update and modify data with ease. The goal of this
project is to create and support the creation of real evidence for the concept of the use of Java
combined with a database.

CEAS Consulting company providing custom services re-engineering and automation of the
process for the companies manufacturing and engineering, have created programs distributed
systems for their clients. Overview of the program they are as follows:

How it Works RMI

In this model, a process of calling the method of the object that lies in a host / remote
computer. In this paradigm, service providers register themselves with the directory server on
the network. The process that desire a directory server to contact the service at runtime, if the
service is available, then the reference to the service will be provided. By using this
reference, the process can interact with the service page. This paradigm is an important
extension of the RPC paradigm. The difference is the objects that provide the service
requested (registered) to a global directory services, making it possible to found and accessed
by an application requesting the service.

Example applications for remotely on engineering RMI (Remote Method Invocation) use
TeamViewer to another computer remotely.

TeamViewer is a program that is quite simple and very easy to use for multiple purposes
primarily to access the PC remotely via the internet.

How to remotely RMI

The main view TeamViewer, if it is performed (Ready to connect (secure connection)) then it
is ready to connect to another PC, then enter the ID PC client if the connection is successful it
will display the "Password", the contents of password TeamViewer PC that you want the
remote. If successful it will show the diremote desktop PC. If you want to perform File
Transfer, then select "File Transfer" on the choices that appear below the box ID, and then
click "Connect to partner".

If you want to use a password and ID are fixed then simply place the mouse cursor in the
password box, it will look like the image above, select "Set definied user password" and then
enter the password you want. The result Once we apply the settings on TeamViewer and after
login and enter the password correctly goal then we can access a remote computer that we are
full.

Advantages and Disadvantages RMI

profits were RMI

One of the main advantages is the ability to download RMI zytecodes (code) of an
object's class if the class they will not be defined in its VM recipient.
Type-type and methods of the object (class), which is located in one VM, can be sent
to another VM, which may be remote.
The properties of this object are sent not changed at all

Weakness RMI

Socket opening process that sometimes can not be implemented through the internet
network, but this can be overcome by using Spring HttpInvoker, exactly the same but the
RMI via HTTP protocol.

Conclusion

Remote Procedure Call (RPC) is a method that allows us to access a procedure located on
another computer. To do this a server should provide remote service procedure. The approach
that was done is an open server socket, then wait for the client who requested the procedure
provided by the server. If the client does not know what to call the port where, the client can
Me- request to a matchmaker at a fixed RPC port. Matchmaker will give any port used by the
client requested procedures.
 Remote module Remote module references Reference responsible for translating between
local and remote reference object and to create a remote object reference. To support this
task, reference remote modules in every process has a remote object table that records the
correspondence between local object references in the process and remote object reference.
 CORBA
Definition of RMI

The Common Object Request Broker Architecture (CORBA) is a standard defined by

the Object Management Group (OMG) designed to facilitate the communication of systems
that are deployed on diverse platforms. CORBA enables collaboration between systems on
different operating systems, programming languages, and computing hardware. CORBA uses
an object-oriented model although the systems that use the CORBA do not have to be object-
oriented. CORBA is an example of the distributed object paradigm.

Corba Architecture

CORBA (Common Object Request Broker Architecture) is a specification developed

by the OMG (Object Management Group), a consortium of over 800 companies.

The aim is to develop programming CORBA distributed objects. CORBA is not a

programming language, but is a specification for developing distributed objects. Some
software that implements COBA eg Orbix (by IONA Technologies), VisiBroker (by Insprise),
and JavaIDL (by JavaSoft). CORBA architecture-based object model. The model is derived
from the abstract Core Object Model that is defined in the OMA OMG (Object Management
Architecture). This model is an abstract picture that can not be implemented without the use
of a particular technology. With this model, an application built with the standards that have
been determined. The system consists of CORBA objects to isolate a client from a server
using encapsulation interface is strictly defined. Objects CORBA objects can run on multiple
platforms, it can be located anywhere in a network, and can be encoded with any
programming language of origin has IDL mapping.

Object Management Architecture (OMA) defines various highlevel necessary

facilities for object-oriented computing. The main part of the OMA is the Object Request
Broker (ORB). ORB is a mekanime that provides location transparency, communication, and
activation. An object. ORB is a kind of software bus to objects in CORBA. Based on the
OMA, CORBA specifications must be complied with by the ORB.

ADVANTAGES

Maturity - CORBA is extremely feature-rich, supporting many programming languages,

operating systems, and a diverse range of capabilities such as transactions, security,
Naming and Trading services.

Open standard - users can choose the implementation from a variety of CORBA
vendors.
 Wide platform support - CORBA implementations are accessible for a wide variety of
computers, including IBM OS/390 and Fujitsu GlobalServer mainframes, LINUX,
Windows and several embedded operating systems.

Wide language support - CORBA defines standardized language mappings for a wide
variety of programming languages, such as C, C++, Java, Smalltalk,COBOL,Python and
IDLScript.

Efficiency - The on-the-wire protocol infrastructure of CORBA guarantees that messages

between clients and servers are transmitted in a compact representation.

Scalability - The flexible, server-side infrastructure of CORBA makes it possible to

develop servers that can scale from handling a small number of objects up to handling a
virtually unlimited number of objects.

DISADVANTAGES

Firewall unfriendly - There's no real CORBA standard to bind an ORB and its clients
to a port or a port range, there are (only) vendor specific options.

Regarded as complicated some remote invocation of CORBA interfaces is at least as

simple as over XMLRPC (which is regarded as easy).

No standard to get the initial reference for the naming services.

No official Perl making - There are at least two Perl ORBs available as open source, but
neither the mapping is official, nor are the implementations complete.
SOURCE

https://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture

http://chumchumsoft.blogspot.co.id/2013/09/makalah-corba.html

http://201415tcs4063.blogspot.co.id/2014/10/advantages-and-disadvantages-of-corba.html