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