Demo v0.1 Doc - easysoa/EasySOA GitHub Wiki
Here are all the steps required to run the "May Demo".
NB. TODOs are potential improvements, OKs are done improvements, FAQs have to go in the FAQ.
Installing from the prepackaged VM
- Install Virtual Box
- Get the prepackaged demo VM
- Run it on VirtualBox
- Start it, see below
Installing from the archive
Install prerequisites for running the demo (for contributing, see Development-Environment) :
- Java JDK 6
- node.js (Use version 0.4.5 or upper, it's recommended to get it by downloading the archive on the website: http://nodejs.org/)
Get the archive (or build it, see dev. env.), and untar it. Then configure the browser to use the web proxy as proxy :
Start/restart the demo :
- Using the start script
run.sh
orrun.bat
(which launches: webserver, web proxy ; Nuxeo, service proxy ; Pure Air Flowers demo web service) - The demo root is at http://127.0.0.1:8083 (the start script should open a web page, else go there)
- The root page contains link to all applications. FYI, Nuxeo is at http://127.0.0.1:8080/nuxeo, the Discovery Client at http://127.0.0.1:8083/client, the Service Scaffolder at http://127.0.0.1:8080/easysoa/light.html
To reset the demo, delete old & unwanted services in Nuxeo, empty your browser cache and restart the demo.
During your first time launch, you might need to configure Nuxeo using the online wizard. When you're asked, select "embedded database".
Running the demo scenario
- To get authentication, connect to Nuxeo at http://127.0.0.1:8080 (Administrator/Administrator) TODO SSO
- From the demo root at http://127.0.0.1:8083, go to the Discovery Client page
- There click on the mock intranet home page, and then on the Services page :
- Due to a cache problem, you might need to force reload the Services page after having opened it in a dedicated tab (http://127.0.0.1:8083/services.html)
- The service's descriptor should be detected and shown on the left of the Client.
- Select it, change the extracted metadata above, and click on "save" to put it in Nuxeo.
- From the demo root, go in Nuxeo and from there in the "services" folder, the registered service should be there. (if you were on the page before the upload, refresh the folder by clicking on the appropriate icon)
- Click on the service : it shows business metadata, and is linked to its descriptor
- From there, click on the "call it" button : it goes to the Service Scaffolder
- In the Service Scaffolder, enter a value in the input field and click submit : the response comes back
- Now click quickly several times on the submit button :
- after a few times, it should show an error,
- because the service proxy layer is configured with a "fuse" behaviour protecting from too much use.
FAQ
Web proxy
- 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.
Nuxeo
- 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
- If Nuxeo doesn't restart at the end of the wizard, restart manually after setting in bin/nuxeo.conf the property: nuxeo.wizard.done=true
node.js : if DNS error (in npm, proxy...)
such as
Error: ECONNREFUSED, Could not contact DNS servers
at IOWatcher.callback (dns.js:74:15)
solution :
-
offline, use 127.0.0.1 rather than localhost
-
and online, add (google) nameservers in /etc/resolv.conf :
nameserver 8.8.8.8
nameserver 8.8.4.4 -
see also https://github.com/isaacs/npm/issues/79 https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-%28Windows%29
Demo improvements
(mdu win) "error downloading wsdl" -> OK patched by mka
(mdu win) FAQ node.js offline dns :
- replace localhost by 127.0.0.1 (and when filtering the proxy's own messages) -> OK 20110520 patched by mdu
- TODO replace localhost by 127.0.0.1 in proxied message ??
- TODO proxy existing proxies ?!
(mdu win) FAQ node.js module relative path :
- pb : doesn't find custom modules
- solution : use launch scripts (rather than require webserver/ or proxyserver/ ) OK patched by mdu
TODO PAF intranet cache :
- alt HTTP header nok because if in cache non request
- alt using HTML META but nok if alread in cache http://127.0.0.1:8083/intranet/img/bann.jpg http://www.commentcamarche.net/forum/affich-28946-gestion-du-cache-du-navigateur
- alt additional button in client to specify pages to reload with "another" url i.e. by proxypassing it in the server, or even auto every 1s BUT also requires HTML changes