Installation and Setup V3 (2021 versions)

prerequisites

• docker
• minikube (optional)

release files

• Let delivery-V3.zip be the current distribution.
• unzip it to a directory, called V3 in the following.

To ease the deployment process the pure jetty as well as the docker-related files are contained in the distribution.

pure Jetty (angular navigator frontend (ang-navi) not supported)

• unzip V3/docker-build-dir-jetty/cts2le/WebCts2LE-embedded-jetty.zip to a directory (denoted by W in the following)

• go to directory W

• run ./bin/startup.sh -port <port>

• shutdown command: ./bin/shutdown.sh <port>

docker

• go to directory V3/docker-build-dir-jetty

• adapt the url used by the angular navigator frontend (ang-navi) to access the backend in file cts2le-navi.env (property <CTS2LE_SERVER>).
  !!! <CTS2LE_SERVER> is exactly the url of the container/service cts2le (see compose file), externally reachable

• run sudo docker-compose -f docker-compose.yml up -d --build (stretch version)
  (use docker-compose-net-host.yml in environments where no docker net is allowed)
  (use docker-compose-standalone.yml for standalone version)

• check container with sudo docker logs -f cts2le
  (last line ... INFO:oejs.Server:main: Started ...)

• ang-navi: get the service url U of the frontend (hint: execute docker ps -a ) and check it in a browser with U/CTS2LE

kubernetes

• ensure that all docker images are generated according to above section.

• go to directory V3/docker-build-dir-jetty/kubernetes
  (all kubernetes yaml files are located at directory yaml)

• backend

  • apply modifications for your environment (e.g. targetPorts in service definitions or storage requirements in persistent volume claims)

  • execute ./setup-kube-cts2le.sh
    (all resources for the backend are created in kubernetes. To create single resources comment out the others)

• ang-navi

  • adapt the url used by the angular navigator frontend (ang-navi) to access the backend in file yaml/cts2le-navi-env-configmap.yaml (property <CTS2LE_SERVER>).
    !!! <CTS2LE_SERVER> is exactly the url of the container/service cts2le (hint: in minikube execute minikube service cts2le --url ), externally reachable
  • execute ./setup-kube-cts2le2-navi.sh
  • get the kubernetes service url U of the frontend (hint: in minikube execute minikube service cts2le-navi --url ) and check it in a browser with U/CTS2LE

load standard terminologies

• go to directory V3

• important prerequisite: the cts2le instance

  • must not contain the terminology to load
  • services cannot be accessed during load

• run java -jar cts2le-3-command-bulk.jar --sourceLoc SL --targetLoc <CTS2LE_SERVER>/WebCts2LE
  where SL is a directory of bulk files. Files in SL have to end with .nq.gz (to ignore a file, suffix it with e.g. .igno). For <CTS2LE_SERVER>/WebCts2LE see sections above, e.g. http://localhost:9090/WebCts2LE. Be aware that on a notebook (~2 GHz, 16 GB RAM) the load time will be around 20 min (standard terminologies excl. snomed). For possible errors consult sudo docker logs -f cts2le

• update the Lucene/Solr index by executing (http)

  • GET <CTS2LE_SERVER>/WebCts2LE/service/manage/index/update (estimated index time 50 min due to complex quad store queries) and subsequently
  • GET <CTS2LE_SERVER>/WebCts2LE/service/manage/index/suggester/update