Role(s): Service Provider

Component(s):                     Semantic Yellow Pages Service

Semantic Service Aggregator

License: BSD

Usage Instructions

Installation

Software Installation

Semantic Service Offer Discovery Toolkit API

Usage Instructions

This toolkit of components allows resource providers to outsource new resources (computing capacities) on demand from third parties through the use of the BREIN infrastructure. It works through a distributed system of services that implement a common web-service interface so that clients can query at any point in the overall system that they choose. Resources are outsourced through publication of offers to use them (via suitable BREIN-enabled services) in a semantically annotated form to a Yellow Pages service. Clients then submit SPARQL queries to the Yellow Pages service and get back results in a (reasonably optimal) order; this allows a Semantic Scheduler to off-load much of the work on working out who to establish a new SLA with to these expert components.

The Aggregator component allows a single query to be spread out across multiple Yellow Pages components, and the results from them collated. Its use is optional, but it makes it more practical to search multiple Service Providers for opening offers to supply a service and resources.

 Semantic Service Offer Discovery Installation

Installation Requirements

The toolkit components require Windows/Linux OS platform[1], with the following features:

· Java 1.5+

· Web service Container.

This toolkit of components allows resource providers to provide a semantic lookup service for their service offers. It is expected that these offers will only form initial offers; further negotiation may be needed for clients (including other service providers) to actually use the service in question.

A service provider will not deploy all of the components of this toolkit on the same system; the Yellow Pages and Aggregator services offer the same port type as they are two ways of implementing the same abstract functionality.

Components Involved:

The components involved are: the Resource Manager and the Semantic Service Discovery. Figure 44 shows their relationships. They will be installed in both Service Provider and Third-party infrastructure.

Can be combined with: Semantic Enhanced Resource Allocator, (resource manager)

 Deployment Tips

The steps needed to integrate the Service Semantic Offer Discovery in a system are:

Integrating a Service Semantic Offer Discovery will be a matter of configuring and deploying a service into a container. Then the address of the discoverer will need to be published, typically as a URL; all kinds of Discovery Service use the same service port type, so a URL is sufficient for publication purposes.

For Aggregators, the addresses of the target services will need to be given to it as URLs in service properties. The Yellow Pages service does not require any configuration under normal circumstances; it is up to entities publishing offers to control their publications at the time that they make them.

Software Installation

Semantic Yellow Pages Service

This component provides two services, a publication interface that allows RDF-annotated service offers to be made, and a lookup interface that integrates with the Semantic Service Discovery System.

Prerequisites

This component is OS independent, and runs under Java 5 or later and should be installed into a standard Java WebService container.

Installation

This installer has been created for Windows, at runtime the components are installed automatically under the Web Service container that should be previously installed:

Semantic Service Offer Discovery v1.0.exe

This component can also be distributed as a WAR file, which should be installed into your WebService container according to that container's service deployment instructions. It should not need manual configuration in normal operation. Use by creating offers and using the publication port type's operations to upload and manage them, and the Semantic Service Discovery type's operations to look them up.

Note: Logging uses the standard java.util.logging interface.

Semantic Service Aggregator

This component provides the offer aggregator for the Semantic Service Discovery system, allowing queries to be distributed across multiple systems for the "cost" of a single query by an end user.

Prerequisites

This component is OS independent, and runs under Java 5 or later and should be installed into a standard Java WebService container.

Installation

Storing URLs for the services to delegate to in service properties configures this component. The properties to use are:

aggregator.target.1
aggregator.target.2
aggregator.target.3
...

See the javadoc for this component for other tweakable parameters, though they should not normally need adjustment.

Note: Logging uses the standard java.util.logging interface.

 Semantic Service Offer Discovery Toolkit API

Aggregator Interface