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

Automated build using Jenkins

This only works once the project has been checked into the NCIEVS repository

  1. Navigate to https://evs-jenkins.nci.nih.gov/jenkins/job/_default/job/_lower/job/_Protege/
  2. Choose protege_build
  3. On the left side, select "Build With Parameters"
  4. Select the tag to be built from the "BUILD_OR_TAG" option list and click the "Build" button
  5. Wait until the build is complete
  6. If the build is successful, got back to https://evs-jenkins.nci.nih.gov/jenkins/job/_default/job/_lower/job/_Protege/
  7. Choose protege_deploy_dev (or protege_deploy_qa if applicable)
  8. Select "Build With Parameters"
  9. The version you selected in step 4 should automatically be populated in the "BUILD_OR_TAG" option list. Click the "Build" button
  10. Wait until the build is complete

Manually building a new Protege version on Dev

This step should only need to be performed during early snapshots, before code is checked into the NCIEVS source repository.

  1. You will be notified of the new build number.  For example: nci-1.00v
  2. On the dev machine go to /local/project and create a directory "mkdir nciedittab-dev-1.00v"
  3. Enter the directory and checkout the project from git "git clone https://github.com/ncievs/nci-protege5.git"
  4. The clone will create a directory "nci-protege5".   Enter into the scripts subdirectory "cd nci-protege5/scripts/"
  5. Run the build script, passing in the version number "./build.sh nci-1.00v ncievs".  Occasionally we may need to build from another server.  The developer should notify when this is necessary.
  6. Review the output for errors or build failures.
  7. Navigate to /local/content/protege/
  8. Move the protegeserver directory to a backup and create an empty folder in its place
    1. Delete any previous protegeserver-bak, if present. "rm protegeserver-bak"
    2. "mv protegeserver protegeserver-bak"
    3. "mkdir protegeserver"
  9. Repeat the backup step for protegedesktop
  10. Copy the new protegeserver into the empty server directory "cp -r /local/project/nciedittab-<version>/nci-protege5/scripts/nci-protege5/protege-server/target/server-distribution/server/* ./protegeserver/"
  11. Copy the new protegedesktop into the empty desktop directory "cp -r 

    /local/project/nciedittab-<version>/nci-protege5/scripts/nci-protege5/protege/protege-desktop/target/protege-5.1.1-SNAPSHOT-platform-independent/Protege-5.1.1-SNAPSHOT/* ./protegedesktop"

Shutdown/Startup of Services

The main server and explanation services are part of a single application. The server is controlled by scripts in the protege/scripts directory

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.

Packaging Server for Deployment to Upper Tier

  1. Navigate to /tmp/protege and remove any files and folders there
  2. Copy up server directory -  cp -R /local/content/protege/protegeserver .
  3. Package into tarball with version number - tar -cvzf protege-server-deployment-<version>.tar.gz protegeserver
  4.  Copy tarball to /priv-file-repo/protege/deployment
  5. Move any previous versions to /priv-file-repo/protege/archive/deployment-package

Packaging Client for Deployment

There is a script called package.sh that will perform all of the below.  You pass in the version of the protege build number as a parameter "./package.sh <version>"

  1. Navigate to /local/project/protegeClientPackage
  2. Remove any previous zip files and version directories but leave everything else.
    1. i.e. remove nci-protege5_V<previous> and nci-protege5_V<previous>.zip
  3. Create directory nci-protege5_V<current>
  4. Copy in the desktop client "cp r /local/content/protege/protegedesktop/* ./nci-protege5_V<current>"
  5. Copy the jre and run scripts into the new directory
    1. cp -r ./jre<version> ./nci-protege5_V<current>/

    2. cp run.* ./nci-protege5_V<current>/

    3. cp removeOldPlugins.bat ./nci-protege5_V<current>/

    4. cp -rf bookmark ./nci-protege5_V<current>/

    5. cp .fileprefs ./nci-protege5_V<current>/

  6. Create a zip "zip -r nci-protege5_V<current>.zip nci-protege5_V<current>"

Deployment

The .fileprefs copied into the package should have most of the below configured.  Plugins will likely need to be updated (Step 3). 

  1. Unzip the protege package in your chosen directory
  2. Run the bat or sh file
  3. Do NOT immediately accept download of plugins.  
    1. Go to Launcher/Preferences then the plugins tab.  Make sure you are pointed to the correct plugins location.
    2. Go to File/Check for plugins and select all plugins
    3. Restart protege
  4. Set up Lucene - Go to File/Preferences and choose Lucene in the General tab
  5. Set up Pellet - Go to File/Preferences, the Reasoner tab and the Pellet sub-tab.  
    1. Select Remote as the reasoner type
    2. Enter the server address for pellet
  6. Optional - restart Protege
  7. Choose "File Open from Protege Server".  Enter the credentials and wait.
  8. Once open, go to Lucene tab and wait for it to index.
  9. Once indexing done go to Reasoner on the menu and select "Pellet" as the reasoner.
  10. Under Reasoner on the menu select "Start Reasoner"
  • No labels