HP Open Source Middleware Stacks Blueprint: LAMP Architecture on HP ProLiant BladeSystem Servers on RHEL

Manuals Brands HP Manuals Software HP Linux Caliper Software Electronic LTU

HP Open Source Middleware Stacks

Blueprint:

LAMP Architecture on HP ProLiant BladeSystem

Servers on RHEL

HP Part Number: 5992-4862

Published: August 2008

Edition: 1.0

Summary of content (25 pages)

PAGE 1

HP Open Source Middleware Stacks Blueprint: LAMP Architecture on HP ProLiant BladeSystem Servers on RHEL HP Part Number: 5992-4862 Published: August 2008 Edition: 1.
PAGE 2

© Copyright 2008 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 3

Table of Contents Introduction ...........................................................................................................................................7 Executive Summary...........................................................................................................................7 Intended Audience............................................................................................................................7 Scope and Purpose......................................
PAGE 4

List of Figures 1 2 3 4 4 LAMP Environment Architecture...................................................................................................9 Apache Server Information...........................................................................................................12 Webalizer Usage Report................................................................................................................13 SSL-Enabled Apache................................................................
PAGE 5

List of Tables 1 Software Test Configuration...........................................................................................................
PAGE 6
PAGE 7

Introduction Executive Summary The HP Open Source Integrated Portfolio (HP OSIP) comprises a range of products and services designed to ensure that customers can successfully realize the cost and feature benefits of adopting open source software in their IT environments. HP Open Source Foundation components include the base components of an open source-based ecosystem: HP servers and storage are validated to run the Linux operating system together with commercial Linux distributions from Red Hat.
PAGE 8

Typographic Conventions This document uses the following typographical conventions. Command ComputerOut Ctrl-x ENVIRONVAR [ERRORNAME] Key Term UserInput VARIABLE \ (continuation character) ... | A command name or qualified command phrase. Text displayed by the computer. A key sequence. A sequence such as Ctrl-x indicates that you must hold down the key labeled Ctrl while you press another key or button. The name of an environment variable, for example, PATH.
PAGE 9

Figure 1 LAMP Environment Architecture Table 1 lists the software this is used to test the configurations described in this blueprint. Table 1 Software Test Configuration Software Package Version Apache Web Server Package Name Distributor Website Link httpd-2.2.3-11.e15 httpd-2.2.3-11.e15.x86_64.rpm Red Hat Apache httpd website MySQL 5.0.22 mysql-5.0.22-2.1.0.1.x86_64.rpm mysql-server-5.0.22-2.1.0.1. x86_64.rpm Red Hat MySQL website mod_ssl 2.2.3-6.el5 mod_ssl-2.2.3-6.el5.x86_64.
PAGE 10

NOTE: You must set a valid server host name prior to running an Apache HTTP Server to avoid an error. The Apache configuration files are located in /etc/httpd/conf and the main configuration file is httpd.conf. 1. Edit /etc/httpd/conf/httpd.conf and designate a valid hostname for the ServerName directive using the following syntax: ServerName :80 2. Restart Apache to force the changes to take effect by entering the following command: # /etc/init.d/httpd restart 3.
PAGE 11

3. Perform a concurrency request to the test system by logging into another system and entering the following command: # ab -c 1000 -n 1000 http:///abtest.html Where: The value of the -n option sets the number of requests. The value of the -c option sets the number of concurrency requests. 4.
PAGE 12

2. Restart the Apache HTTP Server for the changes to take effect. Use the following procedure to verify the server status and display the server information web page: 1. Verify the server status by opening a browser and entering the following URL: http:///server-status 2. Display the server information web page by opening a browser and entering the following website: http:///server-info The Apache Server Information web page opens, as shown in Figure 2.
PAGE 13

Using Webalizer to Perform Apache HTTP Server Log Analysis Webalizer is an analysis tool that you can use to generate detailed usage reports using the information recorded in the Apache HTTP Server logs. Webalizer provides easy-to-read reports in HTML format that you can customize for your needs. Use the following procedure to set up Webalizer: 1. 2. Open the file named /etc/httpd/conf.d/webalizer.conf with a text editor.
PAGE 14

NOTE: file. For Windows systems, edit the C:\WINDOWS\system32\drivers\etc\hosts www.website1.com www.website2.com 2. Verify that both websites are resolved to the same IP address by entering the following commands: # ping www.website1.com # ping www.website2.com 3. Create the following two directories: /var/www/html/website1 /var/www/html/website2 4. Create a file named /var/www/html/website1/index.
PAGE 15

This is www.website1.com In a second browser, enter the following URL: http://www.website2.com The following message appears: This is www.website2.com Using Apache HTTP Server URL Redirection The following procedure illustrates the use of the URL redirection feature which allows you to configure the Apache HTTP server to send requests for one URL to another URL. This requires the use of two servers that are both running Apache HTTP server. 1. 2. 3.
PAGE 16

Order deny,allow Deny from all Allow from all 3. For the preceding changes to take effect, restart your second Apache HTTP server by entering the following command: # /etc/init.d/httpd restart 4. Using the benchmarking tool, test the Apache Proxy server using the third system, which acts as the web client: # ab -c 10 -n 10 -X :80 \ http:///test.html 5. View the access log file on the Apache Proxy server.
PAGE 17

2. Create an HTML file named /var/www/html/missing.html and add the following content:
The page you request does not exist! Local redirects example
3. 4. Restart the Apache HTTP server for the changes to take effect.
PAGE 18

The following is an example for configuring per-user web directories: 1. Add a user named tester to your server by entering the following commands: # useradd tester # mkdir /home/tester/public_html # chmod 755 /home/tester/public_html 2. Create an HTML file named /home/tester/public_html/index.
PAGE 19

2. Create a sample test file named /var/www/html/Testphpmysql.php by adding the following code to the file: ; $dbuser = ; $dbpass = ; mysql_connect($dbhost, $dbuser, $dbpass) or die ('Error connecting to mysql:'.mysql_error()); printf('MySQL Version:'); printf(mysql_get_server_info()); mysql_close(); ?> 3. Launch a browser and navigate to the following website to verify PHP and MySQL are working: http:///Testphpmysql.
PAGE 20

4. Restart the Apache server by entering the following command: # /etc/init.d/httpd restart 5. Verify that Perl and MySQL are working by navigating to the following website: http:///Testperlmysql.pl The test page opens and the following message is displayed: MySQL Version: 5.0.22 Integrating Apache HTTP Server with Python and MySQL The mod_python module embeds the Python environment into the Apache Web server.
PAGE 21

Secure the Web Server Stack This section covers web server security. • • Data Transportation—Secure Sockets Layer (SSL) is a widely used technology to protect data transfer. It provides secure communications by encrypting the data on public or private networks. Application Authentication— Apache Web server provides a built-in authorization module to enable access protection.
PAGE 22

3. Verify that the HTTPS support in Apache is enabled by navigating to the website at: https:// The certificate is displayed as shown in Figure 4. Figure 4 SSL-Enabled Apache Apache HTTP Server Authorization The Apache default document root is: /var/www/html A directory named test must exist in the document root directory. In the following sections, access to the test directory is restricted, and that access to the directory for TESTNAME using the password PASSWORD has been granted.
PAGE 23

3. Modify the value of the data item as follows: AllowOverride AuthConfig Creating a Password File Create a password file to contain the HTTPS server passwords using the following steps: 1. Create the password directory by entering the following command: # mkdir /etc/httpd/conf/passwd 2.
PAGE 24

mod_authnz_ldap uses the domain name (DN) of the entry and the password provided by the HTTP client to bind the directory server. Configuring CDS and LDAP Services Use the following procedure to configure the CDS and LDAP services: NOTE: In the steps for this procedure: rootdn is set to"cn=Manager,dc=example,dc=com" rootpw is set to secret in the slapd.conf file 1. Create a file named webbase.
PAGE 25

1. Edit the following file: /etc/httpd/conf/httpd.conf Verify that the preceding file contains the following modules: LoadModule ldap_module modules/mod_ldap.so LoadModule authnz_ldap_module modules/mod_authnz_ldap.so 2. Create the following file: /var/www/html/foo/index.