Sub-Term Mapping Tools

Deploy to NLM internal users

  • Install to ${PROJECTS} (use previous LVG installed option).
  • Create ${PROJECTS}/STMT/stmtData.${YEAR}
    • data.${YEAR}AA
    • data.${YEAR}AB
      • link HSqlDb
      • link tables
      • Copy Config from previous year
        • Update ${YEAR} (from ${PREV_YEAR}) in lsf.properties
        • Update ${YEAR} (from ${PREV_YEAR}) in smt.properties
        • Update ${YEAR} (from ${PREV_YEAR}) in stmt.properties
      • mkdir ./Lvg
        • update ./Lvg/lvg${YEAR}lite.tgz
          => copy from ${BACKUP_DIR}/Releases/LVG//${YEAR}/lvg${YEAR}lite.tgz
        • gtar -xzvf lvg${YEAR}lite.tgz

        after 2023, LVG uses HSqlDb.2.7.0-jdk8, which conflicts with STMT use HSqlDb 2.3.2. So, the latest Lvg should be used is lvg.2022. Accordingly, just link lvg to ../../stmtData.2022/data.2022AA/Lvg
        =>This is also done in the above 3 config files.
  • link ${PROJECTS}/STMT/stmt2015/data.${YEAR}.AA/AB
  • update the link of ${PROJECTS}/STMT/stmt2015/data
    shell> link ./data.${YEAR}.AA data
    shell> link ./data.${YEAR}.AB data

  • create ${PROJECTS}/STMT/stmt2015/bin/smt.${YEAR}AA
    • Test!!
      shell> smt.${YEAR}AA -h
      shell> smt.${YEAR}AA -ci

  • create ${PROJECTS}/STMT/stmt2015/bin/lsf.${YEAR}

  • create ${PROJECTS}/STMT/bin/stmt2015/stmt.${YEAR}

  • Update program in /nfsvol/lex/Lu/LSG/bin/
    • smt${YEAR}AA
    • lsf${YEAR}
    • stmt${YEAR}