Client Server - A New Paradigm for Collection-Master
Multi Tiered Client/Server Architecture (Collection-Master
with BR Client, the New Paradigm)
Taking advantage of the multi-tiered Client
Server Architecture of Business
Clients Responsibility:
1. User Interface
2. Communicate Requests to Server
3. Receive Results from Server
4. Interact with Local Resources and 3rd Party Applications.
a. Word Processor
b. Document Imaging
c. Web Browser
d. Ms-Excel
Client Requirements (BR Client):
1. Each Session uses 40-150MB of Memory
(Comparable to Distributed or Native Client)
2. Very friendly to a Terminal Server Environment.
3. Graphical or Display Intensive (The Client’s Primary Job
is to Display Information to the user).
4. Minimal Network Requirements – Overall Network usage will
decrease dramatically
Application Server Responsibility:
1. Receive Requests from Client
2. Apply Business Rules Logic
3. Run Collection-Master Code
4. Communicate Requests to Data Resources
5. Return Results to Client
Application Server Requirements (BR
Listener/Server):
1. Windows 2003/2008 Server
2. 32 or 64 bit Servers Supported (64 bit Preferred).
3. Data or I/O Intensive
4. Each Session uses roughly 10MB of Memory (Roughly 100
Sessions per 1GB of server Memory).
5 CPU Utilization is automatically spread out over available
cores. (Minimum 4 Cores Recommended)
6. Minimal Network Requirements.
7. Very Friendly to Virtualization (AKA VMWare)
Database Resources: (Storage)
1. Usually a local Raid Array on the ‘Application Server”
2. Scale to larger and faster drives with iScsi and SAN
devices
3. May support many Application Servers/Clients.
Traditional Client Server Architecture:
The client/server model is a form of
distributed computing where one program (the client)
communicates with another program (the server) for the purpose
of exchanging information.
The client's responsibility is usually to:
1. Handle the user interface.
2. Translate the user's request into the desired protocol.
3. Send the request to the server.
4. Wait for the server's response.
5. Translate the response into "human-readable" results.
6. Present the results to the user.
The server's functions include:
1. Listen for a client's query.
2. Process that query.
3. Return the results back to the client.
A typical client/server interaction goes like this:
1. The user runs client software to create a query.
2. The client connects to the server.
3. The client sends the query to the server.
4. The server analyzes the query.
5. The server computes the results of the query.
6. The server sends the results to the client.
7. The client presents the results to the user.
8. Repeat as necessary.
Traditional Collection-Master Distributed
Computing architecture: (AKA Native Client).
A distributed computer system consists of
multiple software components that are on multiple computers, but
run as a single system. The computers that are in a distributed
system can be physically close together and connected by a local
network, or they can be geographically distant and connected by
a wide area network. A distributed system can consist of any
number of possible configurations, such as mainframes, personal
computers, workstations, minicomputers, and so on. The goal of
distributed computing is to make such a network work as a single
computer.
Some hardware might use UNIX® as the operating
system, while other hardware might use Windows® operating
systems. For inter-machine communications, this hardware can use
SNA or TCP/IP on Ethernet or Token Ring.
Related Topics
Sample System Configuration as of 2010
|