Page History
Building and Installing using Jenkins
- A new release will be tagged in the github project https://github.com/ncievs/nci-protege5.git
- Navigate to Jenkins at https://evs-jenkins.nci.nih.gov/jenkins/job/_default/job/_lower/job/_Protege/
- Choose protege_build > Build with Parameters and select the appropriate tag in the BRANCH_OR_TAG selection box and click Build
- Review the Console Output for any errors
- For Dev, choose protege_deploy_dev > Build with Parameters. You should be presented with the same tag. Click Build
- Review the Console Output for any errors
- Check the protege dev server and see that the /local/content/protege/protege-server and protege-desktop have been updated
- Confirm the service has started by checking /local/content/protege/logs/protserv-console.txt for "Admin server has started at port 9091"
Manual Build
Building a new Protege version on Dev using Ant
- A new release will be tagged in the github project https://github.com/ncievs/nci-protegeprotege5.git
- Clone the new release into your local build directory.a new directory in /local/project. "git clone https://github.com/ncievs/nci-protege5.git nci-protege-V<tag>"
- The clone will create a directory "nci-protege5". Enter into the scripts subdirectory "cd nci-protege5protege-V<tag>/scripts/"
- Run the build script, passing in the version number "./build.sh versionTag <tag> ncievs >> build.log".
- Review the output for errors or build failures: "cat build.log | grep FAILURE"
- 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
- pellet
- protege
- protege-client
- protege-server
- run-protege.sh
- run-server.sh
Installing the server build
- Navigate to the running instance of protege, likely in on Dev this is /local/content/protege/scripts/Shutdown the explanation server: “./pellet server --config /local/content/protege/protegedata/configdata/server.properties stop"
- Shutdown the protege server: "./shutdown.sh"
- Archive the previous version of the services, which are these 3 directories2 directories in /local/content/protege:
- explanationserver
- protegeserver
- protegedesktop
- 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"
- Copy the new protegedesktop into the empty desktop directory "cp -r Untar the explanationserver tarball to the server folder
- Unpack "tar -xf <build-location>/nci-protege5/scripts/nci-protege5/pellet/distribution/target/*.gz /local/content/protege/pellet-2.4.0-SNAPSHOT" rename "mv pellet-2.4.0-SNAPSHOT explanationserver
Create a new explanationserver directory "mkdir explanationserver"
"
- Remove previously compiled reasonings from the protegedata/pelletdata folder "rm -rf /local/content/protege/protegedata/pelletdata/*"
- From the /local/content/protege/scripts directory start the protege server: "./run-background.sh". The server should start almost immediately
- Confirm the service has started by checking /local/content/protege/logs/protserv-console.txt for "Admin server has started at port 9091"Start the explanation server “./pellet server --config /local/content/protege/protegedata/configdata/server.properties start". The service can take half an hour or more to start.
- Confirm the service has started by checking /local/content/protege/logs/pellet-console.txt for "Listening at: https://<server>.nci.nih.gov:18080"
<build-location>/nci-protege5/scripts/nci-protege5/protege/protege-desktop/target/protege-5.1.1<version>-SNAPSHOT-platform-independent/Protege-5.1.1<version>-SNAPSHOT /local/content/protege/protegedesktop"
Shutdown/Startup of Services
...
Shutdown
- Navigate to /local/content/protege/scripts/
- To shutdown the protegeserver: "./shutdown.sh" To shutdown the explanation server: “./pellet server --config /local/content/protege/protegedata/configdata/server.properties stop"
Startup
- Navigate to /local/content/protege/scripts/
- To startup protege server: "./run-background.sh"
- Do "tail ../logs/protserv-console.txt" to check that the protege server is running.
- To startup explanation server: “./pellet server --config /local/content/protege/protegedata/configdata/server.properties start"
- Do "tail ../logs/pellet-console.txt" to check that the explanation server is running.
Packaging Server for Deployment to Upper Tier
- Navigate to /tmp/protege and remove any files and folders there
- Copy up server directory - cp -R /local/content/protege/protegeserver .
- Copy up explanation server - cp -R /local/content/protege/explanationserver .
- Package into tarball with version number - tar -cvzf protege-server-deployment-1.00v.tar.gz explanationserver protegeserver
- Copy tarball to /priv-file-repo/protege/deployment
- Move any previous versions to /priv-file-repo/protege/archive/deployment-package
Packaging Client for Deployment
- Navigate to /local/project/protegeClientPackage
- Remove and previous zip files and client directories but leave java and the run scripts
- Create directory nci-protege5_V2.1.00v
- Copy in the desktop client "cp r /local/content/protege/protegedesktop/* ./nci-protege5_V2.1.00v"
- Copy the jre and run scripts into the new directory
cp -r ./jre1.8.0_102 ./nci-protege5_V2.1.00v/
cp run.* ./nci-protege5_V2.1.00v/
Create a zip "zip -r nci-protege5_V2.1.00v.zip nci-protege5_V2.1.00v"
Copy the zip to your local machine, unzip and test
Put zip on sFTP under evs/Protege/Protege-2.0
Deployment
- Server is started when you see "Admin server has started at port 9091"
- Unzip the protege package in your chosed directory
- Run the bat or sh file
- Do NOT immediate accept download of plugins.
- Go to Launcher/Preferences then the plugins tab. Make sure you are pointed to the correct plugins location.
- Go to File/Check for plugins and select all plugins
- Restart protege
- Set up Lucene - Go to File/Preferences and choose Lucene as in tne General tab
- Set up Pellet - Go to File/Preferences, the Reasoner tab and the Pellet sub-tab.
- Select Remote as the reasoner type
- Enter the server address for pellet
- Optional - restart Protege
- Choose File Open from Protege Server. Enter the credentials and wait.
- Profit