SYSTEM ADMINISTRATION SECURITY

PART 2

1. Introduction to LAMP

For Linux, Apache, MySQL and PHP, LAMP stands. They offer a proven range of web
applications software to deliver high performance. Each component provides the stack
with important capabilities. It is an open source software package for the development of
web applications. To work smoothly on a web application, a system, a web server, a
database and a language must be included.

LAMP has a four-layered platform, which means it is also called a LAMP stack. Stacks
can be installed on different operating systems. LAMP is a web server stack acronym
example. Much more than confining themselves to the initial range, the LAMP
components are interchangeable. LAMP has been designed to create interactive websites
and web apps. The LAMP model has been adapted to another part since it was developed,
albeit traditionally consisting of open source free software.

LAMP (Linux Operating System), Apache Web Server, MySQL as relational database
management system, and PHP as the object-oriented scripting language is an open source
Web development platform.
1.1 Components of LAMP stack
Four software components comprise Linux based web servers. The software stack is
composed of these components, arranged in layers that support each other. On top of this
underlying stack are websites and Web applications. The common software components
of a LAMP stack are: The following
 Linux Operating System
 Apache HTTP Server
 MySQL database management system
 PHP programming language

PHP/Perl/Python scripting layer

Apache Web server layer MySQL Database layer

Linux Operating System Layer

 Figure 1. Components of LAMP

1.1.1 Linux

Linux is the backbone of the LAMP stack and the layer of the operating system. On top
of this base are all other components of the stack. On different operating systems such as
Windows, macOS and other, you can manage the remaining stack components
efficiently. But, not only because it is open source, but also because of its flexibility,
customization and technology, Linux is at the forefront of web development.

1.1.2 Apache

Apache HTTP Server is a Linux operating system Web Server Software. It has more than
half of the websites in the internet and is the most commonly used Server. The web
server is responsible for processing requests and communicating information via the
Internet, using HTTP.

1.1.3 MySQL

The most frequently used query language is SQL (Structured Query Language). A query
is what we call an information request or a database request in your table. MySQL has
become renowned for its supported SQL and relational tables as a well-known database
system. By doing so, the development of dynamic company-level databases is much
easier.

1.1.4 PHP
PHP is a language that combines all the LAMP stacks' elements to enable the Website or
the Web application to work efficiently. This is the programming language used to create
 an efficient web application. Briefly, the server processes the commands and sends the
results to a visitor's browser when a visitor opens the web page.
2. LAMP Architecture

With Linux at the lowest level, LAMP has traditional layer architectural design. Apache
and MySQL are the next layer, and PHP is the next. Although PHP is the top layer or
layer of presentation, the PHP element is in Apache.

Figure 2. Architecture of LAMP

The LAMP stack order of execution shows how the elements interoperate. The process
starts when the Apache webserver receives requests for web pages from a user's browser.
If the request is for a PHP file, Apache passes the request to PHP, which loads the file
and executes the code contained in the file. PHP also communicates with MySQL to
fetch any data referenced in the code.

In this case, PHP uses the file code and the database data to produce the HTML required
to display web pages by browsers. Not only static web pages but dynamic pages are easy
to operate with the LAMP stack. Content can change each time it is loaded depending on
date, time, user identity and other factors.

After running the file code, PHP then passes the resulting data back to the Apache web
server to send to the browser. It can also store this new data in MySQL. And of course,
 all of these operations are enabled by the Linux operating system running at the base of
the stack.

3. Advantages
 The LAMP stack is composed of four components, all free and open source
software examples (FOSS). Given that they are free and available for download,
many users are interested in preventing large sums of money from paying when
developing their websites.
 As it is FOSS, the software source code is shared and accessible to people, which
enhances their overall results.
 Thanks to its large community, which contributes when there are problems, the
LAMP stack has proved to be a safe and stable platform.
 We can easily adapt the stack and interchange component with other open-source
software to suit the needs.
4. Literature Reviews

While LAMP is a popular architector, there has been little work, particularly at
application level, to characterize and benchmark the architecture. However, considerable
work has been done to analyze the performance of certain other web applications.
Emmanuel Cecchet et al [1] compared LAMP architecture performance to EJB
performance and Java servlet performance. Two benchmarks, RUBiS[2] and
RUBBoS[3], were used as the basis for the comparison. The document[4] discusses the
benchmarks developed for comparison purposes. The characteristic bottleneck of their
work is presented in [5]. The presented work[6] discusses the efficiency and scalability of
the EJB applications through experiments on two different open source EJB applications
servers using different types of EJBs (sessions, entities, etc). (JBOSS and JOnAs).

In the early days of the start of the World Wide Web, C. D. Murta, J. M. Almeida and V.
F. Almeida [7] presented an evaluation of the performance of the WWW Server. In a
high CPU load performance analysis, Arun Iyengar et al.[8] presented Web server
analysis. Y. Hu, A. Nanda and Q. Yang[9] examined Apache web server performance on
uniprocessor and 4-CPU SMP machine. In the first place they analyze Apache web
servers performanceThe web server performance analysis Vsevold V. Panteleenko and
Vincent W. Freeh [10] have been performing WAN conditions. Vsevold V. In the field of
customer emulators some work has been done. The paper by Peter Drushel and Gaurav
Banga[17] describes a method that is temporarily above the web server's capacity to
generate bursty traffic. It also describes the challenges faced by the Web server capacity
measurement. They implement an emulator for the client, which can create explosive
traffic, using two architectures in the process. Some open source client emulators such as
HTTPerf, EVE and so on are available. The architecture of these client emulators is
described in documents [12] and [13].

There is work done to compare scripting language performance with programming

language performance. A few of the outcomes he had when comparing C++, Java, and
MFC performance of TCL/TK, Ousterhout describes in his article[14]. To measure
MySQL performance the sqlbench suite supplied by MySQL is available. The URL [15]
discusses some of the results that the sqlbench suite obtains. Wikis are websites which
enable users to create a site that is collaboratively developed and maintained by their
users to add and update content on the site using their own web browser. The report [11].

The need to quickly interact with its members who are often spread around the world in
order to carry out their work is one of the main features of many modern health
information companies. Nevertheless, while many health information technology
organisations discuss and advocate the appropriate use of technologies, the use of
technology in their day-to-day operations seems relatively slow. This seems especially to
be the case with regard to the use of web-based information technology and interaction
with online communities of its members and wider circumstances of concern [18][19],
whether this interaction involves sharing resources or knowledge, developing or utilizing
tools to support such interaction and diffusion or to improve patient benefits.

It is not an easy task to manage and run a web server. It requires extensive expertise in
various sectors, including operating systems, web service, databases and languages of
programming. The managing decision making and support for the platform is to be used
in addition to the technical aspects of the formula. Cost is the main determining factor
 which platform to use and which to avoid. [16]. another aspect that is properly checked
before choosing the right supplier is the availability of support.

The LAMP platform is a default install for all customers for several shared web hosting
companies. [20] LAMP stands for Linux operating system and is an acronym in addition
to running Apache's Web server, using a PhPMyAdmin to implement a MySQL database
management systems and then to use the PHP programming language.
5. Technical depth, correctness & completeness
With LAMP architecture an address book with the following requirements is created and
demonstrated
 A list of all contact entries stored in an address book should also be presented;
 Each entry (above) should include fields(name, first name, email, street, zip code)
and a city where a city should be a download of the cities defined in a database
table;
 A form for adding a new entry;
 A form for editing existing database entries
5.1 Uses of wireframe
Wireframes are simple product sketches to be created. They serve as models to clarify
how both the customer and the contractor will look like the software to be built. We can
say that wire frames are like maps that show characteristics of a certain landscape or
building. Wireframe is one of the prototypes of low fidelity that are used as blueprints
prior to the software development project. There are numerous tools for prototyping
wireframes. Adobe xd is used for the development of software in this project. One can
easily start using pencil project software for prototyping.
5.2 Lamp stack infrastructure provisioning
In developing, staging and production environments, the lamp stack can be supplied with
a number of ways. The local development environment is used to code previous shipping
code to another environment (staging and production environment) In the development
context, many other preliminary development activities, for example unit testing and
similar things, are often characterized by a lot of debugging. The stage setting is available
for massive testing before code is deployed for the production to satisfy functional, non-
functional and user requirements. The staging environment is so created that the finished
software product is used and retained to imitate the production environment.

Figure 3. Creation of address book

The creation of form for address book with needed fields are designed and shown in the
figure 3.
 Figure 4. Sample address book
The sample address book is executed and shown with two contact fields in figure 4

Figure 5. list of contacts

With the use of contact list fields the data stored in database is retrieved and listed using
SQL in LAMP stack which is shown in figure 5.
 Figure 6. Edit contact
In the contact book there is possibility to show contact list as well the contacts can be
edited using edit option shown in figure 6.

Figure 7. add contact

By using INSERT operation of database new contact can be added even at any place in
the database like in figure 7.
6. Conclusion
The LAMP packing solution was a reliable installation which serves very large web sites
and ensures that the server is running optimally. The system offers outstanding load
balance and is regarded as a leader in providing high availability of LAMP instances'
services. As it provides better performance and smooth handling of the relation database
and extremely high web traffic and demand, the LAMP platform is the perfect solution
for system administrators and information system professionals.
7. References
1. Jakobovits RM, Rosse C, Brinkley JF. WIRM: an open source toolkit for building
biomedical web applications. JAm Med Inform Assoc. 2002;9(6):557-70.
2. International Institute of Infonomics. Free/Libre and Open Source Software: Survey and
Study. [monograph on the Internet]. Maastricht: International Institute of Infonomics,
2002 [cited 2005 Jan 21] Available from: http://www.infonomics.nl/FLOSS/index.htm
3. Stallman RM. Linux and the GNU Project.[homepage on the Internet]. Boston (MA):
Free Software Foundation; c.1997-2002 [updated 2004 Jul 12; cited 2005 Jan 8 Available
from: http://www.gnu.org/gnu/linux-and-gnu.html
4. Wheeler DA. Why Open Source Software / Free Software (OSS/FS)? Look at the
Numbers! [monograph on the Internet]. 2005 [updated 2005 Jan 15, cited 2005 Jan 21]
Available from: http://www.dwheeler.com/oss_fs_why.html
5. Cecchet etal, Performance Comparison of Middleware Architectures for Generating
Dynamic Web Content, 4th ACM /IFIP/USENIX International Middleware Conference,
Rio de Janeiro, Brazil, June 16-20, 2003
6. RUBiS: Rice University Bidding System URL: http://rubis.objectweb.org
7. UBBoS: Rice University Bulletin Board System URL: http://rubbos.objectweb.org
8. Amza etal, Specification and Implementation of Dynamic Web Site Benchmarks, IEEE
5th Annual WWC-5, Austin, TX, USA, November 2002.
9. Amza etal, Bottleneck Characterization of Dynamic Web Site Benchmarks, Technical
Report TR02-398, Rice University, January 2002.
10. H. Jamjoom and K. Shin, Eve: A Scalable Network Client Emulator, University of
Michigan Tech Report, CSE-TR-478-03
11. Ousterhout, Scripting: Higher Level Programming for 21st Century, IEEE Computer
Magazine, March 1998.
12. MySQL Benchmarks, http:// dev. mysql. com/ tech-resources/benchmarks
13. UV Ramana, Some experiments with the performance of LAMP architecture, Masters
thesis, IIT Kanpur, 2004.
14. Len Bass, Paul Clements and Rick Kazman, Software Architecture in Practice, Second
Edition, SEI Series in Software Engineering, 2003
15. Cecchet etal, Performance and scalability of EJB applications, 17th , Oopsla 2002,
Seattle, WA, USA, 4- 8 November 2002.
16. C. D. Murta, J. M. Almeida and V. A. F. Almeida, Performance Analysis of a WWW
Server, XXII SEMISH, Recife, Brazil, August, 1996
17. Iyengar etal, An Analysis of Web Server Performance, In Proceedings of the IEEE 1997,
GLOBECOM '97, Phoenix, AZ, November 1997.
18. Y. Hu, Nanda, and Yang., Measurement, analysis and performance improvement of the
ApacheWeb server, Proc. of the 18th IEEE IPCCC, (Phoenix/ Scoottsdale, Arizona), pp.
261-267, Feb. 1999.
19. Panteleenko and Freeh, Web Server Performance in a WAN Environment, Proc. of
ICCCN, Dallas, TX, October, 2003
20. Banga and Drushel, Measuring the Capacity of a Webserver, USENIX Symposium on
Internet Technologies and Systems, Monterey, California,December 1997