########################################################################
# INSTALL
#
# Instructions for installation of the demo package
# accompanying this tutorial.
#
# Albert L. Rossi, IU Extreme! Computing
# December 2001
########################################################################

We suggest that, for simplicity, you use the provided Ldap
host and context for registering event channels.

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

1.  Necessary modifications to the shell scripts
    (in the scripts directory):

    - run.sh:             You may wish to hard-code the JDK path,
                          though the script should locate the
                          installation automatically.  Also, if
                          you do not wish to use IU-Extreme Lab's
                          Ldap server, you will need to set the
                          EVENTS_CTX to wherever you will be 
                          registering event channels.

    - javaComp.sh:        Set the JDK variable to the path where
                          Java 1.3 or later is installed.

    - appMan.sh:          Set the JDK variable to the path where
                          Java 1.3 or later is installed.  If
                          you are not using IU-Extreme Lab's
                          Ldap server, set the REGISTRY_HOST
                          and REGISTRY_PORT variables to their
                          proper values.

    NB: the JDK variable needs to be hard-coded in the 
        latter two scripts because it may not be in the 
        environment visible to the Globus Gatekeeper.
    
------------------------------------------------------------------------

2.  Necessary modifications to the .xml files
    (in the xml directory):

    - appMan.xml:         <hostName> entries need to correspond
                          to the machines on which you will be
                          running the components.

                          <exec-dir> is the absolute path
                          where you have installed this package
                          plus wherever you wish the output
                          to be placed.  Note that this must
                          be either the directory where the
                          script to be executed is found, or
                          one of its ancestors.

                          <exec-script> should be the path
                          of javaComp.sh relative to the 
                          directory indicated above (just the
                          file name if the exec-dir is 
                          the scripts directory).
                      
    - printEnv.xml:       Follow the same directions as given
                          for appMan.xml.

    - build.xml:          Nothing need be changed.

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

3.  Necessary modifications to the .py files
    (in the scripts directory):

    - printenv.py:        If there is some other path to "sh"
                          other than /bin/sh on the host where
                          the appMan will run, you will need to
                          change the "command" string.

                          The Ldap information should reflect 
                          where you have registered the channel.  
                          If you have changed "EVENTS_CTX" in 
                          run.sh, then you will have to change 
                          it here.  Also, the channel name 
                          should correspond to whatever name 
                          you gave it when you launched it.

                          Note, however, that this script will
                          run even if there is no channel;
                          the ProcessManager will simply 
                          throw a few "ConnectionRefused"
                          Exceptions; you could get rid of
                          these simply by commenting out
                          option (a) and uncommenting option
                          (b) where the code reads "construct
                          ProcessManager".
    
    - launchAppMan.py:    Change "machine" to the remote host
                          on which you will be launching the appMan.

                          The script assumes you will be using
                          Gram to launch the job; if you wish to
                          use ssh or simply "exec" (the latter only
                          for local launches), you will need to change
                          the "setCreationMechanism" parameter.

    - launchJava.py:      Follow the same instructions as given for
                          launchAppMan.py.

    - launchAppManRSL.py: You will need to set the "host" variable,
                          as well as the "dir", "launchScript" and
                          "uploadScript" paths.  

                          "dir" should correspond to the <exec-dir>
                          value in the .xml files above.

                          "launchScript" should be the same as the
                          <exec-script> value.  

                          "uploadScript" is the path to "printenv.py".

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

4.  C source-code (in the exe directory):

    - printenv.c:         This code should be compiled with the 
                          C-compiler appropriate for the platform 
                          you are on; the binary should be called 

                          "printenv.out" 

                          and should be found in the exe directory, 
                          in accordance with the expectations of the 
                          "printenv.csh" script (in the scripts
                          directory) which calls it.

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

5.  Java source-code (in the java directory):

    This package comes ready with a demo.jar file already included
    in the lib directory.  

    Should you wish to make changes to the source and recompile,
    simply run "build.sh" from the java directory.  This creates
    a "build" directory containing the .class files, along with
    a new .jar file which it automatically moves to the lib directory
    so that it will be in the classpath.  To remove the build, do
    "build.sh clean".

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

6.  C++ source-code (in the cpp directory):


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