| IMPLEMENTATION OPTION BENEFITS |
 Quick and secure
implementation as this solution does not need an Apache or IIS
server to be installed and maintained.
 Uses an
existing commercial web server for the front-end presentation
of the customer web pages.
 Same benefits as
item 2 above. In addition, speed tests are not performed
on the customer facing web servers, but on the back-end MySpeed
Server. This ensures better customer response times by isolating
the business website from the speed test activity.
 Same benefits as
item 3 above. In addition, use of multiple computers for the
MySpeed Server spreads the speed test demand across multiple
servers. This approach also enables speed and quality testing
of multiple network segments and application servers which
may be located in different cities and countries.
|
|
PERFORMANCE
DATABASE |
The Professional, NOC and Support Editions
record all speed test results in a server-side
database that provides visibility
to end-user bandwidth performance.
The Session
ID option enables easy tagging
of results to identify bandwidth performance
from individual customers, web pages, locations,
etc. |
|
| VoIP
TESTING |
| Try MySpeed
Server VoIP Editions add VoIP
simulation testing and analysis,
to identify the level quality of VoIP
sound supported your end-users’ connections. |
|
MYSPEED
FOR YOUR PC
|
Looking for an accurate
speed test program to run bandwidth tests
from your PC?
|
|
|
MySpeed Server provides flexible
options for implementations on a standalone
system
or as a back-end server to a front-end web server such as Apache
or IIS.
MySpeed Server Only
Web page is served directly
by the MySpeed Server
MySpeed Server is a self-contained fully
functional and secure web server
that does not require the use of commercial web servers such as IIS
or
Apache which are more complex to maintain and secure.
To implement this option, once you start
the MySpeed Server engine, all you need
is a web page to serve the Java applet. There
are several example pages included with MySpeed
for your use, or you can create your own
connection test page by adding the HTML below
between the BODY tags.
<applet name="MySpeed" code="myspeed.class" archive="myspeed.jar" width=600
height=400></applet>
MySpeed Server as Back-end
Web Server, Apache or IIS as Front-end Web
Server
Web page is served by IIS/Apache with
the Java applet served by the MySpeed
Server
To run MySpeed bandwidth tests on your own
web server such as Apache, you will need
to enable the codebase option
and then insert it in the HTML of the MySpeed
web page. The codebase option allows you
to serve the MySpeed test applet from a web
server other than the MySpeed web server,
even from a different system from where MySpeed
Server is installed.
The VoIP and speed tests are always conducted
from the server where the MySpeed applet
is served, not from where the web page is
served. This is important because using the
codebase option allows you to configure the
installation so the front-end web servers
(Apache or IIS) are not responsible for conducting
the actual speed tests themselves; instead
the codebase redirects the traffic to a designated
back-end server(s).
To use Apache or IIS as a front-end web
server follow these easy steps:
- From the Control Panel, Administration,
Server Configuration. In the ‘Permitted
Domains’ section, add the domain(s)
that you want to allow to serve the MySpeed
applet.
- The next step is to create a web page
for the IIS/Apache server that will serve
the Java applet from the MySpeed
Server. To do so, you may modify the
example speedtest.html or
voiptest.html files from the MySpeed
Server www directory,
in which case just add the codebase paramater
to the APPLET tags as shown below. Or,
you can use your own web page and insert
the HTML code below between the BODY
tags.
<applet name="myspeed" code="myspeed.class" archive="myspeed.jar" width=600
height=400 codebase=http://(myspeedserver:port)></applet>
In the above HTML, myspeedserver is
the domain (such as www.visualware.com)
or the IP address of your MySpeed
Server. If the MySpeed Server is using
port 80 (recommended, see note below),
it is not neccessary to indicate the
port number.
Once the codebase option is enabled in MySpeed
Server and in the web page on the IIS/Apache
server, you can view the MySpeed applet
on your web server via a browser.
NOTE: If the MySpeed
Server and the front-end IIS/Apache
web server are on the same computer
server then it is advisable to
allocate at least 2 IP addresses
to that computer server so each
web server (IIS/Apache and MySpeed)
can use the default port 80. Otherwise
one of the server engines will
be forced to use a port other than
80 which may cause firewall access
issues for users that block the
allocated port number.
|
|
Copyright © 1997-2007
Visualware Inc. · All Rights Reserved
|
