Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: Launching Service Registry"
(→Prerequisites) |
(→Prerequisites) |
||
| Line 7: | Line 7: | ||
*[[Swordfish_Documentation:_Running_Target_Platform|Running Target Platform]] - to set up Target platform from local machine | *[[Swordfish_Documentation:_Running_Target_Platform|Running Target Platform]] - to set up Target platform from local machine | ||
*[[Swordfish_Documentation:_Setting_Up_Registry_From_Galileo_Update_Site|Setting Up Registry From the Galileo Update Site]] - to set up target platform from Update Site. | *[[Swordfish_Documentation:_Setting_Up_Registry_From_Galileo_Update_Site|Setting Up Registry From the Galileo Update Site]] - to set up target platform from Update Site. | ||
| + | |||
| + | == Local and remote service resolvers == | ||
| + | Swordfish uses service resolvers retrieve service description (wsdl and agreed policy). Currently Swordfish supports local and remote resolvers: | ||
| + | * <b>org.eclipse.swordfish.plugins.resolver.backend.remote</b> - remote resolver communicate with remote Swordfish registry using REST http calls. | ||
| + | * <b>org.eclipse.swordfish.plugins.resolver.backend.local</b> - local resolver not executes remote calls and retrieves service descriptions for local folder. By default this is org.eclipse.swordfish.plugins.resolver.backend.local\src\main\resources\wsdl folder. | ||
==Launching Service Registry== | ==Launching Service Registry== | ||
Revision as of 06:53, 19 June 2009
Prerequisites
Eclipse Galileo M7 build or later. The examples described here are based on Eclipse Galileo M7.
This "How To" assumes that user have downloaded and activated Swordfish Target Platform with Swordfish Runtime (core) bundles and Swordfish Registry bundles included. Follow steps from:
- Running Target Platform - to set up Target platform from local machine
- Setting Up Registry From the Galileo Update Site - to set up target platform from Update Site.
Local and remote service resolvers
Swordfish uses service resolvers retrieve service description (wsdl and agreed policy). Currently Swordfish supports local and remote resolvers:
- org.eclipse.swordfish.plugins.resolver.backend.remote - remote resolver communicate with remote Swordfish registry using REST http calls.
- org.eclipse.swordfish.plugins.resolver.backend.local - local resolver not executes remote calls and retrieves service descriptions for local folder. By default this is org.eclipse.swordfish.plugins.resolver.backend.local\src\main\resources\wsdl folder.
Launching Service Registry
Service Registry JAR files are built together with the Swordfish Runtime JAR files.
To launch the Service Registry JAR files, specify the following environment variables:
- org.osgi.service.http.port - port for HTTP interface to SR
- org.eclipse.swordfish.registry.fileLocation - a path to the directory where SR will store WSDL files
You can specify value of these environment variables, using -D parameters when you are launching equinox.
Here is an example script that shows you how to launch it:
#!/bin/bash cd ./target/bundles java -Dorg.osgi.service.http.port=8080 \ -Dorg.eclipse.swordfish.registry.fileLocation=/tmp/swordfish-sr \ org.eclipse.osgi_3.5.0.v20090311-1300.jar -console -clean
The option -console starts equinox in the console mode. In this mode you can type commands. When the option-clean is used, equinox will clean up the caches before starting up.