Database Management Issues in

Mobile Computing

Lesson 04
Client–Server Computing and Adaptation
in Mobile Device

© Oxford University Press 2018. All rights reserved. 1

 Two Network Based
Computing Architectures
• Distributed Peer-to-Peer─ designed each
node distributed computing node of the
system, each node on the network similar
resources and the various nodes can
depend on each other resources
• Client-Server─ designed such that a node
is either a client or server

© Oxford University Press 2018. All rights reserved. 2

Client-Server Architecture in
Mobile Environment
• Client node has much less resources than
server
• Client nodes depend on server resources

© Oxford University Press 2018. All rights reserved. 3

Client-Server Architecture in
Mobile Environment
• A client requests the server for data or
responses
• The client can either access the data
records at the server or cache these
records through broadcasts or distribution
from the server

© Oxford University Press 2018. All rights reserved. 4

 Client-server Computing

• An N-tier architecture (N = 1, 2, …)
• On the same computing system (not on a
network), then the number of tiers, N = 1
• When the client and the server are on
different computing systems on the
network, then N = 2

© Oxford University Press 2018. All rights reserved. 5

 Server networks

• Connecting to other computing

systems
• Connecting to other systems provide
additional resources to the server for the
client then N > 2
• N > 1 means that the client device at tier
1 connects to the server at tier 2 which,
in turn, may connect to other tiers, 3, 4,
and so on
© Oxford University Press 2018. All rights reserved. 6
Application server in two-tier

• Client–server computing architecture

• Local copies 1 to j of database hoarding at
the mobile devices) on client request
• Synchronization API enables running of
the application independently on the
devices without the need for a run-time
retrieval

© Oxford University Press 2018. All rights reserved. 7

Two-tier Client–Server
Architecture

© Oxford University Press 2018. All rights reserved. 8

APIs and Synchronization API

• Various APIs synchronization with each

other
• Synchronization─ means that when copies
at the server-end modifies, the cached
copies accordingly modified
• The APIs designed independent of
hardware and software platforms as far as
possible as different devices may have
different platforms
© Oxford University Press 2018. All rights reserved. 9
 Two-tier client–server
architecture using a multimedia
files server

10
© Oxford University Press 2018. All rights reserved.
 Three-tier Client–Server
Architecture
• The application interface, the functional
logic, and the database are maintained at
three different layers
• The database is associated with the
enterprise server tier (tier 3)
• Only local copies of the database exist at
mobile devices

© Oxford University Press 2018. All rights reserved. 11

 Three-tier Client–Server
Architecture
• Database at the backend system of an
enterprise (company) that holds IBM DB2,
Oracle, and other databases
• Server at Tier 2 connects to the enterprise
server through a connecting protocol. The
enterprise server connects the complete
databases on different platforms, for
example, Oracle, XML, and IBM DB2

© Oxford University Press 2018. All rights reserved. 12

Database record Copies of database at
the mobile devices using three tier
architecture

© Oxford University Press 2018. All rights reserved. 13

 Mobile Device with J2ME or BREW
platform, an OS and database having
local copies

© Oxford University Press 2018. All rights reserved. 14

 Connectivity of synchronization-
cum-application server
• To enterprise server is by RPC, RMI,
JNDI, or IIOP protocols
• When application client at tier 1 connects
to tier 2 using the Internet, the connectivity
protocol, HTTP or HTTPS

© Oxford University Press 2018. All rights reserved. 15

 N-tier Client–Server
Architecture
• When N is greater than 3, then the
database is presented at the client through
in-between layers
• Four-tier architecture in which a client
device connects to a data-presentation
server at tier 2
• The presentation server then connects to
the application server tier 3
© Oxford University Press 2018. All rights reserved. 16
 N-tier Client–Server
Architecture
• The application server can connect to the
database using the connectivity protocol
and to the multimedia server using Java or
XML API at tier 4

© Oxford University Press 2018. All rights reserved. 17

 4-tier architecture in which a client
device connects to a data-presentation
server

© Oxford University Press 2018. All rights reserved. 18

 Mobile-device number of
interfaces (APIs)
• PIM (personal information manager)
interfaces for the calendar, contacts
• Microsoft Outlook or Intellisync Wireless
e-mail
• Lotus Notes (5x and 6x)

© Oxford University Press 2018. All rights reserved. 19

 Mobile-device number of
interfaces (APIs)
• Lotus Organizer (5x and 6x)
• APIs for IBM WebSphere Everyplace
Access, BlackBerry Connect, Oracle
Collaboration Suite, Secure Mobile
Connections via VPN Client and Symantec
Client Security 3.0, Fujitsu mProcess
Business Process Mobilizer. report

© Oxford University Press 2018. All rights reserved. 20

 Necessity for Client Server
Computing with Adaptation
• The data format differences in different
cases for data transmitted from the
synchronization server and those required
for the device database and device APIs

© Oxford University Press 2018. All rights reserved. 21

Client Server Computing with
Adaptation
• Two adapters (adaptation software) at a
mobile device
• An adapter for standard data format for
synchronization at the mobile-device
• Another adapter for the backend database
copy, which is in a different data format for
the API at the mobile-device

© Oxford University Press 2018. All rights reserved. 22

 Adapter

• Software to get data in one format or data

governed by one protocol and covert it to
another format or to data governed by
another protocol

© Oxford University Press 2018. All rights reserved. 23

 APIs, database and adapters at a
mobile device and the Adapters for the
server

© Oxford University Press 2018. All rights reserved. 24

 Adapters
• Used for interchange between standard
data formats and data formats for the API
• IBM WebSphere Everyplace Access
(WEA) provides adapters for
synchronization objects (for example, XML
format synchronization objects) and the
objects of API databases (for example, for
the PIM APIs)

© Oxford University Press 2018. All rights reserved. 25

 Summary

• Two methods in Network Architecture for

computing
• Peer-to-Peer and Client Server
• 1 Tier in which server and API at the
mobile device itself
• Two, three, four or N tier architecture
• Use of presentation, synchronization,
enterprise database servers
© Oxford University Press 2018. All rights reserved. 26
 Summary

• Client-server computing with Adapters

for interchange between standard data
formats and data formats for the API

© Oxford University Press 2018. All rights reserved. 27

 End of Lesson 04
Client–Server Computing and Adaptation
in Mobile Device

© Oxford University Press 2018. All rights reserved. 28