| [4] | 1 | # |
|---|
| 2 | # |
|---|
| 3 | # APP LAUNCHER for SAGE2 |
|---|
| 4 | # |
|---|
| 5 | # |
|---|
| 6 | # Ratko Jagodic - Nov 8, 2006 |
|---|
| 7 | -------------------------------------------------------- |
|---|
| 8 | |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | 1) INSTALLATION: |
|---|
| 12 | ------------------ |
|---|
| 13 | - appLauncher comes with sage and is placed in the bin/appLauncher folder |
|---|
| 14 | - there is no need to install it but you do have to have python2.4 or |
|---|
| 15 | later in order to run it |
|---|
| 16 | |
|---|
| 17 | |
|---|
| 18 | |
|---|
| 19 | 2) CONFIGURATION: |
|---|
| 20 | ------------------ |
|---|
| 21 | - you need to modify the "applications.conf" file in the appLauncher folder |
|---|
| 22 | - the format of the file and additional comments are in the file itself |
|---|
| 23 | |
|---|
| 24 | |
|---|
| 25 | |
|---|
| 26 | 3) HOW TO RUN: |
|---|
| 27 | ---------------- |
|---|
| 28 | - to run type (from bin/appLauncher directory): |
|---|
| 29 | |
|---|
| 30 | python appLauncher [sage_config_file][-v] |
|---|
| 31 | |
|---|
| 32 | - the first (optional) parameter is an alternative config file that the appLauncher |
|---|
| 33 | will use instead of the default "applications.conf" |
|---|
| 34 | - '-v' shows the output of the appLauncher on the console, if not specified |
|---|
| 35 | the output will be written to 'output.txt' and 'errors.txt' |
|---|
| 36 | - you can also run the appLauncher constantly in the background since it's |
|---|
| 37 | not necessary to restart it whenever sage is restarted: |
|---|
| 38 | |
|---|
| 39 | python appLauncher & |
|---|
| 40 | |
|---|
| 41 | |
|---|
| 42 | |
|---|
| 43 | 4) APP CONFIG GENERATION: |
|---|
| 44 | -------------------------- |
|---|
| 45 | - one of the main goals of the applauncher is to generate the app config files, |
|---|
| 46 | copy them to the rendering machine and execute the application |
|---|
| 47 | - for this to work you need to have "scp" enabled and you need to have ssh permissions |
|---|
| 48 | on the rendering machines (the best is to set up ssh keys so that you dont have to |
|---|
| 49 | type in passwords every time you launch an application) |
|---|
| 50 | - the appLauncher also makes use of the SAGE_DIRECTORY environment variable in order |
|---|
| 51 | to copy the app config files into SAGE_DIRECTORY/bin |
|---|
| 52 | - the app config files are generated from the applications.conf AND from the requests made by |
|---|
| 53 | SAGE UI when launching applications. For example, if SAGE UI requests that the app be |
|---|
| 54 | shareable, the appLauncher will write the sageBridge info into the app config file, |
|---|
| 55 | otherwise the app will connect directly to SAGE and it wont be shareable. |
|---|
| 56 | |
|---|
