Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
moteur2 [2011/07/28 17:05]
javier [Deployment of application services]
moteur2 [2012/11/16 16:26] (current)
blay [MOTEUR server]
Line 2: Line 2:
  
 MOTEUR2 is available as a pre-release (v0.9). MOTEUR2 is available as a pre-release (v0.9).
 +
 +===== Reference =====
 +
 +Tristan Glatard, Johan Montagnat, Diane Lingrand, Xavier Pennec. "​Flexible and efficient workflow deployement of data-intensive applications on grids with MOTEUR",​ International Journal of High Performance Computing Applications (IJHPCA), 22 (3), pages 347-360, 2008. [[http://​hal.archives-ouvertes.fr/​hal-00459130/​PDF|pdf]]
 +
 +
 +===== User Guidelines =====
 +
 +http://​proton.polytech.unice.fr/​doc/​user/​UserGuide.html ​
 +
 +https://​modalis.i3s.unice.fr/​softwares/​moteur/​guidelines
 ===== Downloads ===== ===== Downloads =====
  
Line 33: Line 44:
  
  
-The client is used for workflows design and execution monitoring. The server is used for workflow execution enactment. When starting a client, the graphical designer/​monitoring interface appears (unless the --no-gui option is used):+The client is used for workflows design and execution monitoring. The server is used for workflow execution enactment. When starting a client, the graphical designer/​monitoring interface appears (unless the no-gui option is used):
  
  
 <​code>​ <​code>​
- > java -jar moteur2-client-*-jar-with-dependencies.jar+> java -jar moteur2-client-*-jar-with-dependencies.jar
 </​code>​ </​code>​
  
Line 48: Line 59:
  
 <​code>​ <​code>​
- > java -jar moteur2-server-*-jar-with-dependencies.jar+> java -jar moteur2-server-*-jar-with-dependencies.jar
 </​code>​ </​code>​
  
  
-Use the ''​--help''​ option for detailed command line information.+Use the ''​help''​ option for detailed command line information.
  
-**Note:** To use the option of proxy certificates generation using key/​certificate you should use the [[http://​proton.polytech.unice.fr/​moteur2/​moteur2-client-0.9.14-dist.zip|moteur2-client.zip]] distribution because some [[http://​www.bouncycastle.org/​|Bouncy Castle]] depencencies requires signed jar files in the ''​CLASSPATH''​. Uncompress the ZIP file and execute the ''​moteur2.sh''​ under Unix/Mac environments or ''​moteur2.bat''​ under Windows environments. Alternatively experienced users can configure the Bouncy Castle provider in their environments registering it statically and then continue to use the [[http://​proton.polytech.unice.fr/​moteur2/​moteur2-client-0.9.14-jar-with-dependencies.jar|moteur2-client.jar]] distribution of Moteur. 
  
 +**Note:** To use the option of proxy certificates generation using key/​certificate you should choose the [[http://​proton.polytech.unice.fr/​moteur2/​moteur2-client-0.9.14-dist.zip|moteur2-client.zip]] distribution because some [[http://​www.bouncycastle.org/​|Bouncy Castle]] jars require to be signed in the ''​CLASSPATH''​. Uncompress the ZIP file and execute the ''​moteur2.sh''​ under Unix/Mac environments or ''​moteur2.bat''​ under Windows environments. Alternatively experienced users may configure the Bouncy Castle provider in their environments registering it statically and then continue to use the [[http://​proton.polytech.unice.fr/​moteur2/​moteur2-client-0.9.14-jar-with-dependencies.jar|moteur2-client.jar]] distribution.
 +
 +The provider can be configured as part of your environment via static registration by adding an entry to the java.security properties file (found in ''​$JAVA_HOME/​jre/​lib/​security/​java.security'',​ where ''​$JAVA_HOME''​ is the location of your JDK/JRE distribution). You'll find detailed instructions in the file but basically it comes down to adding a line:
 +<​code>​
 +security.provider.<​n>​=org.bouncycastle.jce.provider.BouncyCastleProvider
 +</​code>​
 +Where <n> is the preference you want the provider at (1 being the most prefered). Issues arise if the Sun provided providers are not first.
 +
 +Where you put the jar is up to mostly up to you, although the best (and in some cases only) place to have it is in ''​$JAVA_HOME/​jre/​lib/​ext''​. Under Windows there will normally be a JRE and a JDK install of Java if you think you have installed it correctly and it still doesn'​t work chances are you have added the provider to the installation not being used. [Source: [[http://​www.bouncycastle.org/​specifications.html|Bouncy Castle Specifications]] (see last part of section 5.1)]
  
 ===== Development ===== ===== Development =====
Line 61: Line 80:
   * [[https://​nyx.unice.fr/​projects/​moteur2|trac server]]   * [[https://​nyx.unice.fr/​projects/​moteur2|trac server]]
   * [[https://​nyx.unice.fr/​svn/​moteur2|SVN server]]   * [[https://​nyx.unice.fr/​svn/​moteur2|SVN server]]
-===== Deployment of application services ===== 
  
 +===== Deployment of application services =====
  
 The MOTEUR workflow engines support different kind of services: The MOTEUR workflow engines support different kind of services:
- 
- 
     * command-line tools wrapped with the jGASW wrapper and accessible as Web Services.     * command-line tools wrapped with the jGASW wrapper and accessible as Web Services.
     * regular Web Services     * regular Web Services
     * command-line tools wrapped with the GASW wrapper (executable on gLite, OAR/G5K and locally)     * command-line tools wrapped with the GASW wrapper (executable on gLite, OAR/G5K and locally)
     * local java code (beanshell)     * local java code (beanshell)
- 
  
 Pre-deployed Web Services (including jGASW-wrapped tools) hosted in an Axis2 or a Tomcat service container are browsable from the MOTEUR2 editor. Pre-deployed Web Services (including jGASW-wrapped tools) hosted in an Axis2 or a Tomcat service container are browsable from the MOTEUR2 editor.
- 
  
 The recommended method to deploy new command-line based application services is to use the jGASW wrapper tool (use the tool GUI to create and deploy the Web Service bundle) and host services in a Tomcat container. To do so, a Tomcat server with the metro Web Service software stack is needed. The recommended method to deploy new command-line based application services is to use the jGASW wrapper tool (use the tool GUI to create and deploy the Web Service bundle) and host services in a Tomcat container. To do so, a Tomcat server with the metro Web Service software stack is needed.
Line 80: Line 95:
  
 === Tomcat container installation === === Tomcat container installation ===
- 
  
     - Download Apache Tomcat version 6.x from [[http://​tomcat.apache.org/​download-60.cgi|here]] and declare ''​$CATALINA_HOME''​ environment variable     - Download Apache Tomcat version 6.x from [[http://​tomcat.apache.org/​download-60.cgi|here]] and declare ''​$CATALINA_HOME''​ environment variable
Line 93: Line 107:
     - Download jGASW UI jar archives from [[http://​proton.polytech.unice.fr/​jgasw|here]] ​     - Download jGASW UI jar archives from [[http://​proton.polytech.unice.fr/​jgasw|here]] ​
     - Run the service packaging interface with''​ java -jar jgasw-ui-%%*%%-bin.jar''​     - Run the service packaging interface with''​ java -jar jgasw-ui-%%*%%-bin.jar''​
-    - Tun the service deployment tool with ''​java -jar jgasw-tools-%%*%%-bin.jar''​+    - Run the service deployment tool with ''​java -jar jgasw-tools-%%*%%-bin.jar''​
  
 ==== Invoking Web Services from MOTEUR ==== ==== Invoking Web Services from MOTEUR ====
Line 100: Line 114:
   - Endpoints to services deployed: select the custom services list item in the list of repositories and use the ''​(+)''​ button to enter the URL of the service WSDL.   - Endpoints to services deployed: select the custom services list item in the list of repositories and use the ''​(+)''​ button to enter the URL of the service WSDL.
   - Listing containers content: MOTEUR2 is capable of browsing the content of AXIS2 server containers. Press the ''​(+)''​ button and enter the container URL. MOTEUR2 can also browse the content of Tomcat server containers if a specific discovery service is hosted within this server. The service discovery archive for Tomcat is available [[http://​proton.polytech.unice.fr/​moteur2/​TomcatDiscoveryService.war|here]]. Just copy this file in your ''​$CATALINA_HOME/​webapps''​ folder.   - Listing containers content: MOTEUR2 is capable of browsing the content of AXIS2 server containers. Press the ''​(+)''​ button and enter the container URL. MOTEUR2 can also browse the content of Tomcat server containers if a specific discovery service is hosted within this server. The service discovery archive for Tomcat is available [[http://​proton.polytech.unice.fr/​moteur2/​TomcatDiscoveryService.war|here]]. Just copy this file in your ''​$CATALINA_HOME/​webapps''​ folder.
 +
 +===== MOTEUR server =====
 +
 +MOTEUR server is a Web-Service used to start grid workflows executed with MOTEUR. It is developed in collaboration with the [[http://​amc-app1.amc.sara.nl/​twiki/​bin/​view/​EBioScience/​WebHome | eBioScience group]] of the Academic Medical Center Amsterdam) and [[http://​www.creatis.insa-lyon.fr | Creatis ]]. It is primarily meant to be used with the [[http://​www.vl-e.nl/​vbrowser| VBrowser ]] client as described in [[ http://​www.creatis.insa-lyon.fr/​site/​sites/​default/​files/​main.pdf | Olab-10]].
 +
 +Please find the current documentation here: http://​kingkong.grid.creatis.insa-lyon.fr:​9002/​projects/​vip/​wiki/​Wiki
 +
 +
 +{{:​softwares:​moteur:​rapport_tklascaw.pdf.zip|}}
 +{{:​softwares:​moteur:​security_integration_report.pdf.zip|}}
 +