Home
News
Events
Press
Downloads
Publications
Links
Partners
Contact
Search
Newsletter Issues
Wiki
BREIN User and Development Forum
BREIN Architecture
Knowldege Portal
Login Form
Latest News
6th Newsletter issue available   The 6th BREIN newsletter issue is now available. To download it, visit the "Newsletter Issues" section on the left menu or click here .   Details...

SOC-LOG'09 workshop at ICSOC-ServiceWave conference     BREIN is supporting the 1st International Workshop on Service Oriented Computing in Logistics (SOC-LOG'09) which will be held as part of ICSOC/ServiceWave, in Stockholm, Sweden (November 23, 2009).    Details...

New demo video BREIN project participated in the Internet of Services 2009 Concertation meeting, presenting among others two demos showing the work done on Semantically enhanced SLA Negotiations and Semantic aware and SLA-Driven Resource Management for Virtualized and Heterogeneous Platforms.   Details...

Cloud Computing Providers Part of our work done for the State of the Art is now available also through Gridipedia (visit here )   Details...

Semantics Week 2009   BREIN and the European projects STASIS, SOA4ALL, and the NESSI Semantics Group, would like to invite you to "Semantics Week" to be held June 22-26th in beautiful and logistic friendly Amsterdam.   Details...




BREIN Dissemination CDcd.jpg

newsletter.jpg





Receive HTML?

Semantically enhanced service selector

 

Prerequisites

Software Installation

SESS API

Prerequisites

The Semantically Enhanced Service Selector is a Web Service developed in Java, so that it can be deployed in any Operating System. It requires Java 5 or later and Apache Tomcat 5.5 to be installed. In case Tomcat is not installed in the computer, the installation process is aborted.

Installation

The BREIN installer provides a wizard so that the customer can specify some configuration information for the installation.

 

After all the steps are done (like accept the license terms), the application is installed and has some desktop links to access to the component functionality like  REF _Ref234904403 \h Figure 7 shows.

 

The SESS component is deployed as a Web service in a .war file. By using the BREIN installer, the .war file is just deployed inside the tomcat server container. In order to run the application, the user can just link the SESS file which start tomcat.

To configure the component, the user can update the configuration file (sess.properties) with the following properties:

·    log_file: the path of the file where the logs are stored.

·    log_level: level of the log (FINE, CONFIG, INFO, WARNING, SEVERE)

·    url_slat: the URL where the SLAT service is deployed

Finally, the services should be accessible locally at the following URL:

       http://localhost:8080/SESS-2.0/SESSService

 

       SESS API