You are here: UK Essays » Essays » Information Technology » System Design Development

Cookie Information

Privacy Information

System Design Development

This chapter aim to develop an Intranet system in order to provide as much as possible resource and also the way to communicate between user and user especially in order to deliver as much as possible for educational purpose. Beside the implementation, this chapter also provide with some description about the some technical processing. The objective of this installation will be shown in Figure 7.1.

In this chapter we will introduce not detail but only a brief about how to install and implement windows server 2003 as the Web Server operating system. We also install and implement some necessary Windows components such as IIS 6.0, DNS to make the Web Server meaning full. Beside Windows components we also need to install and configure some software in order to make the web site for the Web Server more and more color full (for instant MySQL and PHP).

Because of this case study have a minimum limit of time; we cannot develop our own portal for system testing. On the other hand we are going to use a free Content Management System (CMS) web portal for system testing.

Figure 7.1: The concept of system design

7.2 Hardware implementation

7.2.1 Network History

In the early 1980s, when desktop computers began to proliferate the business world, the intend of their designers was to create machines that would operate independently of each other. The computing ideal was summed up with the phrase “One User, One Computer,” which means that individual was free to manage information on their own desktops any way they linked.

This attitude was a reaction to the business-information environment of the time, based on large mainframe computers controlled by technical specialist and programmer. If you wanted information-a report on the aging of your accounts receivable, for instant-you made a request to the Information Services (IS) department, who would program the computer to provide the report for you. The report could take any length of time to produce, depending on its complexity, and your only choice was to wait while IS massaged your report out of the mainframe. Once you got the report, if you didn't like its format or if the information in it wasn't clear for any reason, you would make another request to IS, wait some more, and hope the revised report was useful.

The market for desktop computers explored, and dozens of hardware and software vendors joined in fierce competition to exploit the open opportunity for vast profits. The competitions spurred intend technological development, which led to increased power on the desktop and lower prices. Desktop computers were soon outperforming older, slower mainframe applications, accomplishing what appeared to be miracles in desktop publishing, graphics, computer-aided drafting, more powerful databases, and sophisticated user interface. Small businesses in particular were able to benefit from information management services that, a few years earlier, have been available only to wealthy corporations. Market place competitions created large numbers of computer from different manufacturers and vendors, large number of applications, and the unimaginably vast amount of information stored in desktop systems.

The large volume of information now being handled, it was impossible to pass along paper copies of information and ask each user to reenter it into their own computer. Copying files on to floppy disks and passing them around was a little better but still took too long and was impractical when individuals were separated by great distances. And you could never know for sure that the copy you received on a floppy disk was the most current version of the information—the other person might have updated it on their computer after the floppy was made.

For all its speed a power, the desktop computing environment was sadly lacking in the most important element: communication among members of a business team.

The obvious solution was to link the desktop computers together and link the group to a shared central repository of information. The problem was, desktop computers we not designed with this capacity in mind, and there were now thousands for theses machines in the marketplace representing billions of dollars in business assets. Few users were willing to scrap their desktop machines altogether and replace them with new, redesigned machines (and new software) that would communicate with each other this way.

Besides, computer manufacturers were quite cleaver, and they were able to create additional components that users could attach to their desktop computers, which would allow them to share data among themselves and access centrally located sources of information. Unfortunately, they early designs for theses networks were slow and tended to break down at critical moments. The desktop computer continues to evolve. AS it became faster and more powerful, capable of addressing much larger amounts of processing memory and thereby incorporation more sophisticated and complex features, communication between desktop computers gradually became more reliable. The idea of a Local Area Network (LAN) became a practical reality for businesses.

Computer networks, with all their promise and power, are more complicated to maintain that simple stand-alone machines. They require ongoing attention from managers whose job it is to oversee the networks and keep them running smoothly. Ironically, this concept looks a lot like the old mainframe paradigm, where a specialized cadre of technical insiders held near-absolute power to make information available. In some ways, it now appears as if business computing has come full circle, from IS to desktop and back to IS again

Over the past few years, internet technology has become more cost-effective and easier to use. Internet access sites have proliferated. AS the Internet Has grown and evolved in just a few years, it has become host to the World Wide Web, a community of thousands of business, educational, and personal information sites. Users can tap into these web sites using special software, called Web browser (e.g. Internet Explorer, Mozila Firefox, Netscape, Opera etc,..)

Networks now take a whole variety of forms: They can exist within a single room, an entire building, a city, a country, or the world. There are networks of networks, and there are networks that access each other at will or at the whim of individual users who can contact them any time over telephone lines.

• Benefit of Computer networking

• Networks allow more efficient management of resources. For example, multiple users can share a single top-quality printer, rather that putting duplicate, possibly lesser-quality printers on individual desktops. Also, networks software license can be less costly separate, stand-alone license for the same number of users.

• Networks help keep information reliable and up-to-date. A well managed, centralized data storage system allows multiple users to access data from difference locations and to limit access to data while it is being processed.

• Networks allow workgroups to communicate more efficiently. Electronic email and messaging is a staple of most network systems, in addition to scheduling systems, project monitoring, online conferencing, and groupware. All these things help work teams be more productive.

• Networks helps businesses services their clients more effectively. Remote access to centralized data allow employee to service clients in the field and clients to communicate directly with suppliers

• Networks greatly expand a business's marketing and customer service capacity. Using Internet technology, a business can automate its ability to inform customers about its products and services, take orders directly from customers, and provide up-to-the-minute facts are figures to be accessed at the customer's whim, anytime day or night.

• Network Protocol

• What Are Protocols? Protocols are the agreed-upon ways that computers exchange information. A computer needs to know exactly how message will arrive from the network so it can make sure the message gets to the right place. It needs to know how the network expects the message to be formatted (for instance, which part of the message is data and which part of the message identifies the recipients) so the network can convey the data to its destination.

• Hardware Protocols: Hardware protocols define how hardware devices operate and work together. The 10baseT Ethernet devices will exchange information and what they will do if it is improperly transmitted or interrupted. It determines such things as voltage levels and which pairs of wires will be used to transmission and reception. There is no program involved; it is all done with circuitry.

• The Hardware-Software Interfaces: Whenever program in a computer needs to access hardware; such as when a message has arrived from the network and is now waiting in the adapter card's memory, ready to be received, the computer program uses a predefined hardware-software protocol. This basically means that the computer program can expect the data to always be in the same place; that certain registers on the card will indicate what is to be done with it; and that when other registers are accessed in the proper order, the card will do something logical, such as receive another message or send a message out.

• Software Protocols: Program communicates with each other via software protocols. Network client computers and network servers both have protocol packages that must be loaded to allow them to talk to other computers. These Packages that must be loaded to allow them to talk to other computers. There packages contain the protocols that computer needs to access a certain network device or service.

Common type of Network Protocol:

+ NetBIOS and NetBEUI: Back when IBM first started marketing their PC Network, they needed a basic network protocol stack, which is an implementation of a board driver, transport protocol, and redirector. Network Basic Input/Output System (NetBIOS) is just 18 commands that ca create, maintain and use connections between PCs on a network. IBM soon extended NetBIOS with the NetBIOS Extended User Interface (NetBEUI), which basically is a refined set of NetBIOS commands. However, overtime the names netBEUI and NetBIOS has taken on new meanings.

- NetBEUI: now refers to the actual transport protocol. It has been implemented in many different ways by difference vendors, to the point where, in some ways, it is the fasters transport protocol for small Networks.

- NetBIOS: now refers to the actual set of programming commands that the system can use to manipulate the network—the technical term for such a set of commands is an Application Programming Interface (API)

+ IPX/SPX: The most popular local-area network type in the world is Novell Netware. When the Novell folks were building NetWare, they decided to build their own protocol rather than use an existing protocol. The Novell protocol is named IPX/SPX, for Internetwork Packet Exchange/Sequenced Packet Exchange. Since it is the protocol used most often on Netware networks, and since Microsoft wanted its software to be somewhat compatible with NetWare networks, Microsoft designed Windows 98 up to include an IPX/SPX implementation.

+ Apple Talk: is the name given to the protocol suite designed for the Apple Macintosh machine to communicate each other. Apple Computer began the development of AppleTalk in 1983

+ TCP/IP (Transmission Control Protocol/Internet Protocol) It is the most famous protocol and widely implemented in the computer networking. It was created over many years by the U.S. government. The protocol is actually a protocol stack, called the TCP suite. The TCP suite is a very efficient, easy-to-extend protocol whose main strength has been in wide-area networking; it glues together dissimilar networks and brings together similar networks that are separated by distance and low-speed connection. It's one of the best supported and best-designed internetworking protocols around.

• Network Operating System (NOS):

The NOS is the computer software that runs on the network server and offers file, printer, application and other services to the clients. It acts as the director to keep the network running smoothly. There are some popular NOS such as: Ms Windows NT, Ms Windows 2000 server, Ms Windows 2003 server, Unix, Linux, Sun Solaris, Novel Netware. There are 2 major types of NOS:

Peer-to-Peer: Peer-to-peer network operating systems allow users to share resources and files located on their computers and to access shared resources found on other computers. However, they do not have a file server or a centralized management source. In a peer-to-peer network, all computers are considered equal; they all have the same abilities to use the resources available on the network. Peer-to-peer networks are designed primarily for small to medium local area networks. The NOS such as AppleShare, Windows for Workgroups...

Client/Server: Client/server network operating systems allow the network to centralize functions and applications in one or more dedicated file servers. The file servers become the heart of the system, providing access to resources and providing security. Individual workstations (clients) have access to the resources available on the file servers. The network operating system provides the mechanism to integrate all the components of the network and allow multiple users to simultaneously share the same resources irrespective of physical location. The NOS such as Novell Netware, Windows Server...

• Server Implement

• Ms Windows 2003 overview

Microsoft has put an immense amount of time and effort into building Windows Server 2003. It's not fair to say that this operating system is an entirely new product because it still retains a great deal of core code from Windows 2000 and even Windows NT. Ms Windows server 2003 is a large, complicated, and very powerful operating system. To use it effectively, you have to understand how it works and how to make it do what you want it to do. There are 4 types of Ms Windows 2003 server in both 32-bit and 64-bit versions: such as Ms Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition and Web Edition.

• Ms Windows Server 2003, Standard Edition

Designed for departmental and standard workloads, Windows Server 2003 Standard Edition delivers intelligent file and printer sharing, more secure Internet connectivity, centralized desktop policy management, and Web solutions that connect employees, partners, and customers. Windows Server 2003 Standard Edition provides high levels of dependability, scalability, and security. See table 7.3.1

Table 7.3.1: Minimum system requirement for Ms Windows server 2003 Standard Edition:

Source : http://www.microsoft.com

• Ms Windows Server 2003, Enterprise Edition

This windows Designed for business-critical applications. Windows Server 2003 Enterprise Edition builds on the standard features found in the Windows Server 2003 family by adding features designed to increase the reliability scalability, security, and manageability of enterprise applications. This paper provides an introduction to the major technical features in Windows Server 2003 Enterprise Edition and discusses the application of those features to mission-critical applications, such as e-mail, databases, and business applications. See table 7.3.2.

Table 7.3.2: Minimum system requirement for Ms Windows Server 2003 Enterprise Edition:

Source : http://www.microsoft.com

• Ms Windows Server 2003, Datacenter Edition:

Designed for the highest levels of scalability and reliability, Windows Server 2003, Datacenter Edition, supports mission-critical solutions for databases; enterprise resource planning software; high-volume, real-time transaction processing; and server consolidation. Windows Server 2003, Datacenter Edition, is available in both 32-bit and 64-bit versions through original equipment manufacturer (OEM). See table 7.3.3

Table 7.3.3: Minimum system requirement for Ms Windows Server 2003, for Datacenter Edition:

Source : http://www.microsoft.com

• Ms Windows Server 2003, Web Edition:

Designed for dedicated Web serving and hosting, Windows Server 2003 Web Edition, delivers a single-purpose solution for Internet service providers, application developers, and others who use or deploy specific Web functionality. Windows Server 2003 Web Edition, takes advantage of improvements in Internet Information Services (IIS) 6.0, Microsoft ASP.NET, and Microsoft .NET Framework to make it easier to build and host Web applications, Web pages, and XML Web services. See table 7.3.4

Table 7.3.4: Minimum system requirement for Ms Windows Server 2003, for Web Edition:

Source : http://www.microsoft.com

• Installation Ms Windows 2003 server standard edition

7.3.2.1 Planning and Preparing:

• Prepare the Hardware: We need to know the minimum hardware requirement of each product and the product software CD. Your computer needs to be set boot from CD in the BIOS. Prepare the BIOS: Set your BIOS to 1^st priority boot CD ROM

• Partitioning: You should to partition your hard drive to at least 1 drive for system and other for data if you have. The minimum for system drive is 4 GB.

• File System. Choose the right file system for your system. The Windows 2003 server is recommended to use NTFS as the file system.

• Server Name: choose the right name for you server to identify the machine in the later use. The Server name is used in upper case. E.g FileServer, Server, Firewall, etc., we can put up to 63 characters. <<in name length in Internet>>

Note: you can easily change the name of the server later.

• Network Connection and Options: Not knowing your network configuration ahead of time isn't usually going to be a showstopper. Knowing it can save you time though.

Plug and Play, Regional and Language, and Name and Organization Screens

7.3.2.2 Installing:

The procedure is focus on new installation only, not for the upgrading. There are 2 phases for this installation:

Phase 1: Text based setup:

The part is very similar to Ms Windows 2000's text base setup or Ms Windows XP's text base. As soon as your machine boots into the text-based portion of Setup, you may notice a prompt at the bottom of the screen that tells you to press F6 if you need to install additional SCSI or RAID drivers. If you don't want these additional drivers, just wait a few seconds and it will go away. But if your system has a SCSI or RAID controller that you know isn't going to initialize without an EM-provided driver, you'll need to watch this part of Setup closely and hit F6. he install starts off with a Welcome to Setup screen. You have the choice to set up Server 2003, Repair an existing Server 2003 installation, or quit. The Press F3 to Quit option will live with you throughout this phase of the setup. If at any time during this phase you decide that you want to abort our setup attempt, this will be your escape route. Upon this exit, your system will be rebooted, but be aware that your boot.ini file will not have been changed. That'll take you to the Disk Partitioning and Installation Location Selection screen. Be careful here. There are two things to do. The most obvious is the selection of the partition in which you want Server 2003 installed. Highlight the partition where you would like Server 2003 installed, and press Enter. Let's take this a step further. Beneath this screen is a very handy disk-partitioning utility. From here, you can completely redo your partitioning scheme. You can delete existing partitions, create new partitions out of unpartitioned space, and format partitions in either the NTFS or FAT format file systems.

Phase 2: Graphical text-base setup:

As soon as you boot into the graphical-based setup phase of the install, Server 2003 will run a Plug-and-Play detection phase to configure all your hardware. This can take quite a while, and because disk

formatting and file copying (both in Phase 2) take some time and Setup reboots itself and moves directly to the PnP detection phase, the format, copy, and PnP detection's done, and I can start answering the wizard's questions, such as

• Plug and Play, Regional and Language, and Name and Organization Screens,

• Products Key and Windows Product Activation

• License, Names, and Password

• Time and Time Zone

• Network Setting

• Computer account

After finishing phase 2, the computer will reboot automatically and start the Windows 2003 server

7.3.2.3 Post installation procedure

After the installation is complete, there are still a few more steps to perform to finalize the server and prep it for production:

• On the first reboot, the Manage Your Server page will pop up automatically. It will identify the last few steps that must be completed to configure your server based on the additional network components you installed. It will also ask you some questions about your existing network to help you determine whether you want to install an Active Directory. I personally find the Manage Your Server page unhelpful and tend to just close it, but that's just my opinion—try it if you like. I'll show you how to manage your server with as few of those dumb wizards as possible!

• Check your device manager for undetected or nonfunctioning hardware components. If you removed any hardware prior to the install due to conflicts, add them back in now. Before you are truly done with the install, every piece of hardware should work properly.

• You'll want to finalize your disk partitions. In many clean install scenarios, you may have un partitioned space left on your hard drive.

• For most new installations using TCP/IP, a DHCP address will be in effect. This may not be a standard practice for production servers. If necessary, acquire and configure the appropriate static TCP/IP information.

• In many larger network environments, certain services, utilities, tools, or other programs are loaded on all servers. For example, some sites may utilize enterprise management tools that require the usage of an agent that runs on the server to collect and pass information up to a management console. Most likely, some sort of backup software will need to be installed also. Find out what additional software is needed and install it now.

• Run through the Control Panel applets to set all server configurations the way they should be for the long haul. Especially noteworthy are the System Control Panel settings for the page file and maximum Registry size.

• At this point, you may get the urge to walk away. Well, hold on just a minute. Too many times, people make some last-minute changes, like the Control Panel settings, and leave it at that. Even though you were never told to reboot the system—your changes were instantly accepted—there may be some unexpected side effects the next time you reboot. Just in case, give it another reboot now, before your users begin counting on the server being available.

• If the system is a dual-boot machine, which is usually not the case on a server, boot into all operating systems to make sure the system integrity is intact and all data is available from all required operating systems.

• Once the system itself is complete, create an automated recovery disk. And as an extra safeguard, you may also want to run a full backup.

• Finally, a step we rarely perform is documenting the server. Ask yourself if anyone else could take care of the server should you decide to take a week off for a golf vacation. If there are any special things you have to do, like restart a service every day, it should be documented. This is a step you must take before you can consider your operating system “installed.”, which covers preparing for and recovering from server failures, for more details.

7.4 Installation Ms Windows 2003 server components

There are some components in Ms Windows 2003 that originally not install after we have complete installing the OS in which we need to the WEB Server.

• Internet Information Service (IIS)

Internet Information Services (IIS) is really a suite of TCP/IP-based services all running on the same system. Although some of the services rely on shared components, they are functionally independent from one another. Just as an electrician has different tools for different jobs, IIS has different Internet capabilities to help meet different needs. With the release of Windows Server 2003, Microsoft has reached version 6 for internet Information Services. The following sections will briefly discuss some of the web application server functionality included with IIS 6:

• World Wide Web (HTTP) Server: IIS includes an HTTP server so that you can publish data to the World Wide Web quickly and easily. IIS's Web service is easily configurable and reliable, and it supports security and encryption to protect sensitive data. You can use IIS's Web service to host a Web site for your own domain or multiple domains, an intranet, and the Internet, and even allow users to pass through your IIS Web server to access HTML documents on machines within your organization.

• File Transfer Protocol (FTP) Server Although the use of File Transfer Protocol is not the only way to send a file from one location to another, it is by far the most widely supported as far as the Internet is concerned. FTP was one of the original means of copying files from one location to another on the Internet, long before the days of graphical browsers, HTTP, and Web sites. Since the protocol has been around for so long, support is available on almost any platform, including midrange and mainframe systems that might not typically support HTTP. In IIS 6, the FTP service now includes support for individual user directories. This feature can be used to permit access to private directories while preventing users from seeing or writing to directories other than their own.

• Network News (NNTP) Server: Sometimes referred to as Usenet, Network News Transport Protocol (NNTP) is something, simply due to the great functionality it provides. By using Internet standards (RFC 977), the NNTP service can be used as a means of maintaining a threaded conversation database on an IIS server, just like in Usenet groups on the Internet. Users with properly configured newsreader programs can navigate through and participate in these conversation databases. Although services like Google Groups (http://groups.google.com ) have made Usenet better known, it still isn't as widely used as something like HTTP. That's unfortunate; NNTP represents a great cross-platform protocol for managing threaded conversation databases. Let's hope the inclusion of NNTP with IIS will increase the use of this capability.

• Email Services: Microsoft included an SMTP service with IIS version 5; however, it was not sufficient to act as a full-blown e-mail server for an organization. The SMTP service included with IIS 5 was only meant to support the other services within IIS—namely HTTP and NNTP. You see, the SMTP service included with IIS 5 was missing an important component—a POP3 or IMAP service. POP3 or IMAP is the means by which clients retrieve their specific messages from their mailbox on a mail server. SMTP provides a “store-and-forward” service for mail but does not support individual user

Setting up IIS service

Install IIS Service: Control Panel > Add and Remove Program > Add/Remove Windows Components > select on Application Server > click on the Details… button > select on the Internet Information Service > click on the Detail... button > check on Internet Information Service Manager > click the OK button twice time > then click the Next button to begin the installation. Insert the Ms Windows 2003 server CD that you used to install to the computer. Then wait till the IIS component has been installed successfully. See Figure 7.4.1.1

Figure 7.4.1.1 IIS installation

*Note

What we have been doing is the minimum configuration. To have IIS install properly we can keep default Web site as the default site so that we do not need to create a new one.

• Domain Name System (DNS)

This session will cover most with system configuration. On the other hand, some concept will be include but not in detail. For further about DNS server we recommend to read, Mastering Windows Server 2003, wrote by Mark Minaci, 2003.

7.4.2.1 DNS Fundamental

DNS began in the early days of the Internet when the Internet was a small network created by the Department of Defense for research purposes. Before DNS, computer names, or hostnames, were manually entered into a file located on a centrally administered server. Each site that needed to resolve hostnames had to download this file. As the number of computers on the Internet grew, so did the size of this HOSTS file, and the amount of traffic generated by downloading it. The need for a new system that would offer features such as scalability, decentralized administration, and support for various data types became more and more obvious. The Domain Name Service (DNS), introduced in 1984, became this new system.

With DNS, the hostnames reside in a database that can be distributed among multiple servers, decreasing the load on any one server and providing the ability to administer this naming system on a per-partition basis. DNS supports hierarchical names and allows registration of various data types in addition to the hostname-to-IP-address mapping used in HOSTS files. By virtue of the DNS database being distributed, its size is unlimited and performance does not degrade much when adding more servers.

7.4.2.2 What DNS Does

DNS translates between computer hostnames and IP addresses. DNS works at the Application layer of the OSI reference model and uses TCP and UDP at the transport layer. The DNS model is pretty plain: Clients make requests (“what's the IP address for www.google.com?”) and get back answers (“64.233.183.147”). If a particular server can't answer a query, it can forward it to another, presumably better informed, server.

7.4.2.3 Introduction to Domain Naming

The Domain Name System is composed of a distributed database of names that establishes a logical tree structure called the domain name space. Each node, or domain, in that space has a unique name. Therefore, bluesun.com and Cambodia.bluesun.net are two different domains, and they can contain sub domains, such as sales.bluesun.com and pp.cambodia.bluesun.net. A domain name identifies the domain's position in the logical DNS hierarchy in relation to its parent domain by separating each branch of the tree with a period. Figure 7.3.2.1 shows the domains hierarchy, where the Microsoft domain fits, and a host called server1 within the khzone.com domain. If someone wanted to contact that host, they would use the fully qualified domain name (FQDN) server1.khzone.com.

Each domain is associated with a DNS name server. In other words, for every domain registered in the DNS, there's some server that can give an authoritative answer to queries about that domain. For example, the chellis.netchellis.net domain is handled by a name server at an Internet provider. This means that any revolver or name server can go straight to the source if it can't resolve a query by looking in its own cache.

Figure 7.4.2.1: The Public DNS Hierarchy

7.4.2.4 DNS and the Internet

You're undoubtedly familiar with how DNS works on the Internet; if you've ever sent or received Internet e-mail or browsed web pages on the Net, you've got firsthand experience using DNS. Internet DNS depends on a set of top-level domains that serve as the root of the DNS hierarchy. These top-level domains and their authoritative name servers are managed by the Internet Network Information Center ( www.internic.com ). The top-level domains are organized in two ways: by organization and by country.

• Top-Level Domain: Below the root are top-level domains. Most of the ones we tend to think of around the world are .com, .net, info and .org, as they've become sort of the worldwide “catch-all” domains. Then, each country has its own top-level domain—the United States has .us, Canada .ca, the Cambodia .kh, and so on. In November 2000, Internet Corporation for Assigned Names and Numbers (ICANN) created several new top-level domains. The following is the sample of the top level domains.

• Second-Level Domain: The second-level domain can be created with the permission of the owner of the parent domain. To create the second-level domain, the parent domain only has to do one thing: “delegate” name responsibility for the second-level domain to some machine. That's an important concept.

• Sub domain or Child Domain: From the second-level domains you can divide into sub domains and delegate. If your namespace is large enough, you may need to divide it, too. Typically, you divide the domain that corresponds to your network number into sub domains that correspond to your subnets. How that works depends on the type of network you have and on your network's subnet mask.

Note: In internet world you can only create the second-level domain and child domain, but you can not create the Top level domain (it's predefined.)

Table 7.4.2.1: The command DNS name

Source: Wikipedia.org, at http://en.wikipedia.org/wiki/Generic_top-level_domain

• Servers, Clients and Resolvers: There are a few terms and concepts you will need to know before managing a DNS server. Understanding these terms will make it easier to understand how the Windows Server 2003 DNS server works:

• DNS servers: Any computer providing domain name services is a DNS server. That being said, not all DNS servers are alike. Earlier implementations of DNS (for example, early versions of the popular Berkeley Internet Name Domain, or BIND) were originally developed for Unix, and they handled a fairly small and simple set of Request for Comments (RFC: An official document of the Internet Engineering Task Force (IETF) that specifies the details for protocols included in the TCP/IP family.) requirements. There is also the concept of primary and secondary DNS servers to consider. A primary DNS server is the “owner” of the zones defined in its database. The primary DNS server has the authority to make changes to the zones it owns. Secondary DNS servers receive a read-only copy of zones through zone transfers (discussed later, in the section “Zone Transfers”). The secondary 0DNS server can resolve queries from this read-only copy but cannot make changes or updates. A single DNS server may contain multiple primary and secondary zones (more on zones in a minute). Any DNS server implementation supporting Service Location Resource Records (see RCF 2052) and Dynamic Updates (RFC 2136) is sufficient to provide the name service for Windows 2000 and newer computers. However, because Windows Server 2003 DNS is designed to fully take advantage of the Windows Active Directory service, it is the recommended DNS server for any networked organization with a significant investment in Windows or extranet partners with Windows based systems.

• Clients a DNS client is any machine issuing queries to a DNS server. The client hostname may or may not be registered in a name server (DNS) database. Clients issue DNS requests through processes called resolvers.

7.4.2.5 DNS Server installation and configuration:

• Install DNS component: To install the DNS component in Ms Windows 2003 server, go to Control Panel > Add and Remove Program > Add/Remove Windows Components>select on Networking Services > click on the Details… button > check on Domain Name System (DNS) > click the OK button. Insert the Ms Windows 2003 server CD that you used to install to the computer. Then wait till the DNS component has been installed successfully.

• Point the DNS server to its self: On the DNS server machine configure the DNS to point to itself. So when the server wants to resolve a DNS query, the server will need to ask it self to resolve names.

• To do it go Network Connections, right-click the NIC's name (e.g. Local Area Network,) choose Properties, click the General tab, then click Internet Protocol (TCP/IP) and the Properties button, and then click the radio button labeled Use the Following DNS Server Addresses and fill in the DNS server's IP address (e.g. 192.168.1.201)

• Configure DNS Server: Before we continuo configure on DNS Server let take briefly about primary DNS suffix.

• So first right click on My Computer> choose property> choose computer name tab> click on button Change…> click on button More…> the dialog box DNS suffix will appear as shown in Figure 7.4.2.2. As we describe above, we using DNS for translate from IP to the name so that it easy for user to remember. So that in this case we need to assign the DNS suffix for the server IP address. As we assume from the beginning to assign the DNS name khzone.com for IP 192.168.1.201, so just type khzone.com in the box. This is the actual domain name that we got. So what it going to happen. Together with NetBIOS computer name and DNS domain name Suffix will be form a full qualify domain name (FQDN) or the full name of the machine (server1.khzone.com). If we didn't configure this, this machine will be not part of the khzone.com. So when we do a forward lookup zone we cannot have to khzone.com as a DNS name. ok let click ok and continue to configure DNS server

Figure 7.4.2.2: DSN Suffix and NetBIOS Computer Name

• Go to the Administrator Tools > DNS (see Figure 7.4.2.3)

Figure 7.4.2.3 : DSN server configuration

• Configure new Forward lookup for Primary Zone for the DNS server: To record name to IP address. Right click on the Forward Lookup Zones> choose New Zone…>Click the Next button

• As this is the first time we configure DNS server in this machine, we need to choose Primary zone in top option and than click button Next. See Figure 7.4.2.4.

Figure 7.4.2.4 : Choose the zone type

• As we decide to choose khzone.com as the DNS name so just type khzone.com for the Zone name as shown in figure 7.4.2.5 and than click button Next, keep the default setting and click Next> Next> and Finish.

Figure 7.4.2.5: Choose DNS name

khzone.com

• The new primary zone after creating. As we only need the basic setup of the Web Server, this configuration may be enough for us.

7.4.3 MySQL

7.4.3.1 Introduction

In several of Relational Database Management system (RDBMS) MySQL in one in those, which also used on several type of website such as portal, e-commerce, education etc,. With the advantage of speed, the most important factor for every developer, and also offer few features, MySQL have more advance than their major competitors like Oracle. On the other hand, even though this RDBMS have less featured compare with their commercial competitor, but it have enough for large group of developer. With this less, so than make MySQL easier to install and use and the most important think is the price witch make MySQL more and more advance. (Valade, 2004)

MySQL is developed, marketed, and supported by MySQL AB, which is a Swedish company. The company licenses it two ways:

• Open source software: MySQL is available via the GNU GPL (General Public License) for no charge. Anyone who can meet the requirements of the GPL can use the software for free. If you're using MySQL as a database on a Web site (the subject of this book), you can use MySQL for free, even if you're making money with your Web site.

• Commercial license: MySQL is available with a commercial license for those who prefer it to the GPL. If a developer wants to use MySQL as part of a new software product and wants to sell the new product, rather than release it under the GPL, the developer needs to purchase a commercial license. The fee is very reasonable.

7.4.3.2 Advantages of MySQL^7.4.1

With the speed and size and price, MySQL is one of the most ideal for majority web developer. According to (Valade, 2004) there are several advantages of this RDBMS:

• It's fast. The main goal of the folks who developed MySQL was speed. Consequently, the software was designed from the beginning with speed in mind.

• It's inexpensive. MySQL is free under the open source GPL license, and the fee for a commercial license is very reasonable.

• It's easy to use. You can build and interact with a MySQL database by using a few simple statements in the SQL language, which is the standard language for communicating with RDBMSs.

• It can run on many operating systems. MySQL runs on a wide variety of operating systems — Windows, Linux, Mac OS, most varieties of Unix (including Solaris, AIX, and DEC Unix), FreeBSD, OS/2, Irix, and others.

• Technical support is widely available. A large base of users provides free support via mailing lists. The MySQL developers also participate in the e-mail lists. You can also purchase technical support from MySQL AB for a very small fee.

• It's secure. MySQL's flexible system of authorization allows some or all database privileges (for example, the privilege to create a database or delete data) to specific users or groups of users. Passwords are encrypted.

• It supports large databases. MySQL handles databases up to 50 million rows or more. The default file size limit for a table is 4GB, but you can increase this (if your operating system can handle it) to a theoretical limit of 8 million terabytes (TB).

• It's customizable. The open source GPL license allows programmers to modify the MySQL software to fit their own specific environments.

7.4.3.3 Setup and configuration of MySQL for Windows^7.4.2

To install MySQL on Windows follow these steps:

• Download the latest available for production use version of MySQL from the website http://dev.mysql.com./downloads/

• Double click on the file you just download to be installed.

• When the first screen of the installation wizard appear click next

• Because we need to control witch components need to be install click custom as shown in Figure 7.4.3.1 and next > next > next > Install. When the MySQL Sign-Up dialog box appear choose Skip Sign-Up option and then click next to continuo configuration. See Figure 7.4.3.2

Figure 7.4.3.1:

Finish the setup and continue configure

Figure 7.4.3.1:

Select the installation type

• Once the new configuration popup click next see Figure 7.4.3.3

Figure 7.4.3.4:

Detail configuration

Figure 7.4.3.3:

Configure MySQL 5.0 for Window

• Because we have been sticking with the detail configuration, so just keep with that. Figure 7.4.3.4

• Read the option and click the one which best for you. If you install MySQL on your desktop machine for some development task, the first one just fine. But now we install for web server so option tow is the best at the moment so choose the option two as shown in Figure 7.4.3.5.

Figure 7.4.3.5:

Choose server type

Figure 7.3.3.6:

Using the storage technique

• Choose Non-Transactional Database Only and click next Figure 7.4.3.6.

• Choose the third option and modify the number to 100 and than click next Figure 7.4.3.7.

Figure 7.4.3.8:

Configure port for security purpose

Figure 7.4.3.7 :

Choose the amount of user

• As long as you don't have any copy of MySQL in your system the port number 3306 just fine. Keep the Enable Strict Mode on as shown in Figure 7.4.3.8 and click next.

• This step seems to be a tricky setting. It should be the best to choose option two, UTF8 the default character set which allow supporting different languages, to be installed. But the problem is the PHP up to including version 5.1 doesn't have strong support for UNICODE build in. So most of PHP code assuming MySQL using Latin1 character set to communicate. So choose option one (Standard Character Set) and click next. See Figure 7.4.3.9.

Figure 7.4.3.10:

Configure MySQL 5.0 for Window

Figure 7.4.3.9:

Choose the language type

• Click check on Install as windows Service. Even though MySQL nowadays can modify by Graphic User Interface but it still need the command line for some configuration. So keep the option Include Bin Directory in Windows PATH on and click next. Figure 7.4.3.10.

• Disable the Modify Security settings option and click next and then Execute and finish. After the configuration finish we need restart the service to make MySQL work properly. See the Figure 7.4.3.11 and 7.4.3.12

Figure 7.4.3.12:

Configure MySQL 5.0 for Window

Figure 7.4.3.11:

Disable the user and password

• After the MySQL setup and running, the first business is we should setup the username and password for security reason. To do so, go and fine the command line client from: go to the start menu > all Programs > MySQL > MySQL Server 5.0 > MySQL Command Line Client. The command line it the most primitive but also some time the most effective way to interacted with MySQL Database. When the Command Line Client appears it will request to type the password. As we didn't set the password yet just press Enter.

• After we press the Enter MySQL prompt will be appear for wait to type the command.

Figure 7.4.3.13: Setup Username and

Password

• To make the password for the root user type the following command

mysql> UPDATE mysql.user SET Password=PASSWORD(“mypass”) WHERE User=”root”;

• The command line for MySQL is case sensitive. All the SQL command line should be finish by semi colon “;”. When you all have the command right, press enter.

• In order to make the new password to have effect we need to enter one more command.

mysql> FLUSH PRIVILEGES;

7.4.4 Install PHP on IIS

7.4.4.1 Introduction^7.4.1

PHP is a scripting language which designed specifically for use on the Web. It is the tool for creating dynamic Web pages which available in over 13 million domains world wild (according to the Netcraft survey at www.php.net/usage.php, 2004), and keep growing everyday.

PHP was early development by a guy called Rasmus Lerdorf as a Personal Home Page tools during that time. When it developed into a full-blown language, the name was changed to be more in line with its expanded functionality.

The syntax of this language is similar to the syntax of C, so that it makes the programmer who already familiar with C easier to adapted with PHP. Further more, PHP design for the concept of web development, so it syntax didn't required as strong as C which meant that it doesn't use some of the more difficult concepts of C. Also, PHP syntax doesn't include the low-level programming capabilities of C.

PHP is particularly strong in its ability to interact with databases. PHP supports pretty much every database you've ever heard of (and some you haven't). PHP handles connecting to the database and communicating with it. You don't need to know the technical details for connecting to a database or for exchanging messages with it. You tell PHP the name of the database and where it is, and PHP handles the details. It connects to the database, passes your instructions to the database, and returns the database response to you.

The popularity of PHP is growing rapidly because of its many advantages:

• It's fast. Because it is embedded in HTML code, the response time is short.

• It's inexpensive — free, in fact. PHP is proof that free lunches do exist and that you can get more than you paid for.

• It's easy to use. PHP contains many special features and functions needed to create dynamic Web pages. The PHP language is designed to be included easily in an HTML file.

• It can run on many operating systems. It runs on a wide variety of operating systems — Windows, Linux, Mac OS, and most varieties of Unix.

• Technical support is widely available. A large base of users provides free support via e-mail discussion lists.

• It's secure. The user does not see the PHP code.

• It's designed to support databases. PHP includes functionality designed to interact with specific databases. It relieves you of the need to know the technical details required to communicate with a database.

• It's customizable. The open source license allows programmers to modify the PHP software, adding or modifying features as needed to fit their own specific environments.

7.4.4.2 Install PHP on IIS 6.0^7.4.2

• Download the latest windows binaries zip package from web site www.php.net

• Extracted the contain file you just download to a directory let say c:\php

• Find the files call libmysql.dll and php5ts.dll from the directory you just extracted

• Copy and paste those two files to system32 folder in your system

• Find the file call php.ini-dist from php directory you been extracted and make a copy of it. Rename a copy from php.ini-dist to php.ini

• Move php.ini file to your Windows directory

• Open php.ini file with notepad (the one in Windows directory not in php directory)

• Find the line extension_dir in your php.ini and change the value to the one you install your PHP and add back slash ext on it (\ext). See Figure 7.4.4.1. This tells PHP all the library extension option that could be switch on and off to give the several of functionality. One of this functionality is allow PHP to communicate with MySQL database

Figure 7.4.4.1: Configure the extension directory for PHP

• Scroll down to fine the line extension=php_mysql.dll and remove the semi-colon “;” from the first lint. Make a new line and type extension=php_mysqli.dll

• Finally scroll down until you find the sessions option and find the line session.save_path= “/tmp”. This point PHP store the temporary information where people visiting the site. Uncomment this line and pointed to the convenient directory in your system. Save and close the file.

Configure PHP for IIS 6.0

In this configuration we assume that IIS 6.0 already install in the system.

• Open the IIS manager console from administrative tool > navigate to Default web page and choose property.

• When the property window appears choose ISAPI Filters tab and click Add… See Figure 7.4.4.2.

Figure 7.4.4.2: Configure the IIS Property for PHP

• Type for the filter name PHP and on the executable click browse…

• Got to your file directory and select the file php5isapi.dll and click open Figure 7.4.4.3

Figure 7.4.4.3: Choose the file Filter of IIS for PHP

• Now we have PHP load as a filter so that it can respond and request to a server. But we still need to tell IIS which file that work with the PHP script.

• Go to home directory tab and click configuration, see figure 7.4.4.4.

Figure 7.4.4.4: Configure Home Directory

• Click Add… for add a new application mapping and for the executable choose php5isapi.dll and for the extension type “.php” then click ok. Figure 7.4.4.5.

Figure 7.4.4.5: Configure PHP Extension

• Finally go to the Documents tab. The documents tab control the file name that it search for when the browser only request a directory name on the server. In order to allow PHP script are able to do so we need to add index.php in the list and move it to up most if you work the most with php and than click ok. We also need to restart the server to make PHP successfully. Figure 7.4.4.6.

Figure 7.4.4.6: Add the index.php to IIS

• This session adapt from Valade, J. (2004), PHP & MySQL For Dummies, 2nd Edition. Indiana: Wiley Publishing. Page 12-14.

• Meloni, J. (2007), Teach Yourself PHP, MySQL and Apache: All in One, Third Edition. Los Altos: Sams. Chapter installing MySQL on Windows

Sign up and be the first to receive our latest offers: