Execution Infrastructure User's Guide
- 1 Execution Infrastructure User's Guide
- 2 Process Optimizer
- 3 Semantic Context Space Engine
- 3.1 Information Management
- 3.2 External Sources
- 3.3 Administration
- 4 Service Orchestration Engine
- 4.1 Installation
- 4.1.1 Download and Install the J2SE Runtime Environment (JRE)
- 4.1.2 Download and install Apache Tomcat
- 4.1.3 Download and install Apache ODE engine
- 4.2 Deployment of ODEDeploymentService
- 4.3 Process Deployment
- 4.4 Monitoring
- 5 User's Environment Configuration
Process Optimizer
Optimization Algorithms
Configuration Parameters
Semantic Context Space Engine
Information Management
External Sources
Administration
To facilitate the operation of the SCS Engine the following ports used by underlying Jini services should be accessible from the net:
- 1091: This port (or 1090) is used by the Jini Lookup service for registering and discovering remote objects/services
Service Orchestration Engine
Installation
We present the installation process for both Microsoft Windows (XP, Vista, 7) and Gnu/Linux (Ubuntu 10.04). In order to install the service orchestration engine on your local machine, you must execute the following steps:
Download and Install the J2SE Runtime Environment (JRE)
- Microsoft Windows
- Download the Java 2 Standard Edition Runtime Environment (JRE), release version 5.0 or later JavaSE.
- Install the JRE according to the instructions included with the release.
- Set an environment variable named JRE_HOME to the pathname of the directory into which you installed the JRE, e.g. c:\jre5.0 or /usr/local/java/jre5.0
- Gnu/Linux
- Install the sun-java packages
>> sudo apt-get-repository “deb http://archive.canonical.com/ lucid partner” - Install the Java 2 Standard Edition Runtime Environment (JRE), release version 5.0 or 6.0
>> sudo apt-get install sun-java6-bin - Alternatively, you may install the Java 6 SDK
>> sudo apt-get install sun-java6-jdk
- Install the sun-java packages
Download and install Apache Tomcat
- Microsoft Windows
- Download Tomcat 6.0 distribution Tomcat. There are two options:
- Install the binary distribution for the windows environment. For this purpose download one of the available Tomcat binary distributions for the windows environment.
- Unpack the binary distribution into a convenient location so that the distribution resides in its own directory (conventionally named apache-tomcat-[version]). Set the CATALINA_HOME environment variable to the pathname of the directory into which you unpack the binary distribution. For the purposes of the remainder of this document, the symbolic name CATALINA_HOME is used to refer to the full pathname of the release directory.
- Install the Windows service installer. This is a Windows specific distribution that includes the Windows service wrapper and the compiled APR/native library for use with 32-bit/64-bit JVMs on both 32/64 bit Windows platforms. This way tomcat is used as a Windows service.
Note: Due to a bug in the installer the apache tomcat icons on the start menu fail to start/stop the service. You can start/stop and configure Tomcat using the provided menu in the Windows toolbar. Because many users may find it confusing we recommend you to install the binary distribution as described in the previous step.
- Install the binary distribution for the windows environment. For this purpose download one of the available Tomcat binary distributions for the windows environment.
- Start up Tomcat executing the command:
>> $CATALINA_HOME\bin\startup.bat
After start up, the default web applications included with Tomcat will be available at http://localhost:8080/ - Shut down Tomcat using the command:
>> $CATALINA_HOME\bin\shutdown
- Download Tomcat 6.0 distribution Tomcat. There are two options:
- GNU/Linux
- Install Tomcat 6.0 with the command:
>> sudo apt-get install tomcat6
The default installation will be in /var/lib/tomcat6/. For more details read the Ubuntu provided guide. Set CATALINA_HOME environment variable to point to the base path of the Tomcat installation location - Start up Tomcat executing the command:
>> $CATALINA_HOME/bin/startup.sh
After start up, the default web applications included with Tomcat will be available at: http://localhost:8080/ - Shut down Tomcat using the command:
>> $CATALINA_HOME/bin/shutdown.sh
- Install Tomcat 6.0 with the command:
Download and install Apache ODE engine
- Microsoft Windows and GNU/Linux
- Download the latest Apache ODE WAR distribution (apache-ode-war-1.3.4.zip) from the Apache ODE download site

- Unzip the distribution somewhere on your disk and copy ode.war to Tomcat's webapp directory.
- Start up Tomcat and ODE should be up and running. You should get the Axis2 welcome page under http://localhost:8080/ode.
- Download the latest Apache ODE WAR distribution (apache-ode-war-1.3.4.zip) from the Apache ODE download site
Deployment of ODEDeploymentService
In this section we present the steps required for the deployment of the ODEDeploymentService. This service will run on top of Tomcat where ODE has been deployed and will support the deployment of service chains on the ODE engine. The ODEDeployment service receives from the user (i.e. this could be either process designer or anyone interested in deploying a process) as input a URL request providing a zip file, which contains the appropriate description files. The zip file is created by the user. We described how the user creates an appropriate zip file. The steps for deploying the service are the following:
- Microsoft Windows and GNU/Linux
- Open the ODEDeploymentService.war file and configure the WEB-INF\classes\com\s3lab\ode.properties file, contained into the .war. This file contains key-value entries which the user must set into system dependent values.
- temporaryDirectory, is a user specified directory that will be used by the ODEDeploymentService to store the downloaded .zip files and to write the log file. This directory must have write permission.
- deploymentDirectoryODE, is the user specified path to the ODE process deployment directory (ode/WEB-INF/processes). This directory is used by ODE to store the deployed processes.
- Copy the ODEDeploymentService.war file to Apache Tomcat’s webapps directory. The service will be automatically deployed on Tomcat.
- Open the ODEDeploymentService.war file and configure the WEB-INF\classes\com\s3lab\ode.properties file, contained into the .war. This file contains key-value entries which the user must set into system dependent values.
Process Deployment
To ensure the deployment of specified service chains to the Service Orchestration Engine compliance to the following rules should be ensured:
- The process specification file (i.e. BPEL file) along with the WSDL files (and WSML files) of the related services should be valid XML (or RDFS) documents.
- Encodings and Styles of all related operations should be properly specified. More details on the selection of the appropriate style/encodings are provided at the IBM article titled "Which style of WSDL should I use?"
- The address of the process endpoint should adhere to the following format http://<server name>:<port>/ode/processes/<process path>





