 |
Page History
...
The caCORE LexEVS Web services interface has a single end point called lexevsapi60Service, which is located at http://lexevsapi60.nci.nih.gov/lexevsapi60/services/lexevsapi60Service. Client applications should use this URL to invoke Web service methods.
| Warning | ||
|---|---|---|
| ||
Building a Java SOAP Client
...
| Info | ||
|---|---|---|
| ||
| Distributed LexEVS API |
Overview
In place of the existing EVS 3.2 object model, caCORE LexEVS is making a gradual transition toward a pure LexEVS back-end terminology server and exposure of the LexEVS Service object model. caCORE 3.2 and earlier required a custom API layer between external users of the system and the proprietary Apelon Terminology Server APIs. With the transition to LexEVS, caCORE LexEVS can publicly expose the open source terminology service API without requiring a custom API layer.
...
