|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Mayo/Jason||We have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources. We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server.||08/30/13||The server resources have been expanded with an addition vCPU and an additional 2GB memory. Initial tests have shown better performance but the testing is ongoing.|
|Area of Interest||Details|
Production environment has been setup and CTS2 and URI Resolver have been deployed.
Still having issues with the getting the firewall exception. ISSO asked about when we will be upgrading JBoss for 5.1 as this is an older version and shows up on the Nessus scan. The LexEVS 5.1 does not support running on a newer version of JBoss. We will need to get a waiver to get the firewall exception for 6.1 because it is on the same server at 5.1.
There is also an issue with the remote calls for 6.1 on all tiers. The Mayo team is looking into the issue.
|LexEVS 6.0 and 5.1||Both are on production and working. Per the comment above. We may be looking at a upgrade to JBoss 5.1.0 for LexEVS 5.1.|
The 2.3 release has been deployed to production and looks like it is working correctly. The smoke test passed.
We have been informed by NCBO that the new graph widget that we implemented with 2.3 release, and the API that it runs on was to be retired by the end of the January. We have been able to get that delayed but need to look at upgrading the widget in an interim release of the browser or remove the functionality so it will not break on production.
|Meta Download Validation App||Work on the GUI and continuing discussion on how the pages will be updated (Plone vs deployment from SVN)|
|Term Suggestion Form||Deployment to production is scheduled for early next week.|
|NCIm Browser 2.3||The 2.3 release has been deployed to production and looks like it working correctly. The QA smoke tests passed.|
Provided technical support to the Operations team on trouble-shooting a multiple CDISC Submission Values issue. The issue appears to be data related. The new data have a source prefix that is not recognizable by the report writer application.
JAVA 1.7 Upgrade
Reviewed the org.apache.cataline.ant package.
Reviewed Tomcat 7 manager-gui and the REST API for executing the corresponding administrative functions. (See http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Session_Statistics)
Added an admin user to the tomcat-users.xml configuration file with roles being defined as "manager, manager-gui, admin, manager-script".
Developed a method to launch the Tomcat 7 server.
Tested the deployment of a web application using the Tomcat 7 DeployTask Ant task. This task takes a path parameter and a war file as input. It will automatically drop the war file to the webapp directory and create a subfolder under webapp directory to hold the expanded war. It will also create a corresponding subdirectory under the work directory.
Tested the undeployment of an active web application using the Tomcat 7 UnDeployTask Ant task. This task takes a path parameter as input; for example, “/ncitbrowser”. It will automatically remove the war file and the expanded folder from the webapp directory. It will also clean up the subdirectory in the work folder. Both DeployTask and UnDeployTask will be reused in the new BDALite application.
|Interim 2.4 release for the NCBO widget upgrade||TBD||There has been a change in the plans for the 2.4 release of the Term Browser due to the need to upgrade the NCBO graph widget which was scheduled to be retired at the end of January. We have been able to get this extended but need to do a limited release before the fully implemented features of the planned 2.4 release.|
|Area of Interest||Details|
|Term Browser 2.3 Release||Provide required support for deployment to Prod tier.|
|Term Browser 2.4 Release||Continue design activities for new feature requests|
|Term Suggestion Application Release||Make any required fixes from QA testing.|
|NCIm Browser 2.3 Release|
Provide required support for deployment to Prod tier.
|NCIm Browser 2.4 Release||Continue design activities for new feature requests.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|6/19/13||11/27/13||Term Browser 2.3 and LexEVS 6.1 are in parallel development with the Term Browser having a dependency on LexEVS release. Both have a hard deployment date of 9/30/2013. Anticipating some QA resource limitations with both schedules being in parallel.||M||Jason||Monitoring both schedules and will provide status to QA to make sure resources are available.|
|01/08/14||VPN access to the NIH network is going to be locked down to just GFE equipment. This could cause some problems with response time to issue after normal working hours.||We will work with the TPM on a mitigation strategy to include possibly getting a GFE laptop.|
|7/17/2013||Removal of JAVA 1.6 from desktops. The Term Browser deployments using AntHillPro require JAVA 1.6. Putting in a request for a waiver until we can upgrade.||This would affect the deployments and production environment for the EVS tools. It sounds like this is going to be a future issue but we should have time to upgrade before it is part of the CBIIT tech stack.||Provided a level of effort for migrating all of the EVS applications to Java 1.7 to the Technical Project Manager and government sponsor.|
|7/31/2013||We currently have an issue where the browsers are ready to move to the QA tier for testing but due to the dependency of LexEVS 6.1 cannot start the QA testing process. LexEVS 6.1 does not currently have all the pre-QA qualification to proceed with the deployment to the QA tier.||With a hard deadline of Sept. 30 for both the browsers and LexEVS API 6.1 there is concern that there will be time to finish all the testing and deployments on time.||This is closed. The hard deadline was expanded due to factors we cannot control.|