Chapter 5

An Intranet Shopping List


CONTENTS

Part I, "Introducing Intranets," laid out the basics:

With this foundation, you are ready to build your intranet. What do you need? What do you want? What are your costs? What will you get for the money? The answer is simple-anything you want. There have been intranets built with Scotch tape and baling wire. Some intranets that work well and are functional cost only a few hundred bucks. On the other hand, large corporations, such as Ford and Silicon Graphics, have spent millions on their intranets. It really depends on your intranet dreams and wish list. Here I'll help you create a shopping list of products to make your dream intranet come true, as shown in Figure 5.1.

Figure 5.1: Your shopping list might include categories for both server and client machines.

Choosing Server Hardware for Your Intranet

As discussed in previous chapters, intranets are built on a client/server principal, which means to utilize an intranet you must have clients and servers in place. Chances are you probably already have client machines you can use, and perhaps even servers. Chapter 4 "Client/Server Basics and Theory," covered the differences between the two, so the first part of this chapter is devoted to the most important part of your intranet-the server machine. Depending on the size and purpose of the intranet, the server hardware can consist of anything from a 386 desktop computer to one or several Sun Sparc Ultra computers. Figure 5.2 shows some examples of server hardware you can use. It just depends on what you want your intranet to accomplish.

Figure 5.2: You have a variety of options when it comes to choosing servers for your intranet.

If your intranet goal is as simple as running a Web server to host 30 to 40 users and post HTML pages, you probably don't need much more than a 386 or 486 processor. You certainly should have a decent amount of RAM on the machine-at least 16 to 24MB. You'll also want a good-sized hard drive that is at least twice the size of all the files you plan to add in the next year. You will also need a large disk cache and an httpd. httpd stands for hypertext transfer protocol daemon, the program that runs on your server and responds to Web requests. httpd is just another name for a Web server.

The next level of server might include a medium-sized intranet for 50 to 75 users that hosts a Web server, a mail server, possibly a gateway into a database, and/or audio-conferencing. In this scenario, you'll want at least a 486 processor, but probably a Pentium, PowerPC, or Macintosh clone, such as a Power Computing machine. This intranet would require at least a 2-gigabyte hard drive and a minimum of 24MB of RAM.

These first two scenarios can incorporate the computers currently sitting on someone's desk. Depending on the operating system in use, it may not even be necessary to buy a new computer for a server. If the goal of either of these intranet scenarios is to perform regular mail and Web service and to communicate internally with a local area network (LAN), the intranet may require just one computer.

If you find yourself in one of these scenarios, I recommend one of two server solutions. You could designate the least-used computer as the server; then this computer would be load-balanced. With most operating systems, including Windows 95, Windows NT, and MacOS, Web and mail servers can run in the background without noticeable impact. With Windows 3.1 or Windows for WorkGroups it might slow down a bit but still probably won't be that much slower. It's similar to hooking your computers to a LAN and accessing information from another computer on the LAN; users don't really notice, unless there is a lot of activity. The other server solution is to find the person who uses his or her computer the most, such as the resident geek or the systems administrator, and run the Web server on his or her machine. In this case, you can be reasonably assured that the server will run most of the time. And, it's even possible that person will upgrade the software and make sure that server issues are dealt with immediately. It's also likely this person has the best and fastest computer. If that's the case, the effects of running the Web server likely will be felt the least. Certainly, if the organization wants to host several Web servers, such as for different departments, this can be done on different machines. The vice president of finance might have a Web server on her machine, while the vice president of manufacturing also has one on his machine. As you can see, servers come in many shapes and sizes. You may realize you can have a fully stocked server on existing desktops, or you may have to do some shopping.

The next level of an intranet might be a large corporation or trade association. An intranet in either of these scenarios typically will have several hundred users. It likely will run mail and Web servers, have a database gateway, and run advanced communications software, like message boards and scheduling. It might even have audio- and video-conferencing. A server capable of hosting this number of applications will vary widely in cost and performance.

How fancy your purchase is and how much money you put down on such a server really depends on how much use you will get out of your intranet. For example, if most users use it occasionally or a few users use it a lot, a fast Pentium processor with 24 to 40MB of RAM might serve all the intranet's needs. With any more use than this, you should move to either a dual-processor Pentium or a minicomputer, such as a Sun Sparc 5 or DEC alpha. Even a small minicomputer, like a Sun Sparc 5, will be much faster than any Pentium-based machine. Of course, it's also possible to split responsibilities between two servers: One could run the Web and mail servers, while the other could run a database. Splitting resources like this could make it possible to use two Pentium machines rather than a more expensive minicomputer.

The next level is an enormous intranet, typically a machine used continually by several thousand users working in different geographic locations. These intranets run large and busy Web servers, handling mail for several thousand people and serving database queries, as well as possibly serving audio- and video-conferencing. At this level, you'll want to start with a Sparc 20, a Silicon Graphics, or an equivalent machine.

If you find yourself on the fence between one of these levels, ask yourself some questions, such as the following:

There are some things you may want to buy today that will be cheaper tomorrow. Any machine you can't afford today may be in your price range a few months from now. If you want to get your feet wet and expand as you go, you might begin with a cheap server or use your current machine as the host. Proceeding cautiously is one thing, but be careful not to create an intranet that is so sluggish that users don't use it. Try to strike that sometimes difficult and delicate balance.

Server Operating Systems

When the time comes to shop for server software, the operating systems should be at the top of this section of the shopping list. To make it easy on you, you might be pleased to know that the operating system you choose is almost entirely a matter of personal preference. Most of the applications you will want to run on your intranet are available for many platforms. Sometimes you won't have a choice, especially if your server will sit on a preexisting machine. In this case, you must make your choices accordingly, as they must be compatible with the operating system on this machine. If you do have a choice, however, here's the rundown. (For more detailed information on operating systems, read Chapter 7 "Servers: Operating Systems.")

Windows 3.1 (Windows for Workgroups) doesn't offer too much, but it will get the job done if you only plan to run Web and mail servers. Figure 5.3 shows Windows 3.1 running httpd.

Figure 5.3: A Windows 3.1 operating system running httpd.

Stepping up to Windows 95, you'll find a wider choice of software availability and compatibility. Although Windows 95 is no Windows NT, most software that runs on Windows NT will run on Windows 95, as shown in Figure 5.4.

Figure 5.4: A Windows 95 operating system running Netscape FastTrack server.

If you're running a Macintosh house or you're more comfortable with Macintoshes, it's certainly an option to have a Macintosh server, although you probably won't find as many software options on the shelves. Macintosh operating systems offer true multitasking, and they have a RISC processor, which makes them fast servers. Figure 5.5 shows MacOS running httpd and a mail server.

Figure 5.5: MacOS running httpd and a mail server.

Windows NT gets the industry's nod of approval as a good choice of operating system. Microsoft is targeting the intranet for its Windows NT line of products. Windows NT comes with a mail and Web server and give users the freedom to run practically any intranet application needed. Figure 5.6 shows Windows NT running httpd.

Figure 5.6: The Windows NT operating system running httpd and a mail server.

Linux is a strong competitor of Windows NT. (Figure 5.7 shows an X Window Linux desktop with a Netscape browser surfing a page hosted on a server on the machine itself.) In fact, I consider the two to be the choice operating systems. One great thing about Linux is that it is free; however, on the downside, there is no support (other than the thousands of users on Internet Usenet newsgroups, who seem happy to provide ad hoc support), and it's not plug and play. Unlike Windows 95 or Windows NT, you can't just slide the CD-ROM into the machine and it's up and running; Linux makes you do lots of configuring. Linux is infinitely more flexible than Windows 95 or Windows NT, allowing its users to perform almost any function and configure the machine any way they want. Like Windows NT, Linux likely will run into problems finding the right drivers or supplemental software on a less sophisticated machine. I recommend using a big brand-name computer like IBM or Toshiba if you want to run Linux. For example, I'm currently running Linux on one of my mail-order machines, but I can't seem to find the print driver.

Figure 5.7: The Linux operating system with a term window running httpd.

The next level of operating system is UNIX, which Linux is based on. UNIX is very fast and has true multitasking, one of its main advantages. The processor can perform many functions easily at once. If two, or even dozens of users are making requests at the same time, it will keep up. As with Linux, UNIX offers some Internet pluses, such as the capability to establish shell accounts, which neither Windows 95 nor Windows 3.1 offers. UNIX makes it easy to set up user space, but it may not give you a nice graphical interface and an easy plug and play. If you use Sun machines, you'll have to use Sun's version of UNIX, which is Solaris.

MCKEON & JEFFRIES
McKeon & Jeffries expects to have fewer than 150 users, who will use the intranet mostly for e-mail and Web service. The accounting firm wants a Web server, a mail server, and a machine to support them. The average user is expected to use the intranet a little each day, though some will never use it at all and a few will use it constantly. The users do not need secure Web transmissions, but they will need decent authenti-cation.

The company needs an e-mail package to integrate its interoffice e-mail with Internet e-mail. It also needs a Web browser on each client machine. McKeon & Jeffries does not plan to use the intranet for audio- or video-conferencing, so it will not need to buy speakers, microphones, or cameras, but it will need to upgrade the machines of its support staff to use the Web browser effectively.

M&J also must set up an Internet connection and a way for users on the road to dial into the network. Users connecting from the road or home will need modems and software to set up dial-up connections.

McKeon & Jeffries Intranet Shopping List

Server:

     Pentium machine
     Operating system
     Web server
     FTP server
     Mail server (possibly a patch for Groupwise)
     Message Board software

Connectivity:

     New ISDN line for third office
     ISDN line to Internet
     Internet service provider
     LAN modem bank
     PPP software (client and server)
     P-50 router

Clients:

     Web browser
     Mail client (possibly Groupwise)
     HTML editor

Security:

     x86 machine
     Firewall Software

Server Software

After you have decided on a server, it's time to look at software that will serve your information. The only server software packages essential to an intranet are a Web server and a mail server. If you want real-time audio, you must also choose a streaming audio server or some other audio server. You may need a streaming video server as well if you plan to utilize real-time video or video-conferencing. You also may need to run a database on your server.

Web Servers

If you want a basic Web server, almost any will do. For instance, if you merely want to serve HTML pages and images, without secure transmissions or complex authentication, you can use any Web server. Regardless of the operating system you're using, you can find a free Web server. The NCSA (National Center for Supercomputing) makes a Web server that can be used by almost any operating system; it's free on the Internet at http://hoohoo.ncsa.uiuc.edu/. Of course, Netscape, Oracle, O'Reilly, Apache, Microsoft, and dozens of other companies are in the running for your server dollars. If you're using Windows NT, UNIX, or Linux, you definitely have a mail server built in and possibly a Web server as well. However, the NT mail server will need software upgrades in order to send Internet mail. Mail servers also are available for every operating system, and these also are free and quite functional. Perhaps now or down the road, you will want to add other servers, such as audio and video. (For detailed information on audio and video servers, read Chapter 8 "Server Software.") If you're considering audio and video servers, be prepared to put down some bucks. Also, if you want Web servers with special features that talk to your database or provide secure transmission, be prepared to spend some serious money. Secure Web servers can run as high as $10,000, and audio and video streaming servers can cost several thousand dollars, depending on quality.

THE SPORTING GOODS AND APPAREL ASSOCIATION
The SGAA expects to have 300 to 500 users, about half of whom will be heavy users. The SGAA expects to provide secure Web service with a heavy daily load. The intranet will need to run a database on the server, as well as real-time audio-conferencing and possibly video-conferencing. It also will need high-level authentication.

The SGAA will need to recommend a Web browser to their users, but purchasing the software will be the responsibility of each individual user or the sponsoring member company. Also, the administrative staff will need speakers, microphones, and cameras for audio and video privileges.

The SGAA will need a fast connection to the Internet, as most of its users will be accessing the site through their own Internet connections. The connectivity of this intranet must support many concurrent users accessing the site.

The SGAA's Intranet Shopping List

Server:

     Sun machine
     Operating system
     Mail server
     Web server
     Database
     Streaming audio server

Connectivity:

     T-1 line
     Internet service provider
     Modem for Sun machine
     PPP software (client and server)
     CSU/DSU

Clients:

     Mail client
     FTP client
     Telnet client
     Web browser
     HTML editor
     Streaming audio client

Security:

     Security testing software
     Firewall software

Client Hardware

As an intranet developer, your biggest task is to make sure your user group has adequate machines. Many users might connect from home, and it's likely they'll have good machines. Of course, if your users are connecting from home, they will need a modem. I wouldn't suggest anything slower than a 28.8Kbps for surfing Web sites. If the user just needs to connect with the mail server, a 14.4 should do. At this time, 28.8 is the fastest available.

However, don't worry about the home users so much; it's the users who have ancient corporate LANs you should think about. For example, it's not uncommon to find 386 DOS-based computers without color monitors on the desktops in many corporate LAN environments. Obviously, there is no longer a whole lot these poor users can accomplish with this antiquated technology. The basic minimum needed for an intranet client is a 486 with a color monitor and 8MB of RAM, and this is bare bones. If you plan to do audio- or video-conferencing or use Java, your users will need a fast 486 or a Pentium with at least 16MB of RAM. If you plan to incorporate even basic audio- and video-conferencing, you must consider sound cards, microphones, speakers, and cameras. These peripherals are not cheap. You can expect to pay for a sound card and speakers about what you'd pay for a decent home-stereo system. If you plan to use a microphone for audio-conferencing, don't waste $10 on a cheap one; spend a few more dollars and buy a decent one.

Client Software

An enormous amount of client software is available for free or for very little money on the Internet, and some of it is even fairly good. You will probably need a Web browser and assorted plug-ins, a mail client, an FTP client, a Telnet (or terminal) client, and possibly streaming audio or video clients. Many Web browsers' beta and preproduction versions are free; of course they don't have all the bells and whistles of commercially available software, but they are functional. These are adequate for getting started. There also are several free mail clients available, such as Eudora and Pine. Also, it is certainly possible to integrate your intranet or Internet mail with your existing LAN mail. Your Groupwise mail can route your Internet and intranet, but you'll have to get a patch for a nominal fee.

Connectivity

Most intranets will not be self-contained within one environment. Several locations, be they offices, homes, or mobile offices, will be hooked together, either by direct connections with one another or through the Internet. This means you must provide for connectivity between the client and the server. This is not a big challenge on a typical LAN, as everything is already connected. If your intranet is going to be self-contained within the LAN, there already is an existing ethernet, or possibly ARCnet, system linking the LAN. After you've determined where your intranet server will reside, the next step is to add modems so users from outside the LAN can dial in. In this case, you'll probably need a Shiva or other brand of network modem system. If you want to connect to the Internet or connect two offices in different geographic locations through direct connection, you'll need an outside connection, or bandwidth.

There are a few different levels of bandwidth. If you just want to use e-mail or a program like Freeloader to surf the Internet, you can get away with a 28.8 modem for your office and a dial-up account. This is probably enough to handle Internet mail and light surfing for an office of up to 10 users. If you have more than 10 users, Internet use is greater, or people are reaching your intranet through the Internet, you will want something like an ISDN line, which is 128 KB/s. You could use an ISDN to connect a few offices. If you had three small offices with a limited number of users, the offices could be connected with an ISDN line and data could be exchanged at a high rate of speed; it also could handle audio- and video-conferencing. But if these offices had hundreds of users, the line would jam immediately. In this case, I recommend a T-1 (1.5 MB/s) or T-3 (10 MB/s), which are established data lines-but this is an expensive solution. A direct connection like this either to the Internet or to another location is a permanent high-speed data connection. Unlike a modem, these lines are always running, are digital, and can transport data very quickly. However, if you're connecting two or three offices or want a big pipe to the Internet or lots of surfing, a T-1 is necessary. A T-3 is only necessary if your intranet requires audio- and video-conferencing at high rates of speeds or if thousands of users regularly access the site.

To minimize bandwidth usage, consider using Freeloader or a similar program. Freeloader software goes out on the Internet on a regular basis and downloads favorite sites so your users can surf them locally. This lets them surf frequently visited sites quickly using minimum bandwidth.

Security

You must start considering security at the earliest stages of planing your intranet. First, consider the physical security of your computers. Dead bolts, cipher locks, and card key entry systems are all things to consider. Also, special rooms, cages, and metal doors might be necessary, depending on how sensitive the data on your intranet is.

After your computers have been physically secured, you must look carefully at the electronic security. Keeping unauthorized people out, keeping your data out of the wrong hands, and protecting your transmissions are all important considerations. To keep unauthorized people out, consider a firewall. A firewall restricts and monitors network traffic so that you can choose who and what to allow in, yet still be able to spot intruders. The Eagle Raptor and Gauntlet products are both good examples of commercial firewalls. To keep your data safe from prying eyes, you need a file system that keeps careful track of permission and ownership. Windows NT, UNIX, and Novell NetWare are all examples of such systems. Windows 95 and MacOS are examples of insecure file systems. Finally, when considering the security of your data when transmitted from computer to computer, you must look at encryption. Encrypting your transmissions ensures that they are useless to an interceptor. PGP, pretty good privacy, is a freely available encryption program that you can use for your e-mail, among other things. Secure Web servers can also encrypt any data you share over the Web. See Chapters 14 through 16 for more details about securing your intranet.

Summary

This chapter should have given you enough basic information to begin penning your intranet shopping list. Remember, though, the information provided here is just a guide to send you in the right direction in search of the building blocks of your intranet. Consider the shopping list in this chapter as an outline with just the basic food groups. Chapters 6 through 13 are designed to help you select the most appropriate foods and ingredients to fatten your shopping list.