Thursday, March 13, 2008

Web Server And Web Hosting Services - An Overview

Web hosting providers provide the following basic services for web servers - anything else can be considered add-on features in theory, although in practice they are rather essential to run a successful Internet business or business website. A web hosting provider should provide the following as part of the functionality of the web server:

1. Hard Disk Space.
This is what you are actually renting, for all practical purposes. You need hard disk space on a web server to host your website. A website really consists of a lot of files, much like MSWord documents, or Excel spreadsheets. These files take up hard disk space. The web hosting provider provides you with space so that people around the world who has access to the Internet can access those files on that web server.

The price or hard disks have come down dramatically over the past year or so and it is not unknown for a hosting provider to make provision for packages from 250Megabytes up to 2000 Megabytes and even more.

How much would you need? The average web site that just makes use of static HTML pages need about 5 MB to 10 MB of space. If you use a dynamic website where some of your data is stored in a MySQL database the database will also take up space. These types of sites require more space and anything between 100MB and 250MB should be enough.

If you are going to store emails on your server you need to add these into your calculations. Emails can take up a lot of web space very quickly if people send you large files. You will need to monitor the space taken up by Emails very carefully since I've seen individual mailboxes go up to 50 or 60 MBs very quickly.

If you want to host video or audio files on your server, you will have to make provision for quite a lot more disk space. One audio file can easily take up 30 to 40MB.

2. Bandwidth
Bandwidth depends on your traffic. Every visitor to your website will consume bandwidth since this is what they will use when they open any pages on your site. Once again, if you have video and audio files on your site you will require more bandwidth. A good rule of thumb is to have an allocation of about 100KB (Kilobytes) for every visitor. This means that 500 visitors per month will consume about 50MB of bandwidth - although this is only true for an average site with mostly text and a few pictures. If you have large picture galleries, audio and/or video files you should rather work on 150KB per visitor or even more. Search engine spiders also consume bandwidth! You should monitor your bandwidth usage through your CPanel control panel or your website statistics and make sure that you communicate early enough with your hosting provider in case you need to purchase more bandwidth to prevent penalties and/or lockouts.

3. Access to your site
Under this can be counted access to a control panel, such as CPanel, Plesk or Helm, that will help you with setting up of emails, sub-domains, software installations and your MySQL database if you are running dynamic functionality such as shopping carts, forums, Content Management Systems etc.

You are also going to need FTP access to upload files to your web server. Without being able to use FTP you will not be able to maintain the content on your site (unless you make use of a Content Management System). FTP access is still required even in that case since you will definitely have occasion to have to upload files such as pictures, audio, video and other files to your server.

These are the very basic functionality that a web hosting provider should provide!

Christine Anderssen is the owner of Tailormade4You Web Design and Web Development Services and Internet Web Hosting for South Africa. Visit our site for free Joomla tutorials and tips on how to get the best performance out of your website

Labels: , , , ,

Monday, March 10, 2008

Monitor the Uptime of Your Websites and Servers

Websites are nowadays used to do business and earn profit. If you belong to those who own such a website or just planning to start on-line business, you will have to monitor the uptime of your websites or servers. Do not let your clients to let you know about your downtime.

There are companies, which websites are essential for their business success, as they are generating the most or the whole of the company's revenue. Maybe also you belong to them. When this kind of website (server) is down, your business is affected. If your website is hosted by another company, you probably have some sort of "uptime" guarantee. Nevertheless, what exactly is uptime and how do you measure it. The basic definition of uptime is the period of time when your site is up and running, being accessible and able to satisfy customers.

The opposite, when your site is not accessible, it is down. And that is how you measure downtime. Faulty routers, malfunctioning LANs, or a loss of electrical power typically causes most of the downtimes; only rarely are caused by a natural disaster. Most often, it is caused by failures from the telecommunications company or an application failure, not a fire, flood or other catastrophe.

The cost of downtime calculation of course depends on many factors, like the products and services you provide, the size of your company, the number of online sales, etc. Even if you do not sell any products or services online, there is still a cost of downtime, but then in terms of damage of reputation etc. Calculate the cost of downtime is difficult and varies from one company to another. There is no "average business", so the statistics that quantify the cost of downtime for average businesses are not helpful.

The cost of downtime include direct costs such as the labor charges for a team of technologists who had to resolve the outages. The indirect costs are much more difficult to calculate and include potential lost revenue, reductions in worker productivity, damaged reputation with customers and in the marketplace, lost future sales and the cost of storing unsold goods. Financial analysts and accountants at your company can help you come up with the factors for your particular business.

If your website is generating profit for your business, you will for sure monitor it by an external monitoring service. The on-line market offers you to choose from different services to get uptime reports, statistics and get notifications as soon as your website is down. You can not let your customers to inform you about your own downtime.

To understand the importance of being aware of downtime, and to be alerted as soon as possible when a problem occurs, have a look at these numbers:
- According to a report by Cumulus Research Partners website downtime, caused by problems such as network failures, costs European businesses more than ? 5 billion a year.
- In the automotive industry downtime is often worth some $1.000 a minute.
- According to a recent study conducted by ARC Advisory Group, accounting for nearly five percent of total North American production, more than $20 billion is lost each year due to unscheduled downtime. Clearly, the traditional "fail and fix" approach to maintenance is no longer a viable MRO strategy.

Many hosting providers guarantee 99 % uptime. 99 % uptime sounds good, but means that your site could be down more than 3.5 days a year, and in today's Internet that is unacceptable. Comparing to that, 99.9 % uptime is much better, but with 8 hours and 45 minutes of possible downtime do not have to be always enough. The table below shows the percentage of uptime and the related downtime per year.

99 % ........ 87 hours, 36 minutes (more than 3.5 days)
99.9 % ...... 8 hours, 45 minutes, 36 seconds
99.99 % ..... 52 minutes, 33.6 seconds
99.999 % .... 5 minutes, 15.36 seconds
99.9999 % ... 31.68 seconds

As you can see, a 99 % uptime may not sound too bad, but it can cost you quite a lot of loss in revenues.

There are more than 30 uptime monitoring websites worldwide, while some of those have also affiliate partners. Among those are: Alertra, AlertSite, Dotcom monitor, InternetSeer, Jaguard, RedAlert, SiteUptime, WatchMouse, WebsitePulse and others. Almost all of them offer some prepaid packages based on monthly fees, varying by number of possible monitored sites (servers), additional services and by the complexity of the service. The price of their basic prepaid package is $5 - $40 per month. For this price you can monitor only 1, or maximum of 3 devices, choose from quite a lot of protocols, allow to send notifications to multiple contacts via e-mail, IM, pager or SMS, allow to choose between daily, weekly, or monthly reports by email and of course uptime performance and statistics available on-line. The Professional packages can go up to $180 per month or even higher.

There are just two completely free 24/7 monitoring services: Montastic and mon.itor.us.

Montastic's (http://www.montastic.com) biggest advantage is simplicity of the service, while it offers just basic service including real time monitoring and alerting by e-mail one contact person - the registred user, or by RSS feed, when the website is down and when it is back again. It allows to monitor only http websites, limited to the number of 100 (what is not a limit at all), checking it every 10 minutes from two different locations.

Meanwhile mon.itor.us (http://mon.itor.us) provides network, website and server monitoring service supporting 11 protocols with possibility to monitor unlimited number of devices and alert unlimited number of contact persons by e-mail, RSS feed, IM message, pager or SMS. There are also other remarkable features as personalized interactive interface, where you can add server performance and availability tests, set daily, weekly or monthly reports sent by e-mail. Tests are performed from 3 geographically distributed servers, and they are always adding more interesting features as they are still in beta version.

Peter Cernak works at Sourcio (http://www.sourcio.com). The company develops mon.itor.us and offers a wide range of IT services and Open Source solutions for small and medium-size businesses

Labels: , , , , ,

Sunday, March 2, 2008

Embedded web server-more than just an operating system

Embedded web server isn't new term. Web server is jus a method of delivering web pages (or other contents) to the user. Market is full of such systems allowing interconnection of domestic devices and other web-enabled appliances. It is hard to understand how microcontroller can drive web server. Embedded web server usually is highly optimized machine code. Usually implemented in the C language. In order to write optimized embedded web server it is necessary to write code from scratch. What parts need to be implemented while creating embedded web server:; Microcontroller hardware; Network protocols for embedded web server; Implementation and optimisation techniques. Microcontroller hardware is a computer on a chip which has program memory for code storage, EEPROM, RAM, I/O and other peripherals. Network protocols can be used for embedded web server: HTTP-document request/response TCP-reliable communications IP-low-level data transport ICMP-diagnostics (ping) SLIP-serial interface Modem emulation HTTP request is Hyper Transfer Protocol which defines a request - response mechanism for obtaining documents from web server. Web browse sends request to web server in multiline string format like: GET /index.htm HTTP/1.0 User-Agent: Mozilla/4.5 [en] (Win95; I) Pragma: no-cache Host: 10.1.1.11 Accept: image/gif, image/x- xbitmap, image/jpeg, */* Accept-Encoding: gzip Accept-Language: en Accept-Charset: iso-8859-1,*,utf-8 In embedded systems all this information isn't needed. For instance we don't care about browser information, HTTP version isn't important because usually simplest HTTP interface is used. Simply you can trim the rest part of message and send line: GET / HTTP/1.0 because most web servers interpret this as request of index.htm.

Http://www.scienceprog.com - embedded related info. Scientific, embedded, biomedical, electronics articles. Interesting electronics and embedded projects

Labels: , , , ,

Monday, February 25, 2008

Learning ASP Series - Installing Personal Web Server

Welcome to the first chapter of your Basic ASP Learning Series.

I mostly communicate on a personal level, so it's better we acquaint ourselves in the beginning. My name is Amrit Hallan and I'm a web developer. I work through my web site - http://www.bytesworth.com. I'm not a nerd (and don't want to be) and most of my knowledge has come to me piecemeal through lots of hard work and interaction with my other developer friends. I don' t think it'd be fair to say that I'm an authority on ASP but yes, I have a few satisfied clients in my portfolio and I know enough to get you started. By the time you are through with these daily chapters, you'll have learnt enough to make a small shopping cart in ASP.

Most of the chapters will be organized in a linear fashion, so that you always have to work according to your previously acquired knowledge. Sometimes I'll sound like writing the entire chapter in a bulleted form, but that'll be just to keep the unnecessary (I mean that is out of the scope of this reference) stuff out.

I wish I could know your name too. But I don't know how many people are going to read this. If you want to let me know that YOU are the one at the moment reading this, you are welcome to send me a friendly message at mailto:amrit@bytesworth.com. I love to hear from people (ok, the word "people" excludes Spammers - they are not people).

Enough of my warming up. Here we go with the first chapter.

Installing Personal Web Server

==> Beginning of Chapter One From there, install the PWS on your computer. The installation
program creates a folder, inetpub in the directly you specify during the installation. This inetpub, further has a folder, wwwroot. So if you install your PWS on your C drive, the wwwroot path should be

C:INETPUBWWWROOT

All the files that you create, you store under wwwroot. What we generally do is, we create separate folders for separate projects under the wwwroot folder. So if I created bytesworth folder in wwwroot folder, the full path should be

C:INETPUBWWWROOTBYTESWORTH

And when I have to view the page on my browser, I'll have to type

http://localhost/bytesworth

as the URL.

After you've installed the PWS, it's icon appears on your desktop, and at the bottom right of your screen. Click or double-click on the icon. On the main window, you should see the message:

Web publishing is on. Your Home page is available at http://servername

The servername is the name you use instead of localhost. But if you are confused about this name game, just use localhost and it should always work if you haven't been naughty and messing around with your computer's basic setup.

Before you proceed further, open the Windows Explorer, go to c:inetpubwwwroot and create a new folder here by the name of "learnASP" (how boringly predictable! So you can name it something else). We'll be storing ALL our files in this folder.

Hence, whenever we want to run a newly created file, we'd type in the location bar:

http://localhost/learnASP/newfile.asp and press Enter.

Ok, next, click on the Advanced tab. Select Enable Default Document

In the Default Document(s) box, type the list of file names you would like to use as your default file once the name of your site is type in the browser.

If you have no idea what's the default file, it is the file that answers your call when you type a specific URL without a specific file. For instance, if I type http://www.bytesworth.com the file that actually gets loaded by default is DEFAULT.ASP. This depends on the setting. Some servers use INDEX.ASP or INDEX.HTML or INDEX.SHTML. It all depends on the file parsing set up on your web-hosting server.

Then click on the Edit Properties button, after selecting the Home folder. There are three select boxes, viz., "Read", "Execute", "Script". Select all of them. The selections tell the server that we want to execute server side scripts in our ASP pages. ASP pages won't run if the server can't read and execute them.

Close the window, and your PWS is running. Of course do not run two servers simultaneously. So if you installed the Apache Web Server and left it running, and then loaded PWS, there is going to be some problem for you to sort out.

Amrit Hallan is a freelance web designer. For all web site development and web promotion needs, you can get in touch with him at http://www.bytesworth.com. For more such articles, visit http://www.bytesworth.com/articles and http://www.bytesworth.com/learn.

Labels: , , , , ,

Wednesday, February 13, 2008

Have A Big Website - Worried About Server Load

Have we ever thought how big websites could be configured to handle massive amount of traffic? How thousands of businesses worldwide are facing challenges everyday to make sure there are no connection failures due to heavy load or congestion of traffic at the website.

The answer is straight, every organization will have to monitor and baseline amount of traffic by going for stress test to find out if the current hardware could be supportive enough to handle a specific amount of load. One such great software is the ?Web Application Testing? or WAPT, which is a great utility for any website?s sustainability. This software is load, stress and performance testing tool for web sites and intranet applications with web interface. WAPT is designed for MS Windows 2000/XP/2003 and Windows 98/Me operating systems. The question that should be asked is why should we consider WAPT or why should the organization consider Load or stress testing? We certainly believe, major performance issues would arise if stress test has not been performed.

This could very well mean that after the server reaches a certain level of concurrent connection made by visitors, it would consume its hardware resources to process every visitor?s request. If there is a lot to process, the server might give priority to web application than its local resource ending up in a system crash.

Thus, the goal of WAPT is very simple; it helps the organization?s web servers to become active at every stage of stress, whether it?s a web development or website traffic processing power. WAPT can perform a stress test by simulating several thousands of concurrent connections to check the web server/website performance and if it finds any bottlenecks it would warn and suggest fixing this issue by recommending the very next thing.
There are lots of new features added in WAPT 4.0
- You can use multiple virtual profiles to test a single scenario
- There is support for IP spoofing where each virtual user can run with individual and unique IP address
- Each Virtual can be configured with different username and password and is compatible with Windows Integrated Authentication or Basic Configuration.
- You can see and configure the type of reports even a test run summary report is generated
- There is command line interface available
- There is a support for persistent cookies
- All the test scenario and profiles are stored in XML format The Main features of WAPT 4.0
- You can have the application run and understand multiple languages
- There is cool recording feature which you can use to record any configuration and stress test simulations for later review or demonstrations as it supports playback of HTTPS/SSL 2.0 & 3.0 pages. You can also record the user connection speed using the keep-alive connections to a HTTP 1.0 or HTTP 1.1 pages or even HTTPS/SSL pages.
- You can generate data for run-times on specific scheduled intervals by randomizing the delay between the page hits.
- It also has a support for proxy servers for HTTP, HTTPS, SOCKS4 & 5 and supports cookies as well.
- All the authentication request can be handled using NTLM (windows Integrated Authentication) or using the basic authentication.
- If you would like to call the website by a different name, then you also have the facility to add custom host headers
- All this the scenarios can be configured using the user friendly Wizard
- You can choose the reports to be either graphical or in plain text along with full virtual server logs
A must tool for administrator or other user who would to maintain their website efficiently.

Ted Peterson writes for CoreDownload, a shareware archive where you can find utilities like WAPT to test your server.

Labels: , , , , ,

Wednesday, January 2, 2008

Benefits of Using a Dedicated Server

Shared web hosting may seem like an inexpensive hosting option, but they are very limiting. Have you ever considered using a dedicated server? The benefits to using a dedicated server are many. After reading this, you may want to switch your web hosting to a dedicated server.

The performance of a dedicated server is far superior to that of shared hosting. This is due in large part to the fact that you are not sharing your processor power, memory, or disk space with other sites using the same server. Since you dont have to worry about the server being slowed down, overrun with traffic, or crashed by another site, a dedicated server is more reliable than a shared server.

You will feel a lot more secure with a dedicated server than a shared server. No one else will have access to your server and you can be positive that you are secure. If you ever need to install some special software or need to configure your server to your needs, then a dedicated server will give you that option.

With a dedicated server, you can run your own custom firewall. This will enable you to enforce your own control policy that will only allow people you want to be able to access it. Something else you get with a dedicated server that you dont get with a shared server is your own IP address. You wont have to share it with anyone else.

If the need arises, you can always add more memory, disk space, or extra processors. With shared servers, you cant do this. Dedicated servers also allow you to have a Service Level Agreement. With all of these benefits, how can you not want a dedicated server?

It may seem too expensive to host your websites on a dedicated server, but when you compare it to shared hosting, the end result is worth it. With your own dedicated server, you can be assured of having a more reliable and stable server. You wont have to worry so much about overload, bad codes and scripts from other users, and too many applications being uploaded.

You will only install the software and applications that you need and want to use on a dedicated server. This lessens your dependency on web hosts and bypasses the time delays and expenses accrued from them. You can supply instant support to your clients whenever they need it. This is a vital part of any successful business. If you provide reliable service to your clients, then they are going to be loyal and give you good word of mouth promotion. This will help your business continue to grow, and that is the ultimate goal.

You will have 24 hour access to your dedicated server, and this will allow you to adjust, correct, or update anything you need to in mere minutes. You wont have to worry about visitors leaving your site because it wouldnt load fast enough or wasnt available. If your website is able to download quickly and is always available, then the visitor will be encouraged to use your services and come back if they need you again. This will be good for your overall image and will make the customers want to refer you to all of their friends.

HotDealShare.com - Find the best deals, freebies, free coupons, sweepstakes, promotional offers, bargains, discount prices, hot deals and hundreds of merchants. Updated daily!

Labels: , , ,