NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

As an integrating/translational platform, caIntegrator depends on service-level or API interfaces for several other applications in the caBIG suite of tools.  Many of these applications have ongoing development and deploy multiple releases each year.  In order to better plan for potential breakage or retest necessary in caIntegrator, the team undertook an analysis of these dependencies and the planned release schedules for each.  This document highlights dependencies and serves as a place to discuss any breakage to caIntegrator and to schedule this into an iteration.

Application Dependencies

Note that only differences between the caIntegrator tech stack and the caBIG tech stack are highlighted here. Areas where we are already in compliance are not listed. See the Technology Stack 2010 page for a complete list.

Technology

caIntegrator
Version
(as of R1.2)

2010
Tech Stack
Version

Future
Tech Stack
Version

Notes/Recommended Resolution

Planned
Iteration

Container

 

 

 

 

 

JBoss

4.0.5

5.1.x

5.1.x

5.1.x incompatible with Grid as per Grid Compatibility Matrix
Until Grid 1.4 released, we cannot upgrade. Systems team has set a June 2011 deadline to upgrade though.
Chris to follow up with Grid team.

none

Database

 

 

 

 

 

MySQL

5.0.45

5.1.x

5.1.x

Upgrade when feasible or when forced by systems team or by CSM release that only supports 5.1.x.

Should be no breakage to queries/code for this upgrade.

TBD

CBIIT Internal

 

 

 

 

 

caGrid

1.2

1.3

1.4

NBIA has already upgraded to 1.3 but has provided us with a backward compatible client (1.2 based) to call their 1.3 service.  Any upgrade must also coordinate with Bioconductor (1.2 based), GenePattern (1.2 based), caDSR (?), and caBio (?) as well.
It appears that 1.2 clients can call 1.3 services, so our dependency is on other services continuing to build legacy 1.2 clients for us even if they upgrade.  Eventually this will become untenable and force us to upgrade to 1.3.
Work with dev teams for services we use in order to plan an upgrade to 1.3 if possible.

TBD

CLM

3.2

4.1.x

4.2.x

Unclear of the impact of this migration.
Chris to research further.

TBD

Build & Deploy

 

 

 

 

 

JDK

1.5

1.6

1.6

JDK 1.5 is end-of-life.  Systems has set a June 2011 deadline to upgrade.
We have run other systems successfully on JBoss 4.0.5 and JDK 1.6.  There should be no impact unless we need to provide API JARs to other applications that are built with JDK 1.6.
Recommend testing a JDK 1.6 build and migrating in an upcoming iteration.

TBD

Ant

1.7.0

1.7.x

1.8.x

We are already compliant with 2010.  We can move to 1.8.x when recommended by BDA.

none

AnthillPro

2.6

3.x

3.x

This is no work for the development team other than testing with new AHP server.
Recommend requesting systems team to migrate us to new AHP 3.0 server and retest builds.

TBD

Subversion

1.3

1.6.x

1.6.x

We are currently on the GForge SVN server, which is running 1.3.  We should migrate to the newer ncisvn SVN server which is on 1.6.  This should be no work for the development team other than having to re checkout from the new server when migration is complete and some testing.
Recommend requesting systems team to migrate us to ncisvn at a convenient time in the schedule.

TBD

Dev Libraries

 

 

 

 

 

Axis

1.2RC2

1.x

1.x

We are technically compliant here, but GenePattern(?) has shown an interest in upgrading to Axis 1.4.  We are locked into the current revision because of the grid.  We need to research alternatives to support a possible GenePattern upgrade in the future.

TBD

Spring Framework

2.5.6

2.5.x

3.x

We are compliant now.
Recommend low priority research into impact of 3.x upgrade next year.

none


  • No labels