Page tree
Skip to end of metadata
Go to start of metadata
  1. Create fresh termserver
  2. Prime with SNOMED CT International Release MySQL and Indexes
    For each MS Product repeat the following (using the example of Denmark (DK)
  3. Create a Branch if it does not exist:
    1. Use this endpoint https://dev-ms-authoring.ihtsdotools.org/snowowl/snomed-ct/v2/#!/branches/createBranch
      1. DK create branch with metadata: MS- Deployment create-Branch.json
      2. US create branch with metadata: MS-Deployment-US-create-branch.json
  4. Create an MS product in the code system registry
    1. Use this endpoint https://dev-ms-authoring.ihtsdotools.org/snowowl/admin/#!/code-system-metadata/createCodeSystem
      Code System Details for Int, DK, SE and US (input just one of DK, SE or US): MS-Deployment code-systems.json
  5. Set the branch metadata for the MS product (IF NOT SET When Creating the Branch as above else skip this step)
    1. Use this endpoint https://dev-ms-authoring.ihtsdotools.org/snowowl/snomed-ct/v2/#!/branches/updateBranch
      Example config: MS-Deployment branch-meta.json
  6. Import the latest MS release - REST
    1. The latest released RF2 archive should be imported onto the correct branch for that Code System.
      Create an import using this endpoint: https://dev-ms-authoring.ihtsdotools.org/snowowl/snomed-ct/v2/#!/imports/create
      Example config: MS-Deployment gistfile1.txt
    2. The response headers of the create import endpoint will contain the URL of the import entity. For example "https://dev-ms-authoring.ihtsdotools.org/snowowl/snomed-ct/v2/imports/479929bb-c043-4ef0-9f0b-d2be8ebc2cb6"
    3. Go to https://dev-ms-authoring.ihtsdotools.org/snowowl/snomed-ct/v2/#!/imports/startImport and using the UUID from the end of the URL (as shown in (b) above) upload the archive and start the import
    4. If the release file is large and your bandwidth poor you could try getting the zip file onto the target machine (e.. aws cp or wget) and then some thing like " curl -u Username:Password -X POST -F 'file=@/path/to/zipfile/SnomedRelease.zip' http://localhost:8080/snowowl/snomed-ct/v2/imports/479929bb-c043-4ef0-9f0b-d2be8ebc2cb6/archive "
    5. You may get a reponse of "413 Request Entity Too Large" from Nginx especially if trying to upload a large file. If so....  Edit /etc/nginx/conf.d/termserver.conf - find "location /snowowl" then within that find "client_max_body_size" and set to a larger number than the size of the file you are trying to upload. Save the termserver.conf. Then issue a "sudo service nginx reload" command and retry (c)
    6. Wait for the import to complete by checking the status of the import entity using the URL ending in a UUID (as shown in (b) above). This can take a while (e.g. a 70mb upload takes at least 1 & a 1/2 hours to import).
    7. Check you have the expected versions under that code system, e.g. https://dev-ms-authoring.ihtsdotools.org/snowowl/admin/codesystems/SNOMEDCT-DK/versions
  7. Import the latest MS release - OSGI Console. As an alternative to ( 6 ) one can use the osgi console
    1.  ssh into the target machine
    2.  make sure you have copied the release file to the target machine
    3. ssh to the local osgi console:  " ssh admin@localhost -p2502 " You will need to get the password from devops.
    4. You will need to make (or copy onto the target machine) a code system json file as per MS-Deployment code-systems.json
    5. sctimport rf2_release -t FULL -b {BRANCH_PATH} -v /{PATH_TO_BUNDLE}/SnomedCT_RF2Release_SE1000052_20160531_20160906-145102_fixed.zip /{PATH_TO_DESCRIPTOR}/example.json

  8. Import any work-in-progress for the next MS release
    1. This RF2 content should have an empty effectiveDate value
    2. Create an import using the branch path of the MS code system but set createVersions to false and type to DELTA
    3. Upload the archive
    4. Wait for import to finish
  • No labels