Test Plan Scenario 26

This scenario tests the implementations of EMI-ES in the various middleware stacks. To this end clients of each of the middlewares are used to interact with service endpoints of each of the other middlewares. It is understood that a client of any middleware is capable of communicating with the same middleware's service implementations.

The following table is used to keep track of which tests have been done. The first column represents clients which access the service implementations represented by each of the following columns. So you read from left (clients) to right (services).

Arc -- Tested using simplified client: CreateActivity (no delegation), NotifyService, ActivityStatus, ActivityInfo, WipeActivity, ListActivities Tested using simplified client: CreateActivity (no delegation), ActivityStatus, ActivityInfo, WipeActivity, ListActivities, GetResourceInfo
CREAM TODO -- Tested: CreateActivity (no ISB/OSB yet 'cause delegat. problem), ActivityStatus, ActivityList, ActivityInfo, ActivityWipe, ActivityCancel
UNICORE TODO CreateActivity: NACK, ActivityInfoService: DONE, ActivityManagementService: TODO, DelegationService: TODO --

Endpoints and other information for the purpose of these tests are mentioned in the following sections.

Test campaign March 2013

During the March of 2013, a final test campaign was conducted with a specific focus on the Java client library (HiLA). Generally, the test results were successful, but also revealed some flaws that were fixed on the way. Whereas activity creation, management, and information had been tested previously, we particularly focused the delegation service.


ID Service involved Description Result
01 Delegation, ActivityCreation Create a delegation, add it's id to the ADL, submit the job. The delegation must be used during job execution, e.g. to transfer files. The ADL shown below guarantees this and involves two GridFTP servers. SUCCESS
02 ActivityCreation, ActivityInfo Verify that an activity with clientDataPush=true remains pending until notified to start. Import an additional file into the activity's StageInDirectory. SUCCESS
03 ActivityManagement After submission of an ADL that sets clientDataPush=true, start the job and run it successfully. SUCCESS

We used the following simple ADL to trigger the job and transfers.

<adl:ActivityDescription xmlns:adl="http://www.eu-emi.eu/es/2010/12/adl">
    <adl:Name>A Simple copy job.</adl:Name>


Test Description Expected Result Result
IT-26-NO-AUTHZ Access services, but authorization is not granted. Should return an AccessControlFault           Yes


Description Tracker URL Status (Pending/Solved)
Specify whether PEM header and footer are to be transferred for proxy certificates. The UNICORE implementation sends proxy without, whereas CREAM-Client expects the header and footer.   Solved, will send ----BEGIN... etc. header and footer

Deployed Middleware

The following endpoints have been used, before EMIR support was fully integrated. A testing campaign in March 2013 used the EMIR endpoint at http://emitbdsr1.cern.ch:9126/.


2 services are running at

Services implement all PortTypes of EMI ES and authorize members of testers.eu-emi.eu dteam VOs.



In order to get access, please send Björn Hagemeier <b.hagemeier@fz-juelich.de> an email with your DN that you use to access the testbed resources.

-- BjoernHagemeier - 12-Mar-2012

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r11 - 2013-03-12 - BjornHagemeierExCern
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback