RedHatLinux network server architecture practice (1)

Preface

Here I will explain the motivation, purpose, content, principles and usage of this document.

I am mainly engaged in network development. The main technical solution I use is FreeBSD/Linux + MySQL/Oracle + JavaBean/EJB + Jsp, that is, the layer-4 structure (some people think it is a layer-3 structure, but the interface layer concept is added to J2EE ). During project development, server architecture is often required. After each configuration, I write a simple configuration document as part of the project technical document. This document is the result of my configuration again and again. I have written some of the common parts used to build network servers into this document. One can be used as a Installation Guide for beginners, second, you can listen to your opinions and suggestions to make them more rigorous and complete.

This document aims to build a standardized RedHat development server as the development environment of the project. This document provides 17 Simple and comprehensive steps to configure DNS, FTP, MySQL, Apache, JVM, Resin, PHP, and other servers.

The following are the principles for writing this document:

1. Try to be concise: Remove any unnecessary steps; make the command speak with only necessary comments to facilitate your use as a configuration list. This document mainly tells readers how to do this and rarely explains why (this has been improved in this version). However, note that, if you ignore any of these steps, subsequent errors may occur;

2. Comprehensive System: the steps go through the entire process from operating system installation to configuration completion. Beginners can do this step by step. server configuration is a system process, many instruction documents only describe the configuration methods of a certain software, and do not take into account the overall planning, So copying often fails;

3. Strive for rigor: This is one of my goals and is also one of the reasons for my release. Of course, this can only be achieved through testing;

4. Stay up to date: All software, including the operating system, is the latest version as of the document release date. If a new software version appears, I will try to update it in time;

5. Featured software: the software mentioned in this article is familiar to everyone and only needs to be explained. 1. Why do we use Redhat instead of FreeBSD? FreeBSD is the best network operating system on Intel, but it has poor support for JAVA (especially the new JDK version, I used FreeBSD as a JAVA development platform for a long time. However, since SUN has not released the JDK on FreeBSD, it has often caused system crashes; why do I use Resin without using Tomcat? Although Tomcat is a project organized by Apache, it is continuously improved, but there is still a certain gap with Resin; resin has excellent performance in Chinese support, execution efficiency, customization, upgrade speed, and support for J2EE, which I have personally learned; although I doubt its performance in terms of high-end applications and system load, it should be more than enough to deal with small and medium Web projects;

6. JSP: Mainly used to build a JSP development environment. It can be used as a server configuration manual for beginners of JSP: 1. RH7.2 enhances multi-language support, if you select the i18n Simplified Chinese package when selecting a language during the installation process, and the Resin provides excellent support for Chinese, you do not need to declare Content-Type (no declaration is required in any way), and the Chinese language will be automatically supported. This is also described in this document. Second: the Resin connection pool configuration and call methods are provided, and a component is provided for database connection and processing. The third is the detailed method for adding a JSP virtual host, from DNSFTPAPACHE to Resin; 4: points out the support methods of JDBC2.0 and provides code for testing;

7. Compilation and installation: All software is compiled and installed, which is beneficial to system customization and system stability;

8. target readers: The Configuration Wizard for Linux beginners and the reference for advanced readers;

9. Configuration goals: This document is currently the most suitable configuration manual for internal enterprise development servers. If you are an Internet server, you need to consider a lot of security factors, at least not all of which should be installed, xserver does not need to be installed. Internet servers not only need the features mentioned in my document, but also require a simple and secure system;

10. Clear functions: I located my server on a DNS + FTP + MySQL + Apache + Resin + Php Web development server and removed dispensable services. Therefore, the configuration methods such as QMAIL, ORACLE, ASP, and FrontPage are not mentioned in this document. In addition to feature separation and reader requirements, the best operating platform for Oracle is SUSELinux, and the best operating platform for ASP is NT. As for Qmail, you can add more Versions later;

The following describes how to use this document:

1. Color Description:
Dark blue: modified or added in the original document
Dark green: My comments
2. symbol description
#: Original notes in the system or software configuration document;
#: I will explain the subsequent paragraphs
//: My Line End description
/*... */: Long description
3. Command description:

I am used to using vi to edit a file. If you do not like this tool, you can use visual editors such as AdvancedEditor or other commands such as mc.

Occasionally, I add shell> before the command to indicate that this command is different from the file content, but this version is Chinese, so I generally do not add this symbol.

Make and makeinstall can be replaced by make and makeinstall, but we recommend that you execute them separately to facilitate viewing the prompt information of each step.

./Appears in many places in the text. There is no space in the middle, and the dot number is not obvious. Note that.