Skip to main content

Development of Intranet

An intranet is a private website or network of a company, or organization used to maintain internal information, manage projects, provide employee information, and distribute common forms and files. 

They are especially important for large organizations with employees in multiple locations who need access to the same data. Organisations commonly have pages on an intranet site for sections, departments, and even individuals. But, intranet websites needs to be updated. 

Requirements for Intranet Development 

Following things are required for intranet development: 

1) Network: An intranet does not require its own cabling; it can operate on the existing network.
 
2) Server Computer that is dedicated to the Intranet: Make sure that this computer has plenty of RAM (at least 2GB) and gigabytes of disk space (at least 100GB). The more users your network has and the more information you intend to place on the server, the more RAM and disk storage you need.
 
3) Windows Server 2003 or a Linux Operating System: Web server software requires one or the other.

4) Web Server Software for the Server Computer: One needs to install a web server, such as IIS (for windows servers) or Apache (Linux or Windows servers).
 
5) Programs to Help you Create Web Pages: If you are the type who dreams in binary, you can create web pages by typing HTML codes directly into text files. In that case, the only program you need in Notepad. Alternatively, you can use a program designed specifically for creating web pages, such as Microsoft FrontPage, or perhaps something fancier, such as Adobe Dreamweaver. If you are going to develop transaction-based applications, you need additional tools.
 
Considerations in Intranet Deployment 

The intranet server platform has to meet ten evaluation criteria:
 
1) Scalability: The efficient transaction read/write capability should be ensured as the number of users and access increases.
 
2) Interoperability: Enterprise web, data warehouse, message and mail manager, online transaction processing and other nodes will form the enterprise server platform cloud, which will require each node to have a high interoperability presence on the network.

3) Configurability: Vendors just provide a broadly configurable array of enterprise servers that do not require major box swaps as enterprise requirements change. Parts must be modular and offer commodity component substitution with other devices from third parties.
 
4) Compatibility: The server family must not only meet expandable configuration requirements, but also standard industry specifications to protect application investment.
 
5) Manageability: As the trend increases, enterprise systems must be operational from any point on the network and address the major operational management problems concerning configuration, fault and problem diagnosis and installation.
 
6) Availability: As enterprise servers assume a larger role in the electronic channel and the enterprise wide web, these systems must be able to sustain tens to hundreds of thousands of accesses and transactions with minimal downtime.
 
7) Reliability: The hardware reliability, data integrity, systems integration, and operational error immunity are essential.

8) Distributeability: Whether in two- or three-tier client/server architectures, the enterprise server must embrace the client, assume a high degree of desktop affinity and must enable resources to be proportioned between server and client appropriately.
 
9) Serviceability: The increased value placed on uptime will mandate online serviceability through the use of hot-swappable components, remote diagnostics directly connected to vendor service centers and pre-failure predictive diagnostics.

10) Stability: The generation changes in technology, and architecture that may include changes to instruction sets, migration from 32-bit to 64-bit computing and operating system enhancements for clustering and advanced symmetric multi-processing must minimise upgrade disruption and preserve investment protection.
 
Steps for Creating an Intranet 

Following are general steps to create an intranet. Your exact steps depend on whether you are converting an existing LAN to an intranet or creating a new network, on the size of your intranet, and on whether you plan to connect your intranet to the internet: 

Step 1) Decide on the key applications for your intranet and look at software to perform the application. If you are looking for e-mail, web pages, and other general internet services, almost any intranet system will do, but if you need specialized services, your choice of software may dictate the hardware and network operating system for at least.one of the servers on your intranet.

Step 2) Decide whether and how the intranet will connect to the internet. Choose an ISP, choose the speed of your internet connection (dial-up), ISDN, cable modem service, or dedicated line), and determine what hardware you need. 

Step 3) Configure the servers for your intranet. Choose the server programs (such as web servers and e-mail servers), NOS, and hardware (CPU, RAM, disk drives, modem, and printer). Be sure to include some form of backup media, such as a tape drive. 

Step 4) Choose the client software, operating system, and hardware for the workstations on the intranet. Client software usually includes an e-mail program and a browser, as well as other standard internet programs. 

Step 5) Determine the cabling topology, if you are.creating a-new-network. Draw a layout of the network, by working off building blueprints. 

Step 6) Configure the internet connection and firewall, including the router, proxy server software, and other components. 

Step 7) If you are adapting a LAN as an intranet, you should already have a security system that is based on the capabilities of your NOSS. If you are creating a new network, you need to learn about your NOS's security system, assign users to groups, make an access profile for each group, and make an access profile for each user.

Step 8) For each new or upgraded server and workstation, install the new hardware (including network adapters) and operating system, and test that the system runs correctly. 

Step 9) If you are creating a new network, configure the servers to communicate over the network. Configure the workstations to communicate over the network. Install and test file and printer sharing services. 

Step 10) Install and test the mail server, the SMTP gateway for the existing e- mail.

Step 11) Configure and test the firewalls. Make backups of all the servers and workstations, so that you have a copy of a "clean install" of all the software necessary for the intranet. Institute procedures for regular backups. 

Step 12) Teach users for using the new facilities on intranet.

Previous Next


Labels:

Comments

Post a Comment

Popular Post

Advantages of EDI

1) Shortened Ordering Time : Paper orders have to be printed, enveloped and sent out by the customer's post room, passed through the postal service, received by the supplier's post room and input to the supplier's order pocessing system. To achieve all this, reliably, in under three days would be to do very well. EDI orders are sent straight into the network and the only delay is how often the supplier retrieves messages from the system. Orders can be in the supplier's system within a day, or if there is urgency, the messages can be retrieved more frequently, for example every hour.  2) Cost Cutting : The use of EDI can cut costs. These include the costs of stationery and postage but these will probably be fully matched by the costs of running the EDI service. The principle saving from the use of the EDI is the potential to save staff costs. For example, if the orders are directly input to the system there is no need for an order entry clerk.  3) Elimination of Errors :...
Post a Comment
Read more

Infrastructure for EC

Introduction The e-commerce infrastructure is defined here as the supporting capabilities for online trading between multiple companies which include hardware, software, networks, online payment technologies, security and encryption technologies, online trading business models, legal and regulatory framework, and managerial and organisation capabilities.  Infrastructure is the shared human, informational , and technical resources on which the work system relies in order to operate, even though these resources exist and are managed outside of the work system.  To evaluate the interdisciplinary aspects of construction e-commerce infrastructure, one proposes using a four pillar approach. Figure 5.1 illustrates the skeleton for the proposed integrated construction e-commerce infrastructure. The proposed integrated e-business infrastructure can be broken down into the following four groups of components:  1) Technological Infrastructure : Technology infrastructure is a work...
1 comment
Read more

Business Strategy - E-Commerce Strategy Inputs

E-Commerce Strategy Inputs Traditionally an IT strategy would be subservient to the business strategy. For e- commerce the IT strategy becomes a central component (or the determinant factor) in business strategy.  Inputs to an e-commerce business strategy are: Technology An E-commerce technology includes:  EDI : Streamline supply logistics and facilitate decreases in trade cycle times.  Electronic Markets : Re-define the operation of a market sector.  Internet E-Commerce : Provides new direct sales opportunities and novel business to business and business to consumer applications.  Internet e-commerce can be used to improve, transform and re-define business value:  Organisation  Source of Business value  i) Improve it a) Product promotion b)New direct sales channel c)Direct saving d)Time to market e)Customer service f)Brand image  ii)Transform it a)Technological and organizational learning b)Customer relations  iii)Re-define it a)New pro...
Post a Comment
Read more