Donal K. Fellows wrote:
dejw wrote:
I agree, this is some solution (magic names) but I have to dig into EPRs as it is good for a user to know real job id - later any debug action could be done directly between user and supervisor of the target BES service and target job management service (it was checked by us in practise). If user doesn't know the real job id then the portal admin has to be involved to get it somehow in some critical situations let's say. So finally I have to get it anyway.
I know of at least one implementation that won't tell you the job identifier, no matter how you look in the EPR. You *can't* rely on it being there.
Alright - but this might be something interesting to implement/explore when composing the OGSA-BES interface with an SLA interface. For example: The service offers in its generic SLA to pass through the job id, for a small fee, for example .99 USD. The user reads this SLA, decides he accepts it, and, along with the job submission, passes *his* SLA describing the acceptance of the fee and details how to debit his credit card. Cheers, Michel -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834