How to test and include your tools in the Sieve inetBench

Last Change: 10/31/1999

Then follow the following steps:

Get a copy of the inebench and the HTML page that starts it at http://simon.cs.vt.edu/sieve/inetbench/
Now open the package and compile. Be sure to read README to see what you have to change in Makefile.config.
This file will create a sieve-root directory, and everything will be inside it.

Modify the ibench.cfg located in sieve-root to tell sieve to load your tool. The format of this file is as follows:

ibench.cfg

toolset1=NAME_TOOLSET#1(total:number_of_beans,bean₁₁,bean₁₂,...,bean_1n) . . . toolsetm=NAME_OF_TOOLSET#M(total:number_of_beans,bean_m1,bean_m2,...,bean_mn) links=link_class₁,link_class₂,...,link_class_k

toolsetn=toolset_name(toolset_definition). Defines a toolset. The format is toolsetn=toolset_name(class,class,...,class). n is a number that starts from 1 and should be consecutive for the next toolset; That is, toolset keywords must be toolset1, toolset2, ...,toolsetm. class can be any java bean or jar file. jarfiles are specified with the .jar extension. class files are specified with the full name. There you need to put the full qualified names of all the tools you want the workbench to load. For example, if you want to load the class CachedSTFTable located in the sieve.sluice.codebook package, and BoxPlot located in the sieve.nuggets package, you specify:
toolset1=Some_Tools(sieve.sluice.codebook.CachedSTFTable,sieve.nuggets.BoxPlot)";links=sieve.sluice.TableViewTableViewLink)
Note that I included sieve.sluice.TableViewTableViewLink in the links section.

Bean classes must also be declared with the full class name (ie. package1.package2.package3.classname), but without the .class extension.
links =link class name #1,link class name #2, ... Specifies the class name of the link classes to preload. Link classes must also be declared with the full class name (ie. package1.package2.package3.classname), but without the .class extension. It is better that Sieve preload the link instead of searching for it in runtime. As any other class, the link classes has to be accesible in the proper package directory.

Set up the HTML loading page to find the sieve client: In the sieve-root directory there is a page called startSieve.html that looks like this:

test.html

<!doctype html public
	      "-//w3c//dtd html 4.0 transitional//en">

	      <html>

	      <!--

	      This is an example of an HTML page to start the sieve client in stand alone
	      (non-collaborative) mode. See user1.html for an exampleof how to start in
	      collaborative mode.

	      --> 

	      <HEAD>



	      <TITLE>Sieve Test Page</TITLE>

	      </HEAD>

	      <P>

	      <OBJECT
	      classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" width="450"
	      height="60"

	      align="baseline" 

	      codebase="http://java.sun.com/products/plugin/1.2.2/jinstall-1_2_2-win32.cab#Version=1,2,2,0">

	      <PARAM NAME="type"
	      VALUE="application/x-java-applet;version=1.2.2">

	      <PARAM NAME="code"
	      VALUE="sieve.inetbench.applet.AppletButton.class">

	      <PARAM NAME="windowclass"
	      VALUE="sieve.inetbench.applet.AppletClient">

	      <PARAM NAME="windowwidth" VALUE="500">

	      <PARAM NAME="windowheight" VALUE="130">

	      <PARAM NAME="buttontext" VALUE="Click here to start
	      Sieve">

	      <COMMENT>

	      <EMBED type="application/x-java-applet;version=1.2"

	      pluginspage="http://java.sun.com/products/plugin/1.2/plugin-install.html"

	      code="sieve.inetbench.applet.AppletButton.class"

	      width=450 height=60

	      windowclass="sieve.inetbench.applet.AppletClient"

	      buttontext="Click here to start Sieve"

	      windowwidth=500 windowheight=130>

	      <NOEMBED>

	      </COMMENT>

	      Sorry, your browser does not have support for the java 1.2 plug-in. You need
	      it to run Sieve.

	      </NOEMBED></EMDED>

	      </OBJECT>

</BODY>

	      </HTML>

WWhat the colors mean

   This part is seen by both Internet Explorer and Netscape Navigator

   This part is only seen by Internet Explorer

   This part is only seen by Netscape Navigator

Don't feel intimidated by the code, you will ignore almost all of it. The only thing you as a develper need to customize is the applet path (CODE parameter).

Now open the page with your browser. If you did not see your tool in the list, see in the Java Console of the Java Plug-In if the class was found, chances are it did not. If you see your tool in the list of tools, try to instantiate the tools and change it is properties to stress your tools.

WWhat the colors mean
	This part is seen by both Internet Explorer and Netscape Navigator
	This part is only seen by Internet Explorer
	This part is only seen by Netscape Navigator

How to test and include your tools in the Sieve inetBench

ibench.cfg

test.html

WWhat the colors mean

If you got lost in any part of this instructions or for whatever reasons you want some help, please write to Dr. Clifford Shaffer ( shaffer@vt.edu).