Edge Server Development Environment

From RifidiWiki

Jump to: navigation, search

This document details the steps necessary to set up a development environment in order to either develop a custom Rifidi Edge Server application, or modify an existing Edge Server bundle.

Configuring eclipse environment

  1. Download and install version 1.7 or greater (32 bit only) of the Java SE Development Kit (JDK) for your OS.
  2. Download the latest version of the Rifidi Edge Server SDK.
  3. Download the Juno release of Eclipse for RCP and RAP developers.
  4. Run eclipse and create a new workspace.
    Edgeserver dev screenshot1.png
  5. Unzip the Rifidi Edge Server SDK into the newly created workspace directory on your file system.
  6. In eclipse go to File->Import. Choose "Existing Projects into Workspace". Now select the SDK folder (which must reside in workspace directory).
    Edgeserver dev screenshot2.png

    Edgeserver dev screenshot3.png
    Edgeserver dev screenshot4.png
  7. Open up the target platform file (the file that ends in .target). Click the button that says "set as target platform" on the upper right-hand corner of the page.
    Edgeserver dev screenshot5.png
  8. Go to Run->Run Configurations. Open up the Edge Server OSGi run configuration (might be an item under "OSGi Framework"). Click Run. Note: The necesary bundles should be already checked by default. One can run the SS command at OSGI prompt to ensure necessary reader, Rifidi, Spring etc.. bundles have started
    Note: Please Do NOT uncheck bundles already checked by default in SDK
    Edgeserver dev screenshot6.png

Congratulations! You have successfully set up and configured your eclipse environment and are ready to develop an edge server application!

Note: If you are having trouble running a rifidi command, most likely the "org.rifidi.edge" bundle isn't started. Do an "ss" in the OSGI prompt and see if the org.rifidi.edge bundles have started correctly. If you don't see any org.rifidi.edge bundles, check your run config and make sure nothing is disabled. If you see them there but for some reason they arn't started, you can attempt to start them. Lets say that "org.rifidi.edge" is bundle "47". Type in "start 47" into your OSGI console to attempt to start that bundle. If it can't start, it should tell you why (most likely it requires another bundle). Keept trying to start bundles to see what is wrong, then you can probably adjust what is wrong in your run config. Also bear in mind that the "add required bundles" button (and the "validate bundles") button in the run config are your friends. They will help you fix your problems automatically.

Personal tools