General Rules for Demos

This document contains the procedures to run an mBS demo as well as the common ways to rebuild it.

Demo Location

The demos of a package are placed in the demo/<package_name> directory where <package_name> is the directory named after the package, for example framework for the Framework Professional Edition Package . If a demo contains bundles, there are located in the demo/bundles folder of the package.

Starting a Demo through an Install Script

This is the easiest way to deploy an mBS demo when it is supplied as a bundle or a set of bundles. The install script handles installation of the demo as well as of all bundles the demo depends on. If some of the components have already been activated, the script will skip them.

The demo's install script is install.txt, located in the demo/<package_name>/<demo_dir> directory where <demo_dir> is the directory of the demo.

There are two ways to invoke an install script:

• Through the Kit Manager Bundle (kitman.jar, from the bundles directory of the Framework Professional Edition Package ).

  To run the demo:

  1. Activate the Kit Manager Bundle on your framework.
  2. Enter the kitman command group by typing kitman/ in the framework console.
  3. (Optional) If you are to install the demo by its ID in the Kit Manager Bundle:
     1. Invoke the list of available scripts by typing list.
     2. Find the ID of the demo and memorize it.
  4. Load the execution of the script through the following command:

     install <kit_ID>

     where <kit_ID> is the ID of the demo's install script or

     install "<kit_name>"

     where <kit_name> is the demo name specified in the install script

• Using the exec command in the framework console. In the framework console type the command:

  exec ../../demo/<package_name>/<demo_dir>/install.txt

Rebuilding a Demo

If you changed the source of the demo, you may recompile and repack it by executing the mk script.

The setenv script file in the demo directory serves for tuning the Java environment. You can modify the path contained there so as to lead to the actual location of the executable files of the interpreter, compiler, etc. of the active VM.

Framework Demos