Apache ODE

From Bauman National Library
This page was last modified on 10 December 2016, at 14:38.
</td></tr>
Apache ODE
Cassandra logo
Developer(s) Apache Software Foundation
Initial release 2007
Stable release
1.3.6 / October 12, 2013 (2013-10-12)
Repository {{#property:P1324}}
Development status Active
Written in Java
Operating system Cross-platform
Available in English
Type Middleware
License Apache License 2.0
Website ode.apache.org

Appache ODE – (Orchestration Director Engine) software executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.

WS-BPEL

WS-BPEL (Business Process Execution Language) is an XML-based language defining several constructs to write business processes. It defines a set of basic control structures like conditions or loops as well as elements to invoke web services and receive messages from services. It relies on WSDL to express web services interfaces. Message structures can be manipulated, assigning parts or the whole of them to variables that can in turn be used to send other messages.

Methods of deployed

ODE can be deployed in three different environments:

  • As a simple Web Service in Axis 2, ODE is bundled in a WAR than can be deployed in any application server and is invoked using plain SOAP/HTTP
  • As a JBI service assembly, ODE is bundled in a ZIP that can be deployed in any JBI container and is invoked using the NMR
  • SMX4 OSGi bundle

Features Apache ODE

  • Side-by-side support for both the WS-BPEL 2.0 OASIS standard and the legacy BPEL4WS 1.1 vendor specification
  • Support for the HTTP WSDL binding, allowing invocation of REST-style web services
  • High level API to the engine that allows you to integrate the core with virtually any communication layer
  • Compiled approach to BPEL that provides detailed analysis and validation at the command line or at deployment
  • Management interface for processes, instances and messages

Installation Apache ODE

Required software

Tomcat 6 installation and integration with Apache ODE

Firstly you need to install Tomcat 6. The installation process is required to pay attention on 2 things:

After installation, and before starting the server, you need to put ode.war file, which will be located in the directory with ODE, to Tomcat 6 folder -> webapps. This folder was specified during installation.

Eclipse extension for ODE

  1. Run Eclipse with administrator rights
  2. Go through Help -> Install new software
  3. Add a new repository from http://download.eclipse.org/bpel/site/1.0.4
  4. Select all available add-ons and install them

Launch ODE Server

  1. In tab Servers, click create new server (If no servers tab in the workspace, it is possible to add from Window-> Show view-> other, and there you may find servers)
  2. During the installation process, select Ode v1.x Server

Creating a BPEL Project

In the Project Explorer window, create a new project (New-> Other-> BPEL Project)

  1. After adding the project, open folder with it, and in the folder bpelContent, create BPEL Processes Fil' (New-> Other-> BPEL Processes File)
  2. In Processes name specify name of the process, and in the field Namespace you need to specify hXXp: //process_name
  3. In the next window, select Synchronous BPEL Process and to the Service Address field, enter: hXXp://localhost:<port number selected>/ode/processes/process_name

Setting up the project

After creating the project, it must be configured. To do this, open Process_name.bpel file, open it in the Design mode, and delete objects in the diagram named: FIX_ME-Add_Business_Logic_Here

  1. Then, in those place add type of element called Assign
  2. Choose this item and go Properties-> Details, and click New
  3. In the From field, select input: string, and in to field choose output: string
  4. Next, create a folder named Deployment Descriptor in bpelContent BPEL
  5. In the deploy.xml file in the Associated Port choose your process. Fields Related service and binding Used should be filled automatically
  6. After all actions you have to restart server
  7. Now we have to go to the internet browser by link: hXXp: // localhost: <port number selected> /ode/processes.html

And if everything is configured correctly, when you open a link should appear Apache ODE window and all information of your created process will be displayed in the processes tab

External links