Software pre-requisites

GRID Pre-requisites:

This software makes use of gLite GRIDs and so can only be run in such contexts. You must have an account in a UI host configured for the GRID where you'll be launching your analysis jobs. That GRID must have installed Java6 in its CEs, in order for the application to run. Ask your GRID administrator for the software tag used to identify  Java6, and for the corresponding experiment software directory.

UI Pre-requisites:

The software must be installed in the UI. The UI must have Java6 installed as well. If the System Administrator does not support it, you can easily install one in your home directory. Please follow the JVM instructions for an account-specific installation, and remember to update the paths to point to that installation.

Server installation

Installation must be done in your home directory, within a UI host.

Create a directory, for example call it StockAnalysisService.

Copy in there StockAnalysisLauncher.jar and StockAnalysisJob.jar

Make a note of the IP address of the UI host; for example assume it is 195.251.52.32

Make a note of the software tag used to identify Java 6 in your GRID; for example assume it is VO-see-sunjdk1.6.0_04

Make a note of the experiment software directory used in your GRID, for java 6; for example assume it is VO_SEE_SW_DIR/jdk1.6.0_04

Notice that the experiment software directory begins with the name of the environment variable pointing to the specific software directory. Omit any initial $.

Create the file sal.properties with the following content:

java.software.tag=VO-see-sunjdk1.6.0_04
experiment.software.directory=VO_SEE_SW_DIR/jdk1.6.0_04
exp.sw.dir.environment.variable=VO_SEE_SW_DIR
remote.logging.server.ip1=195
remote.logging.server.ip2=251
remote.logging.server.ip3=52
remote.logging.server.ip4=32

To start the server, run:

nohup java -jar StockAnalysisLauncher.jar &

Client installation

Installation must be done in your home directory within a UI host.

Create a directory, for example call it StockAnalysisClients

Copy in there all client jars: SAL-T1Analysis.jar, SAL-T2Analysis.jar, SAL-Cancel.jar, SAL-Shutdown.jar, SAL-Status.jar

For convenience, update your path to include that directory.

To run a client, do it like this:

java -jar SAL-T2Analysis.jar paramters.txt stocks.txt

parameters.txt file format

gsiftp://egrid-se-01.pd.infn.it:2811//flatfiles/SE01/egrid/greekuser-data/;
ezio-3keys-id;

Line 1: either WMS or a specific CE to use such as t2-ce-01.lnl.infn.it:2119/jobmanager-lcglsf-euindia; also, specify either USE_TMP if you want the software to run on WN's temporay directory (useful in case of I/O intensive executables and NFS mounted job homes!), or DO_NOT_USE_TMP to run your executble right in the job directory as usual.

Line 2: name of executable file, followed by a comma (","), followed by either MEASURE_PERFORMACE or DO_NOT_MEASURE_PERFORMANCE

Line 3: comma separated list of extra files that are part of the executable

Line 4: comma separated list of attributes that must be passed on to the executable at invocation time

Line 5: comma separated list of input file name prefix

Line 6: comma separated list of input file name suffix

Line 7: comma separated list of input file directories starting with "ROOT/"

Line 8: comma separated list of input SEs URLs

Line 9: comma separated list of input Hydra Key Server key IDs; use "NO_HYDRA" if encryption is not used for the corresponding input file.

Line 10: comma separated list of output file name prefix

Line 11: comma separated list of output file name suffix

Line 12: comma separated list of output file directories starting with "ROOT/"

Line 13: comma separated list of output SE URLs

Line 14 comma separated list of output Hydra Key Server key IDs; use "NO_HYDRA" if encryption is not used for the corresponding output file.

Notice that:

• All lines must end with semi colon (";")

• You may leave a line empty by simply writing a semi colon for that line.

stocks.txt file format

It is a simple list of stock names.

Configuring the server for a business-logic Engine

Copy the executable and any file it needs, in the same directory where StockAnalysisLauncher.jar is found. The server will look in its installation directory for the executable and extra files it is instructed to use for an analysis. Now just edit the parameters.txt file that you will be using with the clients, accordingly.