Skip to content
mkalam-alami edited this page Oct 7, 2011 · 12 revisions

Prerequisites

The only prerequisite for running the demo (for contributing, see Development-Environment) is Java JDK 6 (use the one from Sun). You'll need to set your JAVA_HOME variable to your Java install directory.

Get the archive on our website, and unzip it. You can then use the start script run.sh or run.bat to launch all EasySOA servers.

Configuration

  • At first launch, you might be asked to configure Nuxeo using the online wizard. When you're asked, select "embedded database".
  • As explained in the welcome page, you will need to configure your browser to use our proxy, like this:

Running the demo

If you meet any issue while using the demo, see below the Troubleshooting section.

Restarting the demo

  • To reset the whole demo, delete old & unwanted services in Nuxeo and restart the run script.
  • To restart Nuxeo manually, click on Stop in the Launch user interface or launch bin\Stop Nuxeo.bat, check it is stopped in the windows Task Manager, then click on Start or launch bin\Start Nuxeo.bat

Troubleshooting

Here are the most frequent problems you can get while using the demo (remember that it's just a demo!). If your problem is not here, you can create an issue.

Discovery by browsing

The web proxy seems not to be used
  • If it seems the browser doesn't use the web proxy, check the configuration for proxy exclusions, ex. 'localhost, 127.0.0.1': you need to remove all of these.

Service registry

Nuxeo doesn't restart at the end of the wizard

Restart manually after setting in bin/nuxeo.conf the property: nuxeo.wizard.done=true

The dashboard values aren't up to date
  • Unfortunately, we met indeed some caching problems with the services dashboard. You can try restarting Nuxeo to refresh the cache.

SCA import

My application doesn't appear
  • Try logging out and in again, it's probably a caching problem.

EasySOA Light

When using a service, I get an "Error code 0"
  • Something has not been properly launched, probably because a server wasn't ready yet before to start the next one (your computer was slower than expected!). Take a look at the log files to see which server failed, and launch it manually (each server has a start-xxx.sh and .bat script).
Clone this wiki locally