22
April 2004 Dipl.-Inf. Christian Sandor, Dipl.-Inf. Asa MacWilliams Supervisor: Prof. Bernd Brügge Ph.D. Prof. Gudrun Klinker Ph.D. Aufgabenstelle r: Markus Michael Geipel Presenter: SEP Run-time Development and Configuration of Dynamic Service Networks

Aufgabensteller:Prof. Bernd Brügge Ph.D. Prof. Gudrun Klinker Ph.D. Supervisor:Dipl.-Inf. Christian Sandor, Dipl.-Inf. Asa MacWilliams Presenter:Markus

Embed Size (px)

Citation preview

April 2004

Dipl.-Inf. Christian Sandor,

Dipl.-Inf. Asa MacWilliams

Supervisor:

Prof. Bernd Brügge Ph.D.

Prof. Gudrun Klinker Ph.D.

Aufgabensteller:

Markus Michael GeipelPresenter:

SEP

Run-time Development and Configuration

of Dynamic Service Networks

April 2004 <Markus Michael Geipel> 2/20

Overview

• Motivation• DIVE• Problem Statement• CAR• Requirements• Solutions• Results• Future Work

April 2004 <Markus Michael Geipel> 3/20

Motivation

• Data flows are the heart of an AR-System

• DWARF is thus a cooperating service network

• Via DIVE this network can be visualized

• But: It can not be configured or developed

April 2004 <Markus Michael Geipel> 4/20

DIVE• DWARF Interactive Visualisation Environment• Implemented by Daniel Pustka (SEP)

Service Descriptions

Service Manager

Query Service Descriptions

April 2004 <Markus Michael Geipel> 5/20

• DIVE should not only be a monitoring tool, but a tool to actively support the development of dynamic service networks.

• Further more DIVE has to be convenient to use in means of stability, speed and GUI.

Problem Statement

April 2004 <Markus Michael Geipel> 6/20

CAR

• CAR acts as a source of new requirements and ideas that originate from the everyday practice with DWARF.

• Further more CAR explores authoring techniques in AR. Thus CAR’s field of application intersects with DIVE’s field of application.

April 2004 <Markus Michael Geipel> 7/20

Requirements Analysis: The Requirements

• Functional– Changing the network structure

• Changing Attributes and Predicates• Connecting Services• Starting Services

– Making Changes Persistent– Configuring Services – Looking at the network structure

• List View of the Services• Grouped View of the Services

• Non Functional (excerpt)– Performance: Suitable for CAR, Update in average within 5

seconds. – Reliability: Running several hours in productive work.

April 2004 <Markus Michael Geipel> 8/20

More GUI, more Views• New Icons• New Color Scheme• New List View

April 2004 <Markus Michael Geipel> 9/20

More GUI, more Views• Grouping und Filtering

April 2004 <Markus Michael Geipel> 10/20

Extensions• Changing Predicates,

changing Attributes

April 2004 <Markus Michael Geipel> 11/20

Extensions• Connecting Services

April 2004 <Markus Michael Geipel> 12/20

Extensions• Making Changes

Persistent

April 2004 <Markus Michael Geipel> 13/20

Configurators

Configuration

Graphical User Interface Information

Information

April 2004 <Markus Michael Geipel> 14/20

Configurators

Computer X Computer Y

DIVE

Service to be configured

Configurator Service

1) read ServiceDescription

ServiceDescription for the Configurator

ServiceManager

4) read ServiceDescription

2) Create ServiceDescription

3) start

ServiceDescription of the Service to be configured

ServiceManager

5) connect

April 2004 <Markus Michael Geipel> 15/20

Update Speed• Update Speed

– How fast can DIVE’s internal representation of the DWARF service network be synchronized with the information residing in each individual ServiceManager

• Reorganization of the Update Routine– Don’t throw away the system model– Set the stage for further improvement

• Version Counting– Only services that actually changed need to be updated

• Multithreaded Update– The main part of the update time is network roundtrip delay– Every ServiceManager runs on a different host and is thus independent.– Thus every ServiceManager can easily be queried in parallel

• Reduce the subjective Update Speed– As soon as new information is available, show it.

April 2004 <Markus Michael Geipel> 16/20

Results: Update Speed

A: 2 Hosts, 13 active + 128 inactive sercvicesB: 3 Hosts, 24 active + 192 inactive sercvices C: 4 Hosts, 35 active + 256 inactive sercvices

April 2004 <Markus Michael Geipel> 17/20

Results: Survey

1

2

3

4

5

Higher

Upd

ate

Speed

Chang

e Pre

dica

tes

Chang

e Attr

ibut

es

Conne

ct S

ervic

es

Config

ure

Servic

es

Save

XML

Descr

iption

List V

iew

Start

Servic

es

Color S

chem

e fo

r Ser

vices

Group

ed S

ervic

es

Diplomanden SEP-Students AverageU

tility

April 2004 <Markus Michael Geipel> 18/20

Future Work: Near Future• Refactoring

DwarfSystemModel (Design Patterns)

• Refactoring the Model Views (complete MVC)

• Polishing up the UI– Ergonomic design (like

Eclipse or Visual Studio)– Other graphical notations (e.

g. UML like)– Minimap and zoom

April 2004 <Markus Michael Geipel> 19/20

Future Work: Far Future• DIVE in 3D or even in AR?

– Mockup by Michael Riedl

April 2004 <Markus Michael Geipel> 20/20

Thank you very much for paying attention

• Questions?

April 2004 <Markus Michael Geipel> 21/20

Results: Update Speed

Situation C

April 2004 <Markus Michael Geipel> 22/20

Services in DWARF• Services have Needs and Abilities, which have types

• Abilities have Attributes, Needs have Predicates. • These can be set at runtime. • One service’s Needs depend on other services’ Abilities.• Distributed CORBA-based Middleware establishes connections for communication

between services (management, lookup, connection)