Notifying service about user's operations

$ cat ~/JDLs/activity_files_push.adl 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CreateActivities>
    <ActivityDescription>

        <ActivityIdentification>
            <Name>CustomJob</Name>
            <Description>A job that to run needs a file to be sent and writes its elaboration on an output file to be retrieved.</Description>
            <Type>single</Type>
        </ActivityIdentification>

        <Application>
            <Executable>
                <Path>myjob.sh</Path>
                <Argument></Argument>
                <FailIfExitCodeNotEqualTo>0</FailIfExitCodeNotEqualTo>
            </Executable>
            <Environment>
              <Name>MY_ENV</Name>
              <Value>"my env"</Value>
            </Environment>
            <Error>JobError.txt</Error>
            <Output>JobOutput.txt</Output>
        </Application>
        <Resources>
            <QueueName>creamtest2</QueueName>
        </Resources>

        <DataStaging>

          <ClientDataPush>true</ClientDataPush>

          <OutputFile>
            <Name>JobError.txt</Name>
            <Target>
              <URI>gsiftp://cream-23.pd.infn.it//tmp/JobError.txt</URI>
              <DelegationID>04352064184726456</DelegationID>
            </Target>
          </OutputFile>
          <OutputFile>
            <Name>JobOutput.txt</Name>
            <Target>
              <URI>gsiftp://cream-23.pd.infn.it//tmp/JobOutput.txt</URI>
              <DelegationID>04352064184726456</DelegationID>
            </Target>
          </OutputFile>
        </DataStaging>

    </ActivityDescription>
</CreateActivities>

When the user submits this ADL the CE returns a particular status attribute saying that the CE is waiting for the user action (sending a file):

$ glite-es-activity-create --endpoint cream-52.pd.infn.it ~/JDLs/activity_files_push.adl
*****************************************
ActivityID     = CR_ES510328951
ActivityMgrURI = https://cream-52.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService
Status         = PREPROCESSING
Status Attrs   = {CLIENT_STAGEIN_POSSIBLE}
Timestamp      = Tue Mar 27 09:22:05 2012
Description    = 
ETNSC          = 
STAGEIN Dir    = {gsiftp://cream-52.pd.infn.it/var/cream_es_sandbox/dteam/CN_Alvise_Dorigo_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam021/51/CR_ES510328951/ISB}
SESSION Dir    = {}
STAGEOUT Dir   = {gsiftp://cream-52.pd.infn.it/var/cream_es_sandbox/dteam/CN_Alvise_Dorigo_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam021/51/CR_ES510328951/OSB}

We've already seen above that the user will have to send the myjob.sh executable into the "STAGEIN Dir" and then notify the CE:

$ glite-es-notify-service -e cream-52.pd.infn.it CR_ES510328951:CLIENT-DATAPUSH-DONE

The syntax of the glite-es-notify-service command is simple: the endpoint is the same for all the other commands; the argument CR_ES510328951:CLIENT-DATAPUSH-DONE is simply the <Activity_Identifier>:<ACTION_TO_NOTIFY>. The <Activity_Identifier> is to indicate which activity in the CE is affected by the action performed by the user; the <ACTION_TO_NOTIFY> can have at the moment only these two values:

• CLIENT-DATAPUSH-DONE
• CLIENT-DATAPULL-DONE

We've just seen the meaning of the former. The CLIENT-DATAPULL-DONE is to be sent when the activity is terminated, and output files, available on the CE in the "STAGEOUT Dir", have been retrieved by the user.