"
Author: Traci St.Martin/Craig Stancl
Email: stancl.craig@mayo.edu
Team: LexEVS
Contract: [Contract number]
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
Sign off |
Date |
Role |
CBIIT or Stakeholder Organization |
Reviewer's Comments (If disapproved indicate specific areas for improvement.) |
---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Implementation Requirements
This 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.
Technical environment
No new environment requirements exist for the the LexEVS 5.1, with the exception of additional storage to accommodate larger content loads.
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
Server Hardware
Server
- NCI standard hardware.
Minimum Processor Speed
- Minimum required by JBoss.
Minimum Memory
- Minimum required by JBoss.
Storage
Expected file server disk storage (in MB)
- 200GB (May increase due to additional RRF content load)
Expected database storage (in MB)
- 100GB (May increase due to additional RRF content load)
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.0 and 5.1), there are JBoss considerations.
- Both lexevsapi 5.0 and 5.1 in the same container. This means that both http://lexevsapi.nci.nih.gov/lexevsapi50 and http://lexevsapi.nci.nih.gov/lexevsapi51 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.0 and 1 JBoss container for LexEVS 5.1.
External dependencies
N/A
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
Procedures for Development
Development will follow procedures as defined by NCI.
Detailed schedule
The LexEVS 5.1 project plan is located in Gforge at: LexEVS 5.1 Project Plan and LexEVS 5.1 Project Plan (PDF)
The LexEVS 5.1 BDA Project plan is located at: LexEVS 5.1 BDA Project Plan
Training and documentation requirements
Documentation for LexEVS 5.1 will be located on the Vocabulary Knowledge Center Wiki https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexBig_and_LexEVS
Download center changes
Downloads for LexEVS 5.1 will be located on the Vocabulary Knowledge Center Wiki https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexBig_and_LexEVS