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?

SERVICE DISCOVERY REGISTRY GUI

The Service Discovery Registry Web (SDRWeb) is an administrative GUI for an instance of Service Discovery Registry (SDR). Through the use of SDRWeb we can execute the following main operations:

·         Publish new services into local instance of SDR.

·         Allows the Customers to find services they need by querying, starting from the local instance, the Service Discovery Registry’s network.

·         Manage the configurations of the associated SDR instance (i.e. semantic properties, repositories location, etc...)

·         Aid the Providers to build a basic OWL-WS Service Profile

 

The SDRWeb interface is a Web GUI with four tabs:

·         User Client;

·         Provider Client;

·         Admin Client;

·         Profile Generator;

The User Client allows the Customers to search the services. The tab shows a text area to provide an OWL-WS Query

 

The Provider Client tab shows the service list of current advertised services into the related instance of SDR. It allows the Service Providers to publish new services through a form.  The form has three fields: the “ServiceId” which is a unique identifier of the new service, the “Service Profile” text area where the customers copy the OWL-WS Service Profile description and the “AdditionalInfo” which allows attaching at the new service a list of key/value pair.

 

The Admin Client tab allows the administration of SDR instance, for example the semantic properties, the repositories location, etc. In this tab we can also connect or disconnect the SDR instance form Service Discovery Registries Network.

 

The last interface is the Profile Generator tab, which aids the Providers to build an OWL-WS Service Profile. In this tab we have four kinds of fields: Ontologies, Inputs, Outputs and Classification. The Provider specifies the semantic concepts that define the signature (I/O) and the classification of the new service. After the Provider has generated the OWL-WS Service Profile, it uses the Provider Client tab to publish the new service into SDR.

 

 

Prerequisites

Software Installation

Service Discovery API

Prerequisites

The Service Discovery Registry component requires Microsoft .NET Framework 3.5 or higher and IIS (provided with the O.S.).

Installation

The Service Discovery Registry Web is shiped with the component SDRWeb. The SDRWeb component must be deployed on Microsoft Internet Information Services (IIS) on Windows XP Professional, Windows Vista, Windows Server 2003 and Windows Server 2008.     

In order to deploy the component you have to execute the related installer (SDRWeb.msi) and following the instruction for a correct configuration.

The main configuration of SDRWeb requires the following parameters:

·         SDR endpoint, which represents the associated instance of Service Discovery Registry;

·         SDR log file, which is the log file of associated SDR instance;

·         Semantic Engine, which is the server where the Semantic Engine component of SDR is running (usually is in the same host of SDR instance)

 

The installer by default will create a “virtual” directory in the IIS called “SDRWeb”. By opening the IIS Management Console you will have to create this application directory.

 

 

The Web GUI should be accessible locally at the following URLs:

http://localhost/SDRWeb/Default.aspx

Note: If you wanted to change the SDRWeb configuration manually, the installer execution creates inside SDRWeb “virtual” directory a Web.config config file. The section to modify with relative values as shown below: