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?

SATSLARepository

The SATSLARepository component is present on the server side and is capable of storing the SATSLA Templates, making them accessible by the service discovery and the BREIN Agents. The main component that interacts with the SLA Template Repository is the SATSLA GUI, the graphical interface that works with the SATSLA Templates, allowing the Service Provider to create and update the SATSLA Templates within knowledge of the xml syntax. Another important function of this component is to store the relations among the OWL service profiles and the SATSLA Templates with which Non functional features of those services are offered.

This component is also used for the service discovery to retrieve the SATSLA Templates associated to specific owl service profile and by the BREIN agents for the negotiation process.

The main functionality is as follows:

·        Storing the SATSLA’s in the repository

·        Recover specific SATSLA Template  getSATSLA(slat_Id)

·        Recover associations among SATSLATemplates and OWL service profiles

 

 

 

Prerequisites

Software Installation

Service Discovery API

Prerequisites

The SATSLA Repository service is a .Net application that relies on Microsoft .NET Framework 3.5 and on Microsoft SQL Server.

 

Installation

The SATSLA Repository must be deployed on Microsoft Internet Information Service (IIS) on Windows XP Professional, Windows Vista, Windows Server 2003 and Windows Server 2008. Furthermore, a local installation of Microsoft SQL Server needs to be present, as this database management system is used to store SATSLA Templates. Mandatory modifications are needed after the installation is done.

Standard deployment leads to the service being available on the local host under the following address:

http://localhost/SATSLARepository/SATSLARepositoryService.asmx

 Mandatory modifications after installing in Web.config file are:

·        Set the Path and filename for the Log file

<add key="SATSLARepositoryService_LogPath" value="[DirectoryPathForLogFiles]"/>

<add key="SATSLARepositoryService_LogFileName" value="[LogFileName]"/>

Where [DirectoryPathForLogFiles] is the physical Path for store the log files. The syntax will be as:   [unit:/directoryName/] and [LogFileName] is the name of the file charge to store the log messages.

·        Set the connection string for the database

<connectionStrings>

  <add name="BreinConnectionString" connectionString="Data Source=[.\SQLEXPRESS];Integrated Security=True;" providerName="System.Data.SqlClient" />

</connectionStrings>

Where [.\SQLEXPRESS]is the instance location where SQLServer is running.

·        Generate the Database:  initRepository() method exposed for the service must be called, which sets up the database tables. To do this operation, is necessary invoke the service in the following way:

http://localhost/SATSLARepository/initRepository