------------------------------ -*- Mode: Text -*- -----------------------------
-- ml-setup.txt ---
-- Author           : Mustafizur Rahman ( rahman@jajabor.com )
-- Created On       : Tue Jan 11 17:07:58 2000
-- Created On Node  : quite01.camb.opengroup.org
-- Last Modified By : Mustafizur Rahman
-- Last Modified On : Wed Jan 19 19:34:49 2000
-- Last Machine Used: quite01.camb.opengroup.org
-- Update Count     : 63
-- Status           : Verified Tue Jan 11 19:52:39 2000
-- HISTORY          :
-- Description      : Instructions for starting the R1 AQuA demo
--
-------------------------------------------------------------------------------

This document lists the steps required to bring up the Missile
Launcher (ML) demo for R1 QUITE presentation of July 1999.  A test
driver is provided to verify the ML code so that the setup can be
tested before the final integration in the testbed with other components.

Three machines are required to run the test driver.  We will label
them as float1, float3, and quite05.  float1 and float2 should be
running Linux Red Hat V5.2 with Windows NT V4.0 on quite05.

Software Dependencies
---------------------
o AQuA 0.5 at /home/testbed/aqua/aqua-0.5
o QuO V1.0 at /home/testbed/aqua/quo-1.0

o JDK V1.1.7_v3 (jdk116_v5 for R1 originally) at /home/testbed/aqua/jdk116_v5
o VisiBroker V3.4 (V3.3  for R1 originally) at /home/testbed/aqua/vbroker

quite05
-------
 1. Edit up.txt to specify correct path for ftp to ship IOR files to UNIX
 2. Bring up the VisiBroker SmartAgent
 3. On a DOS window, start channelFromEd.bat:

    > cd <ml_java_directory>
    > channelFromEd.bat

    Note: the ml_java_directory above is the mirror image of
	  /home/testbed/aqua/aqua-0.5/apps/slideshow/java on float1

 4. On a seperate DOS window, start PushSupply (the test driver):

    > java PushSupply

    Note: ensure that both PushSupply.java and TestLaunch.java are
	  compiled using "javac."

 5. On another DOS window, run up.bat to ftp over the IOR files:

    > up.bat

float1
------
 1. Log in as "testbed"
 2. Source in the environment under bash:

    % cd /home/testbed/aqua
    % . aquaSetup

    Note: aquaSetup MUST be modified if machine names other than
	  float1 and float3 are used.  See section
	  "Environment Variable Changes" elsewhere in this document.

 3. cd /home/testbed/aqua/aqua-0.5
 4. Edit ./aqua.config to reflect IP address of float1 (labeled host
    "foo" in the file) and float3 (labeled host "xyz" in the file)
 5. "compile" the configuration:

    % ./config/aqua_configure ./aqua.config

 6. cd /home/testbed/aqua/ensemble/demo
 7. Start the gossip server:

    % ./gossip &

 8. On a new xterm, start depman:

    % /home/testbed/aqua
    % . aquaSetup
    % cd /home/testbed/aqua/aqua-0.5/depman
    % ./depman.float1

 9. On a new xterm, start a factory:

    % cd /home/testbed/aqua
    % . aquaSetup
    % cd /home/testbed/aqua/aqua-0.5/factory
    % ./factory.float1

float3
------
 1. Log in as "testbed'
 2. cd /home/testbed/aqua/aqua-0.5/factory
 3. On an xterm, start a factory:

    % cd /home/testbed/aqua
    % . aquaSetup
    % cd /home/testbed/aqua/aqua-0.5/factory
    % ./factory.float2

float1 (after setting things up on float3)
------------------------------------------
Once, float1 and float3 are registered with depman (they will be
listed in the AQuA Depman GUI), the following need to be entered to
complete the AQuA regsitration process such that factories can bring
up the actual (ML) servers:

 1. On the small Depman window (QuO Regions), click ADD
 2. On the new pop-up window (New Region), enter the following values
    for the fields specified:

    Region Name:	Launch
    Sender Process:	slide_client1
    Server Process:	slide_server1

 3. Click the ACCEPT button

Depman should instruct the respectives factories to start
slide_server.  Once successfully started, the AQuA window should list
a view change in the top text list (ACTIONS) with float1 and float3
being active for slide_server1.  A new xterm will be spawned by the
factories to start slide_server (the xterm may be started as iconized)
om the display.

We can now start the what is known as the Launch Decision
Manager (LDM).  The actual process is "SlideClient."

 4. On an xterm, start the LDM:

    % cd /home/testbed/aqua
    % . aquaSetup
    % cd /home/testbed/aqua/aqua-0.5/apps/slideshow
    % ./slide_client1.float1

The LDM should now come up and start receiving tracks which will be
sent to the two servers that display the incoming track on their
respective xterm windows.

Environment Variable Changes
----------------------------
If machine names other than float1 and float3 are used, then aquaSetup
shell "script" needs to be modified to reflcet the change in machine
names.

1. /home/testbed/aqua
2. Edit ./aquaSetup to modify the following to reflect local machine
   names if names other than float1 and float3 are used:

		  ENS_GOSSIP_HOSTS     # Linux V5.2 machine name for Ensemble
		  *PATH*	       # respective PATHs
		  *HOME*	       # respective PATHs
		  VISIBROKER_JAVA      # directory of VisiBroker
		  JAVABROKER	       # full path to "vbj"
				       # - usually $VISIBROKER_JAVA/bin/vbj

-------------------------------------------------------------------------------