| In recent times I have gone through an | | | | required. Once the request is approved, the |
| article on intranet where it has been | | | | intranet developers would work with Human |
| reflected in the sense that an artistic | | | | Resources to create the application. The |
| method feasible to intranet can be put side | | | | problem with centralized control and formal |
| by side to a composition process where we can | | | | approval processes is that they put |
| endeavor to construct the roof of the house | | | | creativity and timeliness in thumbscrews. |
| before we place the underpinning, and we may | | | | Following a decentralized model, each |
| facade somber problems. Let us dispense the | | | | department within the organization is |
| concrete for the foundation of the house | | | | responsible for its section of the intranet. |
| before we put in the necessary plumbing for | | | | All departments that want to create intranet |
| water and sewer access, and have to spend | | | | services will have to set up, design and |
| more money than we bulldoze for. We can build | | | | administer their own intranet servers. Each |
| a house one footstep at a time and as such we | | | | department will also be responsible for |
| can make certain the house which has a strong | | | | creating the publications and applications |
| foundation. Buildings with strong | | | | used by the department. |
| nitty-gritty tending to a certain period. | | | | |
| When we have more or less done with the frame | | | | When we can draw on a decentralized model, we |
| of the house, we build a roof. Although the | | | | hack out the prescribed endorsement procedure |
| roof of the house is the top of the | | | | for new publications, applications, and |
| structure, we do not stop there. It takes | | | | services. This means anyone can create |
| more than a covered frame to make a house. We | | | | intranet resources. Greater freedom and few |
| hire an electrician to do the wiring and | | | | controls means that new services can be set |
| bring back the plumber to finish the | | | | up quickly by anyone who wants to set them |
| plumbing. Afterward, we hang plaster board, | | | | up. This freedom and lack of controls can |
| add insulation, finish the exterior, add | | | | also lead to abuse of the intranet resources. |
| fixtures, and before we know it, we have a | | | | When someone publishes potentially offensive |
| house that we can call home. We build an | | | | material or when the usefulness of the |
| intranet in the same way, one step at a time. | | | | intranet deteriorates because so much junk |
| We can initiate on the intranet is about as | | | | has been created? By adopting elements of |
| glamorous as the water and sewer pipes | | | | both the centralized and decentralized model |
| waiting for the foundation to be poured | | | | that fit the needs of the organization, we |
| around them; for just when we are ready to | | | | might be able to balance the need for strict |
| roll back our sleeves and dive into the | | | | control with our artistic self-determination. |
| intranet creation process with both feet, we | | | | For paradigm, we could create an intranet |
| might discover we need to conduct research, | | | | with a centralized Web server that links |
| planning, or consider the requirements of the | | | | together departmental servers. The IS staff |
| intranet. When we finally flesh out the | | | | would be responsible for maintaining the |
| foundation of the intranet, we start to build | | | | central server and updating links to |
| the framework. The basic components of any | | | | resources throughout the organization. The |
| intranet are the hardware and software that | | | | individual departments would be responsible |
| make it work. The hardware used in the | | | | for maintaining their own servers. To ensure |
| intranet is focused to determine the way the | | | | the intranet is not abused, one person within |
| intranet is operated. | | | | each department could be responsible for that |
| | | | department's intranet resources. |
| The software our intranet uses will determine | | | | |
| what the intranet is used for. Eventually, we | | | | The real stars on our intranet are the |
| finish designing the intranet, but find we | | | | applications we plan to develop. Still, we |
| still have to develop the hot Java-powered | | | | will need content for our intranet. Most of |
| applications for the intranet. Even when we | | | | our content will be in the form of hypertext |
| have completed the design and development | | | | documents that are served by our Web server |
| processes, the intranet still is not over and | | | | and displayed by our chosen Web browser. As |
| done with in order to check the structure of | | | | we consider the type of content we want to |
| the work for flaws. We make sure we have used | | | | publish on our intranet, think about how we |
| the right structure and created the best | | | | will organize that content. We can organize |
| tools. Once all this is done, we finally have | | | | hypertext documents in many ways. The |
| an intranet worthy of the CEO's wholehearted | | | | structure that is best for a particular |
| embrace. Try to build the whole house at once | | | | document depends on the complexity of the |
| and we will be overwhelmed. The same is true | | | | material we plan to present. For a small |
| for any creative process. When we are | | | | document with limited complexity, a simple |
| building our intranet and its applications, | | | | structure is often best. Simple structures |
| we need to manage many things on a level of | | | | include linear and linear with alternative |
| general organization and on a more specific | | | | paths. The simplest way to structure a |
| level. If we mismanage expectations, our | | | | hypertext document is in a linear fashion. |
| intranet might not turn out as we plan. Our | | | | Using a pure linear structure, we can create |
| potential anticipation and the opportunity of | | | | a hypertext publication with a structure |
| our superiors might be totally different. | | | | resembling a traditional print publication. |
| Before we start to design the intranet and | | | | Readers move forward and backward in sequence |
| the Java-powered applications for the | | | | through the pages of the publication. An |
| intranet, make sure our prospect and the | | | | alternative path structure gives readers more |
| expectations of our administrator network. A | | | | options or paths through a document. By |
| good way to do this is to ensure that the | | | | providing alternative paths, we make the |
| infrastructure channels are open and used. | | | | structure of the publication more flexible. |
| | | | Instead of being able to move only forward |
| To make certain that our scheme is a | | | | and backward through the publication, readers |
| devastating success; we should argue outlook | | | | can follow a branch from the main path. In a |
| throughout the progress of the intranet, | | | | linear structure the branches will rejoin the |
| principally as we develop our intranet | | | | main path at some point. The hierarchical |
| applications. If we develop a rapid prototype | | | | structure is the most logical structure for a |
| of key applications, our superiors should be | | | | publication of moderate complexity. In this |
| the ones to verify that the designs meet | | | | structure, we organize the publication into a |
| their expectations. If the model does not | | | | directory tree. Readers can navigate through |
| meet their outlook, maybe the prototypes were | | | | the publication, moving from one level of the |
| an example of what not to do, or maybe the | | | | publication to the next, more detailed, level |
| expectations of management are unrealistic. | | | | of the publication. They can also go up the |
| If our prototypes meet or exceed the | | | | tree from the detailed level to a higher |
| expectations of our superiors, we have a | | | | level and possibly jump to the top level. |
| green light and our project is well on its | | | | |
| way to a successful implementation. We should | | | | The information bank tree intimately look a |
| also manage our personal expectations for the | | | | lot like the way we store files on our hard |
| intranet and its applications. Our | | | | drive in a main directory with subdirectories |
| expectations play a major role in the success | | | | leading to files. We could also think of the |
| of the intranet. Realistic expectations | | | | hierarchy as a representation of an actual |
| ensure the success of our intranet. If we | | | | tree. If we invert the tree, the trunk of the |
| perceive the intranet as an impossibly large | | | | tree would be the top level of the |
| undertaking, we might cripple by virtue of | | | | publication. The trunk could be the overview |
| wide range of knowledge in this regard. If we | | | | of the publication. The large boughs leading |
| perceive the intranet as a trivial | | | | from the trunk would be the next level of the |
| undertaking, we will not produce the best | | | | document structure. The boughs could be |
| possible structure and tools for our | | | | chapter overview pages. Branches leading from |
| organization. It is best to find a balance in | | | | the boughs would be the next level, or the |
| our perceptions about the intranet. As we | | | | pages within chapters. A combined linear and |
| begin to design the intranet, keep in mind | | | | hierarchical structure is one of the most |
| that the intranet creation process is a team | | | | used forms for hypertext publications. This |
| effort. Few individuals will be able to | | | | is because it is an extremely flexible, but |
| handle all aspects of creating the intranet | | | | still highly structured method. Readers can |
| and its applications. For this reason, we | | | | move forward and backward through individual |
| should have an accurate perception of our | | | | pages. They can navigate through the various |
| abilities and know when it is in the best | | | | levels of the publication by moving up a |
| interest of the project to delegate tasks. | | | | level or descending to the next level. They |
| | | | can also follow parallel paths through the |
| Generating an intranet is exhilarating and | | | | document. The most complex structuring method |
| demanding and as such we have to break a new | | | | is the integrated web. This method lets the |
| ground, making efforts for new things, and | | | | reader follow multiple paths from many |
| carry out research work with a new-fangled | | | | options. This is a good method to use when we |
| request. Managing the intranet is the | | | | want the reader to be able to browse or |
| creation of an amazing process in whatever | | | | wander many times through the publication we |
| way some one will motivate us. If one way of | | | | have created. Each time through the |
| thinking about the intranet is not motivating | | | | publication, readers will probably discover |
| we, change tactics. Do whatever it takes to | | | | something new. After considering the various |
| get the job done. We do not limit a few | | | | styles for hypertext documents, we should |
| strategies or stick with one strategy when it | | | | examine the various tools we will need to |
| obviously is not working. Make a list of | | | | develop the intranet. A tool is anything that |
| strategies. If one strategy is not working, | | | | supports the task we are working on. The |
| switch to a new one. If we do not have a new | | | | tools for unleashing the power of our |
| one, create a new one. The strategy we use | | | | intranet are based on the existing tools for |
| can be very basic. A great strategy to start | | | | the Internet itself, which includes |
| with is to plan to work on the project every | | | | protocols, resource tools, and information |
| day until it is completed. In addition to | | | | services. TCP/IP (Transmission Control |
| this strategy, we should add planning to | | | | Protocol Internet Protocol) is the foundation |
| involve both management and users in the | | | | of the worldwide Internet. We must install |
| development process. The degree of | | | | TCP/IP on our network to enable intranet |
| participation for management and users might | | | | services. A protocol is a set of rules for |
| need to be adjusted throughout the | | | | programs communicating on the network. It |
| development process. Our role in the project | | | | specifies how the programs talk to each other |
| should be a part of our strategy. Initially, | | | | and what meaning to give to the data they |
| we might want to work closely with the | | | | receive. Without TCP/IP setting the rules for |
| development team. Later, we might discover | | | | our network communications, we cannot use |
| that our best role is to manage the | | | | Internet technologies. The good news is that |
| development at a higher level. Or if we are | | | | if our organization already has access to the |
| the top programmer or network administrator, | | | | World Wide Web; we might already have the |
| we might find that we need to work on | | | | necessary TCP/IP structure in place. |
| application design rather than the actual | | | | Additionally, TCP/IP is built in to some |
| programming. Adapting our role as necessary | | | | operating systems, including Windows 95, |
| can help the project flourishing. | | | | Windows NT, and most variants of UNIX. If we |
| | | | have an operating system where TCP/IP is not |
| When we start working on the intranet design | | | | built in and do not have TCP/IP installed, we |
| and creation process, one of the first things | | | | will need to purchase TCP/IP software. |
| we should do is develop goals. Our goals | | | | Fortunately, TCP/IP software is widely |
| should take into consideration the | | | | available from software vendors. |
| complexities and nuances of the intranet we | | | | |
| plan to develop for our organization. Goals | | | | An intranet without Web services is like a |
| should be clear and relevant to the problem | | | | world without water. The key to the World |
| at hand. Set major goals relevant to the | | | | Wide Web is the hypertext transfer protocol. |
| purpose, scope, and audience of the intranet. | | | | HTTP offers a means of moving from document |
| Also, set minor goals or milestones for the | | | | to document, or of indexing within documents. |
| stages of the intranet development and its | | | | Accessing documents published on our intranet |
| applications. Goals and milestones help | | | | involves communications between browsers and |
| define the intranet development process as a | | | | servers. In a browser, such as the Netscape |
| series of steps or achievements. One major | | | | Navigator, the HTTP processes are virtually |
| goal could be to complete the planning of the | | | | transparent to the user. All the user really |
| intranet; another major goal could be to | | | | has to do is activate links to move through |
| complete the design of the intranet. The | | | | our Web presentation. The browser takes care |
| series of steps necessary to complete the | | | | of interpreting the hypertext transfer |
| major goals are the minor goals or | | | | commands and communicating requests. The |
| milestones. Our first milestone will be to | | | | mechanism on the receiving end, which is |
| start work on the intranet. Another milestone | | | | processing the requests, is a program called |
| might be to select and purchase the necessary | | | | the Hypertext Transfer Protocol Daemon |
| intranet software, such as Web server | | | | (HTTP). A daemon is a UNIX term for a program |
| software, browser software, and a Java | | | | that runs in the background and handles |
| Development environment. Our goals are to | | | | requests. The HTTP daemon resides on our Web |
| complete the major steps of the development | | | | server. Before setting up or installing |
| process, such as planning and design. In | | | | server software, we must determine what |
| designing a constructive intranet system, the | | | | platform the Web server will run on. Until |
| intranet designer may create or provide rules | | | | recently, our choices were limited, but this |
| that pertain specifically to the intranet's | | | | changed rapidly as the World Wide Web grew in |
| law or scope of control, such as the | | | | popularity. Today, Web server software and |
| Information Systems department that will have | | | | server management tools are available for |
| overall responsibility for the intranet after | | | | almost every platform. And, like other |
| completion. As we start to create the | | | | software developed for use on the Internet, |
| intranet, these rules might seem perfectly | | | | this software is available as freeware, |
| acceptable. However, as we conduct planning | | | | shareware, and commercial software. We will |
| for the intranet and its applications, we | | | | find that UNIX platforms have the most |
| might find that the overall responsibility of | | | | options for server software. Until recently, |
| the intranet should be divided amongst the | | | | there was only one good choice for the |
| departments that will set up intranet | | | | Windows NT environment, but this has changed. |
| servers. If these early rules cannot be | | | | There are now many excellent commercial and |
| modified to fit the current situation, we | | | | freeware choices for Windows NT. For other |
| will have problems. We might encounter delays | | | | platforms, there is generally only one choice |
| due to loss of efficiency or the final | | | | in server software. Having only one choice of |
| product might not be what was expected. | | | | server software for the Windows system which |
| | | | doesn't mean the quality of the server |
| No rule should ever be considered absolutely | | | | software is poor. Quite the contrary, the |
| and even the best of rules should be | | | | quality of the software is often quite good. |
| interpreted as guidelines that can vary | | | | Tools are an essential part of any operation. |
| depending on the situation. Rules for a | | | | Resource tools provide the means for sending |
| complex project like our intranet should be | | | | and retrieving information. There are three |
| flexible and make sense. A rule that | | | | basic tools of intranet working: |
| conflicts with something we are trying to do | | | | |
| should be reexamined. The rule might be | | | | Electronic mail is a great way to |
| inappropriate for the situation we are trying | | | | communicate. Think of e-mail as a way to send |
| to apply it and as such our intranet will | | | | letters to anyone within the company |
| never be put into action if we avoid working | | | | instantly. Many e-mail programs enable |
| on it. Putting off work until something is | | | | delivery of mail to single users or groups of |
| due is a poor practice. Relinquish when | | | | users. Some e-mail programs even provide ways |
| things do not go our way or when we seem to | | | | to automate responses. Most browser packages |
| have a block is another poor practice. Even | | | | are packaged with e-mail software. File |
| if we flourish on cut-off date, sketch to | | | | transfer protocol provides the basic means |
| work toward intranet's goals and milestones | | | | for delivering and retrieving files around |
| regularly-every day if necessary and | | | | the network. The files can be text, sound, or |
| possible. We should also plan to work on the | | | | graphics. FTP provides a springboard for many |
| intranet and its applications during those | | | | information-based approaches to retrieving |
| times when our thoughts are not flowing. | | | | information. Many higher level tools that |
| Everyone has bad days and good days. Some | | | | have friendlier interfaces use FTP or a |
| days we take more breaks. Some days we work | | | | protocol similar to FTP to transfer files. |
| straight through the day and into the night. | | | | Just about every browser currently available |
| We might tend toward other destructive | | | | supports FTP. Telnet lets our intensive log |
| behavior besides avoiding or putting off | | | | into another system and browse files and |
| work. Sometimes programmers go to the | | | | directories on that remote system. Telnet is |
| opposite extreme. They tear things apart | | | | valuable because it is easy to use and basic |
| impulsively before letting the work cool off | | | | to the network. When we telnet to another |
| so they can look at it objectively. Never | | | | computer, we can issue commands as if we were |
| hack our code just because a few users didn't | | | | typing on the other computer's keyboard. On |
| like our application's interface. Managing | | | | some platforms, like UNIX, telnet is a |
| the aspects of the intranet's design and | | | | built-in resource. On other platforms, we |
| creation is only the beginning. The next step | | | | will need a telnet tool. The basic resource |
| is to determine the best organization for our | | | | tools are indispensable when used for the |
| intranet. Over the years, three models have | | | | purpose that they were designed for. They |
| developed for information systems like our | | | | even provide the fundamental basis for many |
| intranet: centralized, decentralized, and a | | | | high-level resource tools, but they simply |
| combination of centralized and decentralized. | | | | weren't designed for the advanced |
| The three computing models are really driven | | | | manipulation of the wealth of information |
| by the types of computers in use at an | | | | available on the Internet. This is why dozens |
| organization. | | | | of information resource tools have been |
| | | | designed to manipulate networked data. |
| Following the centralized model, all computer | | | | |
| resources are centered in one location and | | | | At this juncture, there will be a list of |
| under the management of one organization. | | | | high-level resource tools we might want to |
| When we think of centralized computing, think | | | | use on our intranet: A system to |
| of mainframes and computer centers. With the | | | | automatically gather, index, and serve |
| introduction of file server and client server | | | | information on the Internet. Archie is a |
| computing, most organizations moved away from | | | | great tool for searching our intranet's file |
| the centralized model toward a decentralized | | | | archives. Once we set up Archie services, |
| model. In decentralized computing, computer | | | | users can access Archie resources with their |
| resources are spread throughout the | | | | browser. A distributed information service |
| organization and under the management of the | | | | that enables us to move easily through |
| departments in which the computers are | | | | complex webs of network resources. Gopher |
| located. When we think of decentralized | | | | uses a simple protocol that enables a Gopher |
| computing, think of the high-power | | | | client to access information on any |
| workstations and servers. After the big move | | | | accessible Gopher server. Most browsers |
| to decentralize computer resources and | | | | directly support Gopher. An automated mailing |
| dismantle massive computer centers, many | | | | list distribution system. Users can subscribe |
| managers had a rude awakening to the anarchy | | | | to LISTSERV lists we set up on the intranet, |
| decentralized computing can cause. Let us | | | | which enables them to read e-mail posted to |
| imagine an organization where each department | | | | the list or to post e-mail to the list. Once |
| sets the rules and decides the standards, | | | | we set up a LISTSERV server, users can join |
| like what hardware and software to purchase | | | | lists and participate in lists using standard |
| and how that hardware and software should be | | | | Internet e-mail software. Most browser |
| set up. Then imagine the nightmare of trying | | | | packages include e-mail software. A bulletin |
| to support the gauntlet of software and | | | | board system of discussion groups called |
| hardware installed throughout an organization | | | | newsgroups. Users can participate in |
| the size of AT&T. Because of a lack of | | | | newsgroups posting messages to the group and |
| control with decentralized computing, many | | | | can read messages posted by other newsgroup |
| organizations are moving to the happy middle | | | | members. Once we set up a newsgroup server, |
| ground of a mixed computing model. In this | | | | users can browse newsgroups and post |
| mixed model, a centralized Information | | | | information to newsgroups using a newsgroup |
| Systems management sets broad policy, such as | | | | reader. Most browser packages include a |
| the direction and purpose of key computing | | | | newsgroup reader. A distributed information |
| initiatives, and the individual departments | | | | service for searching databases located |
| are free to work within those guidelines. | | | | throughout the network. It offers indexed |
| | | | searching for fast retrieval and an excellent |
| As we thrash out the accomplishment of the | | | | feedback mechanism that enables the results |
| intranet with management, we should consider | | | | of initial searches to influence later |
| keeping the three working out models in mind. | | | | searches. WAIS servers are best accessed via |
| While our organization might currently use a | | | | CGI scripts, which allow users to search |
| specific model, we can apply any of the | | | | databases using their browser. Using HTML |
| models to the design of our intranet and | | | | development tools, we can quickly and easily |
| should egg on administration to prefer the | | | | create HTML documents for our intranet. HTML |
| mock-up that wills finest hand round our | | | | editors have features similar to our favorite |
| institute. In an ideal world, the concluding | | | | word processor and enable us to easily create |
| pronouncement will be based on the necessary | | | | documents in HTML format. Typically, these |
| responsibility and control of the intranet | | | | editors enable us to select HTML elements |
| resources. Subsequent a centralized model, a | | | | from a pull-down menu. The menu has brief |
| specific department within the organization | | | | descriptions of elements we can add to the |
| will be responsible for the intranet. This | | | | document. The editor places the element in |
| identical division will be accountable for | | | | the document in the proper format, which |
| the setup, design, and administration of our | | | | frees us from having to memorize the format. |
| intranet servers. The department will also be | | | | When creating complex forms, we 'all find |
| responsible for creating the necessary | | | | HTML editors especially useful. HTML |
| publications and applications based on user | | | | templates enable us to add the functionality |
| requests. With a centralized model, there | | | | of an HTML editor to our favorite word |
| will usually be a formal approval process for | | | | processor. The great thing about templates is |
| new publications, applications and services. | | | | that we can use all the word processor's |
| This means that if the Human Resources | | | | features, which could include checking |
| department wanted an application to track | | | | grammar and spelling. |
| employee files, a formal request would be | | | | |