 |
Page History
...
- Create a method over the Graph API that allows a CodedNodeSet to be passed as a parameter along with an Enumeration value indicating direction, a value for the depth of the resolution, and one or more associations. Return a List of Minimally populated ResolvedConceptReferences.
Constraints:
- Will not require current RMI users to update their client jar
- Features:
- Will provide a loader for the graph database
- Will provide instructions on the use of the loader, including any dependencies on existing services
Architecture – can include a line that says this will be specified at a later date, if not ready:
- Specify which Graph DB will need to be installed on which tiers
- Specify any other services that need to be installed on which tiers
...
The loader requires a local install of Arangodb along with a configuration of LexEVS where lbconfig.props is updated with connection parameters. Instructions for loader use will be supplied in the usual loader documentation section of the Wiki
Loader use is documented here:
Loading the Graph Database into ArangoDb for a Given Terminology
4. Architecture
We will work with the Systems team to get the most optimal installation of Arangodb for each tier.
Each tier will also need to have a tomcat instance with the graph-resolve installed to produce REST services for the Graph Resolution API. We'll provide the usual configuration parameters for the REST service that are normally defined for deployment tracks on Jenkins and/or PTE documents.
...
9 - Installing the Graph Node Resolution REST Service
5. Migration
Proposal Sign off
| Federal Sponsor(s) | Signature |
|---|---|
| Lyubov Remennik | via email |
| Sherri De Coronado | SDC |
| User(s) | Signature |
|---|---|
| Kim Ong | via email |
| NCI System Architect | Signature |
|---|---|
| Tracy Safran | approved during arch meeting 2020.01.14 |
LexEVS Rest Service API
List of terminologies
...
