Modifying the connection EPR

https://cream-52.pd.infn.it:8443/ce-cream-es/services/CreationService

• Activity creation: /ce-cream-es/services/CreationService
• Activity status, cancel, pause, resume, restart, wipe, info: /ce-cream-es/services/ActivityManagementService
• Activity list: /ce-cream-es/services/ActivityInfoService
• Delegation operations: /ce-cream-es/services/DelegationService

These EPRs in principle can differ from the EPRs of another ES implementation, then the ES command line has the possibility to specify a different EPR for a certain operation. In the following example we create an activity to a CREAM/ES implementation (cream-10.pd.infn.it) and to a Unicore/ES implementation (zam052v02.zam.kfa-juelich.de:8080) specifying two different EPRs; note that we will use the -d (--debug) option in order to print extra information (e.g. the complete address to contact, including the EPR):

$ glite-es-activity-create --endpoint zam052v02.zam.kfa-juelich.de:8080 --epr /EMI-ES/services/CreateActivityService ~/JDLs/activity_sleep120.adl -c ~/.globus/usercert.pem -k ~/.globus/userkey_nopass.pem -d
Parsing XML file [/home/dorigoa/JDLs/activity_sleep120.adl] and converting to SOAP objects...
There're 1 activity/ies to submit
Sending CreateActivity request to service [https://zam052v02.zam.kfa-juelich.de:8080/EMI-ES/services/CreateActivityService]
*****************************************
ActivityID     = 5c9b6f1e-1a3b-409f-aea4-d550c57bf155
ActivityMgrURI = https://zam052v02.zam.kfa-juelich.de:8080/EMI-ES/services/ActivityManagementService
Status         = ACCEPTED
Status Attrs   = {CLIENT_STAGEIN_POSSIBLE}
Timestamp      = Thu Jan  1 01:00:00 1970
Description    = 
ETNSC          = 
STAGEIN Dir    = {gsiftp://zam052v07.zam.kfa-juelich.de:2811/home15/unicore/FILESPACE/5c9b6f1e-1a3b-409f-aea4-d550c57bf155/}
SESSION Dir    = {}
STAGEOUT Dir   = {}

$ glite-es-activity-create --endpoint cream-10.pd.infn.it --epr /ce-cream-es/services/CreationService ~/JDLs/activity_sleep120.adl -d
Parsing XML file [/home/dorigoa/JDLs/activity_sleep120.adl] and converting to SOAP objects...
There're 1 activity/ies to submit
Sending CreateActivity request to service [https://cream-10.pd.infn.it:8443/ce-cream-es/services/CreationService]
*****************************************
ActivityID     = CR_ES569960280
ActivityMgrURI = https://cream-10.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService
Status         = PREPROCESSING
Status Attrs   = {}
Timestamp      = Fri Mar 30 09:57:14 2012
Description    = 
ETNSC          = 
STAGEIN Dir    = {gsiftp://cream-10.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_dteam004/56/CR_ES569960280/ISB}
SESSION Dir    = {}
STAGEOUT Dir   = {gsiftp://cream-10.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_dteam004/56/CR_ES569960280/OSB}

Note the different EPRs used for the two activity creations. The ES UI has defaults built-in for all the EPRs needed to contact a CREAM/ES implementation (in fact, this guide refers to the CREAM/ES UI, conceived mainly as CREAM/ES client, but able to 'talk' also to other ES implementations thanks to the standardized ES interface).

Also note that for the Unicore/ES implementation (that does not support yet the proxy certificates) we had to specify our certificate and key files with the corresponding options described above.

In the following example we will ask for activity's status on both CREAM/ES and Unicore/ES implementations using, again, different EPRs:

$ glite-es-activity-status --endpoint zam052v02.zam.kfa-juelich.de:8080 --epr /EMI-ES/services/ActivityManagementService -c ~/.globus/usercert.pem -k ~/.globus/userkey_nopass.pem -d 5c9b6f1e-1a3b-409f-aea4-d550c57bf155
Sending ActivityStatus request for ActivityID(s) {5c9b6f1e-1a3b-409f-aea4-d550c57bf155} to service [https://zam052v02.zam.kfa-juelich.de:8080/EMI-ES/services/ActivityManagementService]
*****************************************
ActivityID  = 5c9b6f1e-1a3b-409f-aea4-d550c57bf155
Status      = TERMINAL
Attributes  = {CLIENT_STAGEOUT_POSSIBLE}
Timestamp   = Fri Mar 30 10:00:34 2012
Description = 

$ glite-es-activity-status --endpoint cream-10.pd.infn.it CR_ES778754308 -d
Sending ActivityStatus request for ActivityID(s) {CR_ES778754308} to service [https://cream-10.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService]
*****************************************
ActivityID  = CR_ES778754308
Status      = TERMINAL
Attributes  = {}
Timestamp   = Fri Mar 30 09:49:16 2012
Description = reason=0

Note that in this last example, for the status request to cream-10.pd.infn.it (CREAM/ES implementation) we omitted the --epr option and the command used the (correct) built-in EPR value (/ce-cream-es/services/ActivityManagementService). If we try to get activity status on the Unicore/ES and we forget the EPR specification, the built-in will be used and an error message will be returned by Unicore:

$ glite-es-activity-status --endpoint zam052v02.zam.kfa-juelich.de:8080 -c ~/.globus/usercert.pem -k ~/.globus/userkey_nopass.pem -d 5c9b6f1e-1a3b-409f-aea4-d550c57bf155
Sending ActivityStatus request for ActivityID(s) {5c9b6f1e-1a3b-409f-aea4-d550c57bf155} to service [https://zam052v02.zam.kfa-juelich.de:8080/ce-cream-es/services/ActivityManagementService]
Received NULL fault; the error is due to another cause:  FaultString=[Cannot send message to https://zam052v02.zam.kfa-juelich.de:8080/ce-cream-es/services/ActivityManagementService, such a site is not registered with this gateway.] FaultCode=[SOAP-ENV:Client] FaultSubCode=[SOAP-ENV:Client] FaultDetail=[]