Objective
The 6.4 release presents a handful of significant changes to LexEVS. These changes will require the users of LexEVS 6.4.1 and earlier to migrate to a new client jar for the API, and possibly to adjust the way they query our REST services. These changes are:
- A service set wide update to the Java 8 code base from Java 7
- The removal of all legacy caCORE Data Services including QBE, Soap and REST services from the LexEVS Remote API
Migration Notes
End User API Migration
- lexbig.jar
- LexEVSSecurity.jar
- lexevsapi64-beans.jar
- lexevsapi64-framework.jar
- lexevsapi64-remote-core.jar
Maven Dependency Management
A LexEVS remote client project provides pom file based access to all supported client jars. Users of the pom in this project: https://github.com/lexevs/LexEVS_Distributed_Client.git can update versions of LexEVS and LexEVS remote client jar sets to 6.4.2.FINAL and 6.4.2 respectively.
<properties> <forkMode>never</forkMode> <lexevs.version>6.4.2.FINAL</lexevs.version> <cagrid.version>1.3</cagrid.version> <lexevs.remote.version>6.4.1</lexevs.remote.version> </properties>
End User REST / Data Service Migration
- A REST Call to LexEVS like https://lexevsapi6.nci.nih.gov/lexevsapi64/GetXML?query=org.LexGrid.concepts.Entity%5B@_entityCode=C29378%5D
- Will instead look like this: https://lexevscts2.nci.nih.gov/lexevscts2/codesystem/NCI_Thesaurus/entity/C29378?format=xml
- Or even https://lexevscts2.nci.nih.gov/lexevscts2/codesystem/NCI_Thesaurus/entity/C29378?format=json
Support
LexEVS will be maintaining dual servers for a period of time to allow people to migrate from earlier versions to 6.4.2. The date of the sunsetting of older versions has not been set and will depend on user feedback. If you have any concerns, questions or comments please contact us at:
Server-side changes
- CentOS 7
- MySQL 5.6