Client, The

Chapter-1
Introduction: - Client / Server is a computer industries latest and hottest buzz words. There is no generic definition of client / server because it is used to detect many of the nature, development and anticipateologies. But the general idea is that clients and servers are separate entities working together on a careful logical network to accomplish a task. Client-server is very fashionable. As such, it could just be a temporary fashion, but it is generally accepted that something fundamental and far-reaching, for example, the Gartner Group, which is the main industry analysts in this area , predicted that
"In 1995, client-server computing will bring." Most of the initial client / server achievements involve small-scale applications that provide indirect or direct access to transactional data in existing systems. Companies must provide data access for decision makers, the relative immaturity of tools client / server technology, the use of the development of wide area networks and lack of expertise in client / server to make those attractive yet low-risk driver. As organizations move up the learning curve of these small-scale projects to mission-critical applications, there is a corresponding increase in performance expectations, the availability requirements and the need to stay flexible scalable. In such a scenario requiring the selection and implementation of appropriate architecture becomes critical. In fact, one of the fundamental issues that practitioners face at the beginning of each project client / server - "architecture is more appropriate for this project - Two or Three levels?". Interestingly, 17% of all critical mission client server applications / Three levels and the trend is growing, according to the Standish Group International, Inc., a market research firm. Architecture affects all aspects of software design and engineering. The architect believes that the complexity of the application, the level of integration and interfacing required, number of users, their geographical dispersion, the nature of networks and all the transactional needs of the application before decide on the type of architecture. Poor architectural design or implementation can lead to imperfect response times appalling. The choice of architecture also affects the development time and flexibility and maintenance of the application. The current literature does not adequately address all these aspects of client / server architecture. This document defines the basic concepts of client / server architecture, describes the two levels and three tier architectures and discusses their respective advantages and limitations. Differences in development efforts, flexibility and ease of reuse is also compared to further aid in choosing the appropriate architecture for a given project.

-Chapter 2
History & defintion: -
History of the University of Waterloo implemented Oracle Financials Government (OGF) in May 1996. This prompted the UW based accounting systems to a set of vendor supported on Solaris / Unix and away from locally developed package (s) on IBM / VM. Plans at that time to move over (if not all business systems) to a single supplier and standardize on a single platform (Oracle database for both). A very important condition of Solaris art system was purchased with the intention of co-localization of these other services provided by Oracle on the same system with the OGF. the network security architecture was expected that the isolation of relevant administrative systems, fire walls of these networks with protocol filters and traffic monitoring force. The systems were purchased and deployed to implement the security architecture ..