Plan for Adaptation of Middleware Components

This page introduces the plan elaborated in the DJRA1.2 deliverable that is being followed up by the developments.

Component	Adaptation required	Deadline	Status
g-Eclipse	React on user feedback. Currently library provided by g-Eclipse is being evaluated by other partners. The possible request for changes and new functionalities will be implemented as soon as possible	October 08	done
g-Eclipse, JSDLJobDescription	Separate JSDL job description from IFile. JSDLJobDescription requires Eclipse IFile for storing JSDL into that file. It is recommended to separate it from IFile and allow to use standard java File or even prepare it in memory.	October 08	done
g-Eclipse, Job Management	Separate WMSClient, CREAMClient and LBClient from g-Eclipse model. All middleware related classes rely on g-Eclipse mode, e.g. for requesting authentication token. It is recommented to separate strictly middleware functionalities from g-Eclipse, so that they can be used outside g-Eclipse model. It is foreseen that WMSClient, CREAMClient and LBClient will not depend on g-Eclipse model. GliteJobAPI class will be split to pure GliteJobAPI and GliteJobEclipseAPI.	November 08	done
g-Eclipse, WMS and CREAM	Uniform CREAM and WMS access. CREAM is quite fresh implementation and has not yet full functionality like WMS. It is planned to uniform the classes for CREAM and WMS services to have the same set of methods. Also GliteJobAPI class should be reviewed and modified. Some additional helper methods will be implemented (e.g. managing set of jobs in the same call).	November 08	done
g-Eclipse, JSDL	Add more JSDL manipulation method. In g-Eclipse environment JSDL files are expected to be created by editor. As it is requested that JSDL objects should be created with API it is necessary to provide more methods for manipulating JSDL parameters.	December 08	done
g-Eclipse, Info-System	The information system plugins of g-Eclipse have to be extended to support instrumentation elements to allow browsing the available instrumentation elements in a g-Eclipse project.	January 09	done
g-Eclipse, IE	Since g-Eclipse does not support instrumentation elements yet it is required to add new plugins to g-Eclipse for accessing IEs. This will reuse the OSGi versions of the VCR IE functionality or use the IE web service directly.	January 09	done
g-Eclipse, glogin and GVid	The glogin and GVid client parts are already provided by plugins in g-Eclipse. It has to be examined if there are changes needed for the interactive applications that might use glogin and GVid for communication and visualisation output.	June 09	in progress
VCR, i2login	Integration of i2login to support interactive gridified applications	November 08	done
VCR, IE, gEclipse	IE Client code for accessing Instrument Element is pure Java. OSGi bundled for gEclipse	November 08	done
VCR, MyProxy	Client code for accessing MyProxy is pure Java based on the Globus package, with a VCR code layer on top of it.	December 08	done
VCR, all components	VCR porting on Gridsphere 3.x, GWT and JSR168 portlets	January 09	in progress
VCR, WfMS	Workflow client integration with the VCR	January 09	prototype
VCR, grid-components	VCR adaptation to access OGSi bundle(s) directly. Investigation of possibility for the GS3/GWT	February 09	abandoned
VCR, grid-components	VCR adaptation to CommonLib	July 09	in progress
VCR, OGC	Integration of OGC services	June 09	not started
WfMS	Providing interactivity for WfMS-components of VLab	December 08	done
IE, VOMS	VOMS integration	December 08	done
IE, plugins	Implementation of new plug-ins (Labview, EPICS, BCS, OGC, …)	June 09	not started

Back to top