Skip to end of metadata
Go to start of metadata

UFrame VM Setup

San Diego developers can find the referenced downloadable files on our local Time Capsule (Data->images).

Install VirtualBox

Import the image

  • File, Import Appliance, Select the exported UFrame appliance (CENTOS.ova)
Import may take 20-30 minutes
  • Adjust VM settings to something appropriate for your hardware (HD at least 50GB, memory, num CPUs, etc)
  • Update the shared folder (if you want to share files between the host OS and VM OS)
    • Under VirtualBox->Preferences, select the Network tab and add a new network in the Host-only Networks
    • Select CENTOS and click Settings. Under Shared Folders, add a shared folder on your local machine (remove the old folder)
    • Shared folder will auto-mount to the VM as /media/sf_<shared folder name>
  • Boot the VM
  • Log in as "race"

Download files

Import java files into eclipse

Download ooi_repo_2014-09-12_13-15-37.tar.gz to your VM box

Can delete old ooi_src directory to free up space in the VM.

rm -rf ~/ooi_src

Untar ooi_repo_2014-09-12_13-15-37.tar.gz to your working directory

tar -xvf ooi_repo_2014-09-12_13-15-37.tar.gz

Open eclipse and follow setup instructions on https://rsvpn.raytheon.com/redmine/projects/ooi/wiki/,DanaInfo=ooicm.omaha.us.ray.com+Developer_Setup, performing the steps for the following sections:

Import Projects into Eclipse

Deploy Edex

Deploy Extras

*must be VPN into the RTN network

*highly recommend creating workingsets for each import for ease of use

  • In Package Explorer window, Open "View Menu" (Downward Arrow), Select Top Level Elements > Working Sets.
  • Open "View Menu" (Downward Arrow), Select Configure Working Sets..

Import Projects into Eclipse

Make a new workspace:

  • Import all of the projects from the following directories into the workspace:** build** common** edex
    • features
    • foss
    • util
    • submodules/AWIPS2_baseline/edexOsgi
    • submodules/AWIPS2_baseline/ncep/gov.nasa.gsfc.fits
    • submodules/AWIPS2_foss
    • submodules/ogc
    • submodules/ufcore/common
    • submodules/ufcore/edex
    • submodules/ufcore/features
    • submodules/ufcore-foss 
  • Close the following projects** com.raytheon.edex.plugin.binligtning** com.raytheon.edex.rpgenvdata** com.raytheon.uf.common.dataplugin.ffmp
    • com.raytheon.uf.edex.plugin.ffmp

Set API baseline error reporting

  1. Click on 'Window->Preferences'
  2. Expand 'Plug-in Development'
  3. Click on 'API Baselines'
  4. Change 'Missing API baseline' option from 'Error' to 'Ignore'
  5. Click 'Apply'

Set JDK

  1. Go to Preferences ('Window->Preferences')
  2. Expand 'Java'
  3. Click on 'Installed JREs'
  4. Click 'Add...'
  5. Select 'Standard VM' and click 'Next'
  6. Click 'Directory...' next to JRE home and browse to uframe java ($HOME/uframes/ooi/uframe-1.0/java)
  7. Name the JRE 'uframe' and click 'Finish'
  8. Uncheck the system java and check the uframe JRE and click 'OK'

Set up target platform location to run CAVE (one-time-only)

  1. In Eclipse, select Window -> Preferences.
  2. Expand Plug-in Development.
  3. Select Target Platform.
  4. Select Running Platform (Active).
  5. Click Edit.
  6. Highlight the location and click Edit again.
  7. Change location to the Eclipse 3.8 instance
  8. Press Finish
  9. Select "Show location content" near the bottom
  10. Ensure the path is valid and that plug-ins are detected.
  11. Click Finish.
  12. Click OK.

https://rsvpn.raytheon.com/redmine/projects/ooi/wiki/Developer_Setup/,DanaInfo=ooicm.omaha.us.ray.com+edit?section=9

Deploy Edex

  1. Ctrl-Shift-R, deploy-install.xml
  2. Double click on the build.deploy one
  3. Run As
  4. Enter the following as deploy arguments:## Change the paths as appropriate for your chosen installation location

Deploy Extras

This deploys changes to the edex-server script and the python libraries, for the time being this is an extra step over the normal deploy above.

  1. Open the deploy.xml file from race.addons
  2. Right click and "Run As -> External Tools Configuration..."
  3. Click the new build icon in the top left ( white paper with yellow star )
  4. Enter the following as deploy arguments
  5. Change the edex path as appropriate for your chosen installation location## Change the python path as appropriate for the location of your git clone

Update LINUX environment

Start EDEX

Run the following two steps if updates were made to .xml or .yml files (or if it is your first time running EDEX)

  • In eclipse, run race.addons/deploy.xml
  • In eclipse, run build.deploy/deploy-install.xml
  • cd ~/uframes/ooi
  • bin/edex-server all start

Ensure EDEX is operational

  • grep "EDEX ESB is now operational" ./uframe-1.0/edex/logs/edex-ooi-$(date +"%Y%m%d").log

Purge existing data

  • bin/edex-server purgeall
  • y

Purge existing database

Copy test data into OPTAA ingest folder

  • cp ~/ooi/edex/com.raytheon.uf.edex.ooi.decoder.dataset/utility/edex_static/base/ooi/parsers/mi-dataset/mi/dataset/driver/optaa_ac/mmp_cds/resource/acs_archive.mpk ~/uframes/ooi/uframe-1.0/edex/data/ooi/optaa

Verify log file indicates data ingested

  • Verify log file reports no errors
    • cd ~/uframes/ooi
    • view ./uframe-1.0/edex/logs/edex-ooi-$(date +"%Y%m%d").log

Verify data ingested

  • Data file should disappear from the optaa ingest folder within ~5 secs
  • Verify data in postgres
    • cd ~/uframes/ooi
    • source bin/edex-server
    • psql metadata awips
      • metadata=# select * from sensorreading;
  • Verify data in HDF5
    • h5dump ./uframe-1.0/edex/data/hdf5/sensorreading/sensorreading-2013-11-24-00.h5 | more

Fix python

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.