Application and Submitter Information Submitted by Tracy Safran Date 10-09-2008 (name & phone #) 301-402-1537 Application name LexEVS GRID SERVICE Version number 4.2 Government sponsor Frank Hartel QA approval Steve Hunter (name & phone #) 301.435.3869 (name & phone #) 301.435.6370 NCICB Build and Policy Documents https://gforge.nci.nih.gov/docman/index.php? Deployment Policies group_id=27&selected_doc_group_id=84&language_id=1

Forms and Templates https://gforge.nci.nih.gov/docman/index.php? group_id=27&selected_doc_group_id=317&language_id=1

Submitter has read all relevant policy and procedures documents available via the links above, and affirms that this deployment request and all supporting documentation and scripts is in conformance with them.

__No _X_Yes Build Information SVN module Server: Tag to build lexEVSgridsrv- https://gforge.nci.nih.gov/svnroo v42_QA_Refresh_02oct t/lexevs 08

Module: /LexEVS_Grid_Services/tags/

Associated change None. request(s) Changes to build _X_ No instructions __ Yes [updated build instructions must be provided; please note that if these changes have not been previously discussed there may be a delay in performing this deployment.] Link to build No build necessary. instructions Changes to _X_ No deployment __ Yes [updated deployment instructions must be provided; please note that if instructions these changes have not been previously discussed there may be a delay in performing this deployment.] Link to deployment Copy 1 jar and bounce JBoss. See details below in “Additional Instructions”. instructions Database update _X_ No necessary __ Yes [database deployment request form is required] Note: Database access is facilitated through the EVS API server. EVS API is a dependent application and needs to be deployed first or already available of the tier the grid services are being deployed to. Link to database N/A deployment supporting materials Additional Instructions Additional __ Build/deploy according to pre-agreed instructions (Initial Deployment) deployment instructions Should the application be stopped/undeployed prior to initiating the database scripts and remain unavailable during the database refresh? ____Yes [please clarify steps] ____ No _X__ Not Applicable

Order of the database script execution ____ Before deploying the new application unit (ear/war file). ____ After deploying the new application unit (ear/war file).

Should a maintenance page be posted during the db/app updates? ( If yes, please provide the HTML page) ____ Yes __X__ No

Restart application server after the db/app deployment (Cold vs Hot deploy- ment) __X__ Yes ____ No

__ Other [please explain]:

GENERAL DEPLOYMENT:

Deployment steps ======1. Shutdown JBoss 2. Copy castor-1.2-xml.jar from the QA server …/jboss- 4.0.5.GA/server/default/deploy/lib directory into the corresponding di- rectory on Stage 3. Start JBoss

Verify that the EVS grid service has successfully registered. 3. Review the JBoss log file. Locate a line containing “Successfully registered” with the date/time of this deployment. Proposed deployment to PROD Requested Date Approval For Promotion to Production Approved by Proposed deployment to production Requested Date