Deployment Howto

Installing the files

Download either the ZIP or TAR/GZ distribution of the tester deployment package. You will want to copy this file somewhere under your web root. If you are unsure about this you may need to consult your network administrator. Once there, you will need to expand the package as follows.

For the ZIP file:

unzip mtester-deploy.zip

For the TAR/GZ file:

tar zxvf mtester-deploy.tar.gz

This will create a subdirectory named "mtester". Remember when accessing the URL later, you will need to add "/mtester" to the location where you originally placed the distribution. For example; if you placed the mtester-deploy.tar.gz file in /var/www/html (the toplevel directory in the web root) you would later view the tester with the URL http://www.myserver.com/mtester.

Necessary modifications

After unpacking the files there are two files you will need to edit. Inside the "mtester" directory created in the previous step you will find files named "test.html" and "test_ns.html". Open these files up in your favorite text editor and look for the lines:

<param name="success" value="http://www.multicasttech.com/?main=mt/success.html">
<param name="failure" value="http://www.multicasttech.com/?main=mt/failure.html">

You will need to modify the value in each of these parameters to reflect the files "success.html" and "failure.html" in the current directory. Unfortunately, a relative path will not work here. So, considering the same example as before, we would change the lines to the following:

<param name="success" value="http://www.myserver.com/mtester/success.html">
<param name="failure" value="http://www.myserver.com/mtester/failure.html">

Running the tester

The tester is now ready to be run from it's installed location. Depending on where you installed it you will need to adjust your URL accordingly, but following our earlier example we would access the tester with the URL:

http://www.myserver.com/mtester/"

Further customizations

You can of course adjust any of the additional html to suit your web site. All we ask is that you leave a link back to Multicast Technologies. There are a few more parameters which you can pass to the tester applet:

• group - the multicast group to join
• port - the port to bind
• timeout - the number of seconds to wait for data before giving up
• success - a URL to redirect to upon success
• failure - a URL to redirect to upon failure
• internal - a URL to redirect to upon internal error
• security - a URL to redirect to upon a security error (user not granting permission)
• target - the target which will be redirected (ie;, "_top", "_parent", etc)

Changing the group and port parameters will allow you to test for the user's ability to receive your own multicast content.

Common problems

This happens when you have not correctly adjusted the redirect parameters for success and failure. See the section titled "Necessary modifications".

This typically happens when there is a malformed URL in the applet parameters. Check that the URL is valid.

Please run the tester located at Multicast Technologies. If you get the same error message please submit a bug report indicating your platform, operating system, browser version, and JVM version.

We are using some server side scripting to detect older versions of Netscape, and swap out the button automatically. A file named "onebutton.php" is included in the distribution to demonstrate how we accomplish this. It is not the default page in the distribution because not everyone has PHP available to them.