GEOSS Banner

Service Portal

Table of contents
  1. 1. References

Subject area/Theme

Architecture and Data

 

Short summary of Best Practice:

This practice describes how a system composed of autonomous loosely coupled services can maintain a consistent user experience. It is achieved by presenting a unified ineteface to a set of services which can be composed together to meet a defined set of user needs.

Explain why is there a need for this Best Practice?

Constructing a system of systems requires the interaction of services designed and operated independently by multiple service providers. If the individual details of service behaviour and environment are not hidden behind a user interface designed explicitly to purpose, the result can be a poor or inconsistent user experience.

Provide an example application(s)

NETMAR Portal

How widely deployed is this practice(if applicable)

Widely

Owner (Originator) Contact Information:

The NETMAR Consortium http://netmar.nersc.no

Submitter Contact Information:

Anthony Patterson (a dot patterson at ucc dot ie)

Detailed Description of Best Practice

The best practice is the application of the pattern described by  Rotem-Gal-Oz as the Composite Front End, or by Erl as the UI Mediator. The version of UI Mediator described here is the one requiring the use of a mediator service agent. In NETMAR, the pattern is implemented through a LifeRay Portal.

 

overview.dot.png

The NETMAR service architecture implements services for the discovery, download and viewing of environmental data products, including earth observation datasets, in-situ observations, and the results of model runs (e.g. oil-spill prediction models). Services are available to process these datasets, e.g. by combining them or performing standard geostatistical functions on them. Workflows can be defined and executed within the system in order to produce and view derived datasets and images. Furthermore, in order to improve the robustness and agility of the service orchestration, the compatibility of inputs and outputs can be checked against standard vocabularies describing their semantics.
References

 

Rotem-Gal-Oz, Bruno, Dahan. SOA Patterns. Manning 2011.

Erl, SOA Design Patterns. Prentice Hall, 2008

 

 

Tag
none

Files (1)

File Size Date Attached by  
 overview.dot.svg
NETMAR Services
33.07 kB12:10, 27 Nov 2012APattersonActions
You must login to post a comment.