Uniterm Home 3






A. THIN CLIENT COMPUTING

Thin Client computing is Server-based computing. Application programs are executed on the Server, keyboard and mouse input from the Client is packetised and sent to the Server. The Server responds sending Video and Cursor updates to the Client Console.


WHY SHOULD I TAKE THE THIN CLIENT OPTION?
  1. TCO

    The total cost of deploying Thin Client's over a period of time compared to deploying PC's to perform the same function over the same time period is considered less.

    The size and expansiveness of your network has a large impact on this cost reduction as a larger network will be easier to manage. Central Management greatly reduces the amount of human resources required to maintain application software and configure network devices.

    The initial purchase price of a Thin Client may well be on a par with an entry level PC but the solid-state architecture of the Thin Client is a more reliable option. Software licensing costs of the Thin Client device are of no concern to the puchaser.

    Limiting the user's desktop to include only the resources necessary to perform a required task can reduce loss of productivity. Lack of a movable media interface to the Thin Client improves security of data and isolation from viruses.

    TCO in a nutshell:
    • reduce hardware and software costs
    • reduce training, maintenance and support costs
    • reduced down time
    • improve productivity
    • improve scalability
    • improve performance
    • enhance security
    • virus immunity
    • reduce logistics and power consumption

  2. Reliability

    Thin client devices have no "moving parts" like Hard Disk Drives, CD-ROMS and Stiffy Disk Drives that are prone to failure from time to time. Thin clients are immune to viruses and other destructive elements.



WHAT HAS TO BE DONE TO IMPLEMENT A THIN CLIENT SOLUTION?
  1. Once you have chosen which operating system best suits your requirement deploy your network infrastructure and server hardware.
  2. The network may be as expansive as a global wide area network or restricted to a simple local area network.
  3. The performance required from your server will determine the processing power and memory requirement. More simultaneous Thin Client sessions running on the Server will require more processing power and memory resources from the Server. A single processor based Server should be capable of catering for the demands of up to a dozen or so users. As the demand for processing power increases, multi-processor Server architecture and Server farm topologies will have to be considered.
  4. The strength of Server-based computing lies in the scalability of your overall implementation. A small operation in one city can simply extend their network to facilities in other cities. As the user count increases additional servers can be added to the network.

WHY USE A LINUX EMBEDDED THIN-CLIENT SOLUTION?

Linux has proven to be a reliable no-cost operating system. The availability of source code to all Linux developers has enhanced software product using Linux and accelerated the acceptance of Linux and the size of the development community.


WHICH SERVER IS THE RIGHT SERVER FOR MY APPLICATION?
  1. There are a lot of questions one has to ask at this point.
    • What applications do you want to run?
    • Which operating system were they designed to run on?
    • Do you want to serve a multitude of applications which run on different operating systems?
    • Are you migrating from one operating system to another?
    • Do you want GUI applications which use a mouse or will text-based applications suffice, or do you want both?
    • Do you have budget constraints?
    • What is the size of the network, is it a WAN or a LAN and are the users going to be working from static desktop points or will they be mobile?
  2. TELNET
    A cost effective text only server, perfect for simple data capture environments.
  3. X11R6
    The traditional UNIX GUI windowing server, not so thin on network resources, more skill required to administer the network.
  4. LTSP
    Linux Terminal Server Project, Linux Server and Client operation. Complete administration of client device is done at the Server. See www.ltsp.org
  5. CITRIX METAFRAME
    Windows NT Terminal Server and Windows 2000 Terminal Services server extensions, uses the really thin and encrypted ICA protocol with audio support to facilitate an NT desktop on a client device. Rich in resources including central management and server farming. See www.citrix.com
  6. WINDOWS 2000 TERMINAL SERVICES
    Native to this server no additional server extensions are required to facilitate a Remote Desktop on a client device. The server component is based on Citrix MultiWin technology and the RDP client protocol based on the ITU-T T.128 application sharing protocol.
  7. CITRIX NFuse
    Publish Windows, UNIX and Java applications for access from any standard Web Browser without application rewrites. Citrix NFuse supports virtually any client device or operating system.
  8. TARANTELLA
    The Tarantella Server must have a web server installed. Enterprise 3 simplifies administration and securely speeds access to Windows, Web, Java technology, mainframe, AS/400, Linux and UNIX based systems and applications from client devices globally. Centralised management effortlessly scales to accommodate rapid corporate change. See www.tarantella.com

B. SMS MESSAGING
WHAT IS EASISMS
  1. EASISMS is a stand alone device which connects your PC or network to the GSM SMS network. The easisms is equipped with an Ethernet TCP/IP connection for network or internet access and serial connection for simple connections to a PC.
  2. When fitted with an SMS SIM card this device can send and receive SMS at costs lower than traditional voice SIM contracts.
  3. easiSMS is great for marketing and advertising, corporate communication and Call-Alert communications.

 
  contact
home