1

A REPORT ON HYBRID DISTRIBUTED APPLICATION IN BANKING

TRANSACTION USING REMOTE METHOD INVOCATION
PURITY BITENGO GWARO
CI/00014/018
DISTRIBUTED SYSTEMS (CCS 407)
 2

Introduction
With technological advancement, banks have many branches with systems that use a central
database. The applications enable customers to carry out different activities like creating
accounts and money transfers. The most competitive bank is the one with speedy technology.
The solution is distributing the application to the network to optimize and reduce the problem
of increased server performance due to many users. To achieve the distribution three-tier
application is used because it supports the deployment of distributed-based applications. A
remote method call is used since distributed applications take a remote method call.

Remote method invocation

Remote method invocation is a feature in java that enables java virtual machines to call
methods of the same object in another Java virtual machine running in a different computer
or same. Implementation of RMI involves two components, RMI server, and RMI client.
RMI server consists of objects whose methods are called remotely. The RMI architecture
consists of three layers. The stub/ skeleton, remote reference layer, and transport layer.

Servlet
It is a java program that can be deployed in a java enabled server to give it full web server
functionality. Servlet is used in accessing RMI. Therefore, we can use servlet to develop
banking applications that handle transactions through the web. Java 2 Enterprise edition can
be used to deploy servlet and JSP. Below are data flow diagrams illustrating the flow of data
in the banking web application and the desktop application that will be developed using the
above knowledge on distributed systems that are implemented using the remote method
invocation and servlet in Java 2 enterprise edition.
 3

Figure 1 Banking web application data flow diagram

Customers send data during registration, and it is stored in the database’s registration table.
After a customer has been registered and has an account, they can log in using the account
number and a PIN. After authentication, access is given, and a customer can carry out
transactions. After transactions go through, a customer is given a report.
 4

Figure 2 Banking Desktop data flow diagram

In the desktop application, it is different; a teller serves a customer. The officer registers a
user, and the data is kept in the registration table in the database. After registration, the
officer can log in using the relevant details and carry out transactions for the customer. After
transactions are done, an update is done on the account balance.

Conclusion
Servlet and RMI help implement the same methods used in the desktop application for the
web application. The three-tier application model helps to implement a distributed application
model in the banking application.