Dear UNICORE Developers,
I need some help or guidance to complete an extension  to UNICORE the right way. My current approach was to follow your unittest examples (submit via jsdl) and write a custom java TSI for EDGI . Using a unicore installation with ucc and jsdl works fine.
My Problem: The Unicore-RichClient summit stuff differently than the ucc+jsdl combination does, with the result, that my code (checked against the unittest jsdls) didn't understand fully the code. In need some guidance, if there are methods or idioms to use, so that a RichClient-Submit, ucc, ucc+jsdl, and unittest result in the same behaviour. I found out (inside the TSI-submit-method) that the ucjob's jsdl (ucjob.ajd) is differently:
- test or jsdl case -
I have stage-entries in the jsdl, which are read by my code: ucjob.getAjd().getJobDefinition().getJobDescription().getDataStagingArray()
- rich-client -
stage-ins and -outs are given as env-variables: INPUT_..., even STDOUT/ERR is defined that way.
in that case my ucjob-object has the following properties
> ucjob.applicationInfo.environment = map INPUT-> ..., STDOUT ->...
> ucjob.stderr, ucjob.stdout is null
> ucjob.executionContext has stderr, stdout with values of "stderr", "stdout"
> ucjob.stageIns = null
> ucjob.stageOuts = null
> ucjob.type = "JSDL"
Bernd mentioned weeks ago, that the GridBean first upload the files, so that the server doesn't need to know them, because they are already in place. Eventually (I'm not sure) the ucc has a similar stagein-behaviour. That might explain the absence of staging entries. (Despite input files I also need to know the specified output files. Why? Because my TSI, or better EDGI's desktop grid interface need this info.)
DesktopGridExecution -> IExecution, IExecutionSystemInformation:
Many thanks for your help,
Best regards from Paderborn,
Computer Networks group
Warburger Straße 100
+49 5251 60 1754