Page History

{scrollbar:icons=false}
h1. {page-info:title}
{panel:title=Contents of this Page}
{toc:minLevel=2}
{panel}
{panel}
*Author:* Craig Stancl
*Email:* Stancl.craig@mayo.edu
*Team:* LexEVS
*Contract:* CBITT BOA Subcontract# 29XS223
*Client:* NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
{panel}

*Revision History*
|| Version || Date || Description of Changes\\ || Author \\ ||
| 1.0 | 5/14/10 \\ | Initial Version Approved via Design Review | Team \\ |

Implementation requirements will include the technical environment (HW,OS, Middleware), external dependencies, teams/locations performing development and procedures for development (e.g. lifecycle model,CM), and a detailed schedule.

h2. Technical environment

No new environment requirements exist for the the LexEVS 6.0, with the exception of load balancing servers.

h3. Software (Technology Stack)

*Operating System*
* Linux (though no operating system dependencies currently exist)

*Application Server*
* JBoss 4.0.5

*Database Server*
* MySQL 5.0.45

*Other Software Components*
* caGrid 1.3 / Globus 4.0.3

h3. Server Hardware

*Server*
* NCI standard hardware.

*Minimum Processor Speed*
* Minimum required by JBoss.

*Minimum Memory*
* Minimum required by JBoss.

h3. Storage

*Expected file server disk storage (in MB)*
* 200GB

*Expected database storage (in MB)*
* 100GB

h3. Networking

*Application specific port assignments*
* Standard port required by JBoss to externalize LexEVS grid service. May be assigned any suitably available port #.

*JBoss Container Considerations*

There are specific requirements for JBoss containers for LexEVS 5.1.

In order to support multiple versions of LexEVS (for example 5.1 and 6.0), there are JBoss considerations.
* Both lexevsapi 5.1 and 6.0 in the same container. This means that both [http://lexevsapi.nci.nih.gov/lexevsapi51] and [http://lexevsapi.nci.nih.gov/lexevsapi60] can exist in the same Jboss container.

* Grid services can NOT be in the same JBoss container because of naming - they both need to be named /wsrf in the container. This results in the use of 1 JBoss container for LexEVS 5.1 and 1 JBoss container for LexEVS 6.0.

h2. External dependencies

N/A

h2. Team/Location performing development

* Traci St. Martin / Mayo Clinic
* Craig Stancl / Mayo Clinic
* Scott Bauer / Mayo Clinic
* Kevin Peterson / Mayo Clinic
* Sridhar Dwarkanath / Mayo Clinic
* Michael Turk / Mayo Clinic

h2. Procedures for Development

Development will follow procedures as defined by NCI.

h2. Detailed schedule

The LexEVS 6.0 project plan is located in Gforge at: [LexEVS 6.0 Project Plan (MPP and PDF)|https://gforge.nci.nih.gov/docman/index.php?group_id=491&selected_doc_group_id=5431&language_id=1]

h2. Training and documentation requirements

Documentation for LexEVS 6.0 is located at [LexEVS 6.0 Documentation].

h2. Download center changes

Downloads for LexEVS 6.0 are located at [LexEVS]

{scrollbar:icons=false}