NIH | National Cancer Institute | NCI Wiki  

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 7 Next »

Building a new Protege version on Dev

  1. A new release will be tagged in the github project https://github.com/ncievs/nci-protege.git
  2. Clone the new release into your local build directory.
  3. The clone will create a directory "nci-protege5".   Enter into the scripts subdirectory "cd nci-protege5/scripts/"
  4. Run the build script, passing in the version number "./build.sh versionTag ncievs >> build.log".
  5. Review the output for errors or build failures: "cat build.log | grep FAILURE"
  6. Check the structure of the build.  The following folders and files should be present under <build-location>/nci-protege5/scripts/nci-protege5
    • binaryowl
    • explanation-workbench
    • metaproject
    • nci-protege_<date>.tar.gz
    • nci-protege_<date>.zip
    • owlapi
    • protege
    • protege-server
    • run-protege.sh
    • run-server.sh

Installing the server build

  1. Navigate to the running instance of protege, on Dev this is /local/content/protege/scripts/
  2. Shutdown the protege server: "./shutdown.sh" 
  3. Archive the previous version of the services, which are these 2 directories in /local/content/protege:
    • protegeserver
    • protegedesktop
  4. Copy the new protegeserver into the service directory "cp -r <build-location>/nci-protege5/scripts/nci-protege5/protege-server/target/server-distribution/server /local/content/protege/protegeserver"
  5. Copy the new protegedesktop into the empty desktop directory "cp -r 

    <build-location>/nci-protege5/scripts/nci-protege5/protege/protege-desktop/target/protege-5.1.1-SNAPSHOT-platform-independent/Protege-5.1.1-SNAPSHOT /local/content/protege/protegedesktop"

  6. From the /local/content/protege/scripts directory start the protege server: "./run-background.sh".  The server should start almost immediately
  7. Confirm the service has started by checking /local/content/protege/logs/protserv-console.txt for "Admin server has started at port 9091"

Shutdown/Startup of Services

Shutdown

  1. Navigate to /local/content/protege/scripts/
  2. To shutdown the protegeserver: "./shutdown.sh" 

Startup

  1. Navigate to /local/content/protege/scripts/
  2. To startup protege server: "./run-background.sh"
  3. Do "tail ../logs/protserv-console.txt" to check that the protege server is running.
  4. Server is started when you see "Admin server has started at port 9091"

  • No labels