Swordfish Documentation: Installing ODE

Installing the ODE Engine

This section contains information and instructions on ODE and BPEL in Swordfish, starting and configuring the ODE.

About ODE and BPEL in Swordfish

The Apache ODE BPEL engine supports the execution of BPEL processes in Swordfish. In Swordfish, the ODE uses Servicemix 4 as the JBI container and an adapted ODE JBI integration layer that supports an EclipseLink based database integration to persist the process state.

For information on the general issues about the ODE JBI deployment, see ODE User Guide. If you want to try out a tutorial on ODE, see ODE Tutorials. The deployment and execution of BPEL processes in Swordfish is described in Executing BPEL processes.

Swordfish ODE is provided as an OSGI bundle which can be installed/started using OSGI mechanisms - either using the install/start commands of the OSGI console or by listing the ODE bundle inside the Equinox config.ini file.

Starting ODE

To start ODE:

1. Create a target platform which extends the standard Swordfish target platform with all the bundles in the ODE.extension project which, can be found in the Swordfish dev.eclipse.org/svnroot/rt/org.eclipse.swordfish/sandbox
2. Create an Eclipse OSGI Run Configuration using the ODE target platform as described above where:

     
     	Program arguments
   
   		-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} -console -clean
   
   	VM arguments
   
   		-Declipse.ignoreApp=true -Dosgi.noShutdown=true
   		-Djava.util.logging.config.file="your logging.properties location"
   		-Dorg.osgi.service.http.port=9001
   		-Dorg.eclipse.swordfish.registry.fileLocation="your_repository_location"
   		-Declipse.ignoreApp=true
   		-Dservicemix.base=.
   
   	Working directory
   
   		${workspace_loc:org.apache.ode}/work
   

3. Export the org.apache.ode project in dev.eclipse.org/svnroot/rt/org.eclipse.swordfish/sandbox as an eclipse plugin
4. Install and start the created ODE bundle using the OSGI console </0l>

   Configuring ODE

   In the debugging phase we recommend to increase the default global logging level in the logging.properties file referred in the -Djava.util.logging.config.file option in the run configuration.

   ODE specific logging options can found in the ode-jbi.properties file in org.apache.ode in sandbox

   ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
   debugeventlistener.dumpToStdOut=on
   

   ode-jbi.properties contains also the definition of the database layer used to persist the process state. The use of EclipseLink is hard coded in our ODE database integration layer - which originally was developed in SMILA. What can be changed is the database used - instead of Apache Derby for instance HSQLDB or an Oracle Database can be used. Currently we configured Apache Derby as an "in memory" data base, which may be changed for long running processes where real persistance is required.

   The JPA configuration is located in META-INF/persistence.xml in org.apache.ode - see persistence_xml for an explanation.

   Swordfish Documentation Home
   

   Swordfish Wiki Home