Web Server Monitoring Goes to Australia

January 31, 2006, Plymouth, Minnesota -- Dotcom-Monitor has just added Sydney as its newest web server monitoring location, bringing executive class monitoring to Australia.

"Companies need to know how their web sites respond to customer usage," says Vadim Mazo, CEO of Dotcom-Monitor. "Adding the Sydney monitoring station means they will now be alerted if their web site is inaccessible or slow to Australian customers."

The Sydney's monitoring station is a robot that visits a company's web site, simulating a human visitor, and performs various functions, including surfing, form-testing, shopping cart usage, etc. Performance speed, accessibility and response times simulate a human user's experience.

Companies depend on remote web server performance monitoring to respond quickly to emergencies (such as an order form no working), as well as to plan for long term upgrades to ensure maximum satisfaction for customers. It is estimated that $20 to $40 billion is lost each year from users who abandon slow loading web sites.

Global web site monitoring secures customers world-wide

Global marketers understand that web sites respond differently in different parts of the world due to trans-Atlantic connections, bottlenecks, the quality of local connections, etc. "Just because a web site performs well in New Jersey, does not mean a customer in Sydney or London benefits from the same performance," Mr. Mazo says. "Monitoring your web servers from Sydney will tell you if you need to make changes to better serve your Australian market."

While only 13% of U.S. home users still use sub-56K Internet connections, that number is much higher in less developed countries, meaning web sites optimized for U.S. customers might not perform well overseas.

Sydney is the tenths monitoring station in Dotcom-Monitor's global network. The other five sites are:

- London, UK - Minnesota, USA - New York, USA - California, USA - Florida, USA - Calgary, Canada - Colorado, USA - Frankfurt, Germany - Honk Kong, China

Dotcom Monitor is an executive class website monitoring company, offering top performance services above and beyond the norm in the industry. Since 1998, its goal remains to protect the reputation and profitability of online business by bringing together monitoring, reporting, notification, escalation and analysis in the combination best suited to a company's needs.

About Dotcom Monitor: Dotcom Monitor is an executive class website and network monitoring company, offering top performance services above and beyond the norm in the industry, including website load stress testing introduced in 2004 (offered by very few monitoring companies). Since 1998, Dotcom Monitor has been protecting the reputation and profitability of businesses online by bringing together monitoring, reporting, notification, escalation and analysis in the combination best suited to a company's needs. Visit the website at www.dotcom-monitor.com or get more details about website monitoring services at www.dotcom-monitor.com/web-site-monitoring.asp. Get information on network monitoring at www.dotcom-monitor.com/network-monitoring.asp.

Johan Jacobsson is a marketing and SEO consultant at Dotcom-Monitor.com, a web-server monitoring company.

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.

Website Updates are a SNAP With Server Side Includes

If you ever had to make a change to your website that needed to be carried onto every page, you know what a tedious job it is.Well, have I got news for you. It doesn't have to be. Welcome to the world of Server Side Includes, also known as SSI. The best part about SSI is that it will make your life as a site owner 'oh so sweet.' You're going to want to kiss me after I give you the lowdown on this little beauty.

Let me give you an example. Let's say you have a site with over 50 pages and you need to add another link to your navigation bar. Can you imagine how long it would take you to open each page and update it? By putting your navigation bar into an SSI file, you would only open up that one file and update that -- and the change to your navigation bar will show up site wide. See how simple that was? By editing one file you have updated your entire site instantly.

The most common use of an include file is for your top navigation, your bottom text navigation, copyright, logo or any other piece of info needed to appear on all pages of your site.

So how do you create an SSI file? Glad you asked! An include file can be an HTML file or a simple text file. It should be whatever HTML coding you need for that element of your site, minus the or tags which should remain on your individual pages.

An easy way to make them is to design your web page and cut and paste the code you want into individual files and name them things like topnavigation.htm or bottomnav.htm. By giving them descriptive names, you'll know at a glance which file is which when it comes time to perform those updates.

After creating the files you plan on using as your includes, you'll need to open your web pages and insert a line of code where you want the SSI information to show up in your documents.

The code looks like this:

If your includes are located at the root level on your web server your path would look like this:

That's it. Pretty simple, really. After you get the hang of it you'll wish you would have learned about them years ago. They really do make global updating a snap.

Here are a couple of good sites to learn more about SSI:

Big Nose Bird-
http://www.bignosebird.com/ssi.shtml

CGI Resource-
http://cgi.resourceindex.com/Documentation/Server_Side_Includes/

New Breed Software
http://www.sonic.net/~nbs/unix/www/ssi/

Web Reference
http://www.webreference.com/programming/ssi/intro/

Before you start implementing SSI you need to ask your web host if they support them (most do), and also if they will need to be named with any special extensions. Some servers may require you to give them specific extensions like .asp (if it's NT) or .shtml (for many Unix servers). Although the majority won't, it's always better to ask first. Better safe then sorry.

By designing your website with server side includes you'll save yourself a ton of headaches when it comes time to updating your site. SSI is a Webmaster's best friend, so I suggest you spend some time getting acquainted.

Merle http://www.EzineAdAuction.com "Where some of the BEST Deals in Ezine Advertising are Made" Buy & Sell Ezine Ads in a live auction setting! Publishers sell off your excess inventory and Buyers pick up some Fantastic bargains. Go now.

A Change in Paradigm: Dedicated Server

I found it hard to believe, but suddenly I was faced with a real problem. Well, I suppose most people would not consider it a huge problem, quite the opposite, in fact. However, it was stressing me out complete, interfering with my writing. I even had trouble sleeping.

What was this horrendous problem? My web site was becoming very popular. So popular, in fact, that I was getting very worried about bandwidth charges.

You see, this was happening after September 11th, 2001, and I had been reading about some people who had created very special and beautiful sites. These sites were so incredible that they attracted lots and lots of visitors. So many visitors that they received hundreds of gigabytes worth of traffic. The webmasters suddenly found themselves charged hundreds or even thousands of dollars for using bandwidth over their allocations.

I had purchased a contract with a shared hosting service which allowed 27gb/month of traffic. This seemed like more than enough at the time. However, I was noticing the bandwidth increasing at an alarming rate - about 2gb/day. At that rate, I would exceed the allotment by quite a bit. I had some time, but not much.

Okay, what to do? I looked around at the various shared hosting options and didn't see much that was all that attractive. There were some that offered "unlimited" bandwidth - I didn't trust these at all. Most of the terms and conditions actually did place a "reasonable" limit of some kind. I preferred a limit that was know verses a limit that was unknown.

Actually, truth be known, I was getting a little tired of the paid host option. I mean, it's far improved from free hosts, but there is still much room for improvement. Some of the things that were bothering me were:

Downtime - All of the shared hosting servers that I'd checked out so far seemed to be down more often than desired. I've been in the computer industry for over 23 years, and to me a few hours of downtime in an entire year is about all that's acceptable. It's not that hard to achieve these kinds of statistics - I've been doing it myself for years.

Support - The level of support from virtually all hosting companies I've used to date has been pathetic to mediocre. My expectation is simple. My site is down, I want someone to work on it quickly. I want to call someone, get an answer right away, and get the problem resolved. Especially during normal business hours. I have never received that level of support from any hosting company yet.

Strange errors - I've noticed that my web sites will run fine for a few days or weeks, then start having strange delays. I know this because I monitor my sites with an automated service. These delays are probably caused by things that other customers are doing on the same server.

Lack of communication - Web host support people seem to forget that we webmasters and businessmen depend upon our web sites. I don't know about you, but if my site goes down for any length of time I completely freak out. I want to know why it's down and what's being done about it. And virtually always I get no answers. This is most annoying when the downtime has been planned - these hosts have my email address, why is it so hard to send an email and let me know what's going on?

Log file issues - Log files are very important to any true webmaster. They are useful for finding errors, gauging traffic and determining the success of promotions and articles. Yet so far all of the shared hosts gave me incredible grief about log files. They seemed to want to initialize them at odd intervals (unpredictable), didn't allow easy access, allowed too easy (unsecured) access and generally made it difficult.

Okay, given all of that, it was time to make a change. Not just a change to another host, but a change in paradigm.

I had tried free hosts (three of them) before deciding they were not at all suitable for anything except a small hobby web site. I moved up to paid shared hosts and for a while was happy. I moved, then moved again, then again. The hosts were all fine for a while, then starting having trouble.

Shared hosting was not doing what I needed. The straw that broke the camels back was a question of bandwidth. Internet Tips and Secrets was exceeding 50gb a month (almost four million hits and three quarters of a million page views). Wow.

I could not find a shared host that offered a package of a full gigabyte of disk and upwards of 50gb a month. Not a single one after looking at over a hundred different packages.

I had a real problem. You see, go over the monthly bandwidth charge and you get smacked with huge overcharges. For the web host I had at the time, the charges were $6 per gigabyte. This would make my hosting bill very large indeed.

Thus I began looking for a dedicated hosting service. I quickly found a company and purchased a single month.

Here's what I got. A web server all to myself. I could define as many as 250 different web sites on the server, and I had complete control of the DNS. I had root access to the server (meaning I was more or less god on the box) and could literally do anything I wanted. I could install anything, do anything and control or not control everything.

I had 9gb of disk space. Best of all, the service provided a whooping 400gb of bandwidth usage per month. The server was extremely fast for my needs. All for around $200/month plus a setup fee.

The downside (there is always a downside, isn't there)? The price was a little steep, but a predictable $200 a month is far superior to a surprise $500 or even $100 hosting charge. They also didn't provide any real autoresponders (but I solved that by purchasing a package) or web based email. Their support is also very basic - they have a 24 hour help desk which is friendly and competent, but they do not appear to be technical heavyweights.

Thus I have now, after a week of hard work, begun a new adventure - a dedicated web server for the 16 sites that my wife and I own. So far, the experience is far superior to the shared hosting nightmares that I've been facing.

Richard Lowe Jr. is the webmaster of Internet Tips And Secrets at http://www.internet-tips.net - Visit our website any time to read over 1,000 complete FREE articles about how to improve your internet profits, enjoyment and knowledge.