NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Contents of this Page

LexEVS 6.x Installation Links

LexEVS Service Clients to be Able to Consume HTTPS Enabled Services

  • All LexEVS 6.4 Services will only be available via HTTPS protocols.
  • These services will feature third party approved certificates.
  • RMI clients accessing the LexEVS services will need to be updated.

Services Affected:

  • LexEVS Remote API
  • LexEVS CTS2 Services
  • URI Resolver

Impact:

General

All Client references to HTTP URL's should be updated to HTTPS versions

LexEVS Remote API

  • LexEVS Remote (Also known as distributed) RMI clients will need to add the following jars to the class path to to support HTTPS updates for 6.4.1
    • lexevs-remote.client.6.4.1.jar
    • httpclient-3.1.0.jar

  • Combined with updating service URLs to any HTTPS services should allow processing of valid certificates and failure on self-signed or otherwise invalid certificates by RMI Clients.

CTS2 Service

  • Any REST Clients will need to adjust for the HTTPS service as needed. 
  • REST Clients using the CTS2 Framework client API should already be able to use the SSL services of an HTTPS service.

Other

  • The URI Resolver is not considered a public REST API, but it will be switching to HTTPS as well. 

Service Related Issues:

LexEVS HTTPS Setup

 

 

 

  • No labels