Loading...
 
ESA > Join & Share > HMA-T > ERGO PROGRESS 0810 INTECS
Print

ERGO PROGRESS 0810 INTECS

ERGO Progress October 2008: Intecs

 

Project Manager Assessment

 

The status of the project is nominal.

 

Key Problem List

 

*Intecs has received the EbRR APIs for the integration of the registry in the Toolbox. The first version of the APIs was not compliant with the requirements. It was a set of java client API (thus using SOAP to communicate with the registry). Intecs asked 4CT to provide a server side set of APIs which can be used to directly access the core of the registry. This new version of the APIs has been received the 24th of October. 

 

* The first version of the EbRR registry runs only on Glassfish. The requirements require a tool which runs on Tomcat. 4CT has started the development of a Tomcat compliant version. Some check are needed on Intecs side to verify that everything is compliant with the requirements and the Toolbox libraries version.

 

Intecs will evaluate if these issues can have an impact on the final schedule.

 

 

 

Risk Table

 

ID Risk Title                           Severity Likelihood Risk Index Risk Domain Action and status

1      

- - - - -

2      

- - - - -

 

 

Deliverables List

 

The following documents have been delivered:

 

*none

 

WP1000: Project Management

 

Activities performed

*Normal work.

 

Outcomes and results

*none.

 

Problems and concerns

*none.

 

Plans for next period

*none

 

 

 

 

WP2100: Requirement definition

 

Activities performed

*none.

 

Outcomes and results

*none.

 

Problems and concerns

*none.

 

Plans for next period

*This WP has been completed

 

 

 

 

WP3100 Integration of the OMAR open source implementation in the SSE Toolbox

 

Activities performed

* EO EbRIM profile. Started discussion over differences between official CSW 2.0.2 EbRIM schema set and the 4CT one. Differences have been found in the usage of two different GML version. The GML version used by the 4CT schema set has been considered mandatory to cover all project needs. A proposal for changed has been submitted.

 

* Started integrating EbRR backend through provided API. Started a discussion about the implementation of the API itself, implementing a SOAP exchange as transport mode. This point has been discussed in depth and it has been decided to create an API set that can connect directly to EbRR through Java calls. The new API will maintain the same interface at client side, allowing a parallel develop between Intecs and 4CT.

 

* Started a discussion over the servlet engine to be used. Tomcat 5.5 will be used as servlet engine. 4CT started moving EbRR from Glassfish to Tomcat 5.5 platform. Waiting for this version to comlpete integration of the tool inside Toolbox Runtime Environment. Currently using networked based API to continue some of the development tasks.

 

Outcomes and results

*none.

 

Problems and concerns

*none.

 

Plans for next period

* Start integrating EbRR in Toolbox.

 

* Switch between SOAP based API to Java based ones.

 

 

 

 

WP4100 Validation and Conformance testing

 

Activities performed

*Activity is not yet started.

 

Outcomes and results

*none.

 

Problems and concerns

*none.

 

Plans for next period

*none


Contributors to this page:
Massimiliano Fanciulli .

Page last modified on Monday 03 of November 2008 09:52:21 CET by .

Category: HMA-T