|
|
|
|
|
TUM, Department of Computer Science,
Chair IV |
|
„Software & Systems
Engineering“, www4.in.tum.de |
|
Prof. Dr. Manfred Broy, ca. 30 MA. |
|
Working Group: Dynamic Mobile Systems |
|
Maurice Schoenmakers schoenma@in.tum.de |
|
Christian Salzmann |
|
Michael Fahrmaier |
|
Topics: Architecture description,
collaboration design and methods |
|
Contact to |
|
Siemens ICN, Microsoft Research, Sun |
|
Jini Applications: Started April/May 99 |
|
Carp@: A tool to manage Jini Systems, www4.in.tum.de/~carpat |
|
Jini Demonstrator: Handy, Fax, Scanner,
Printer und Camera |
|
Cooperation with Siemens ICN (Dr.
Michael Frank) |
|
|
|
|
|
|
|
|
|
|
|
|
A tool to create an architectural
overview to observe and manage Jini services and clients |
|
Observation |
|
Clients & Services, Locations |
|
Channels, Messages exchanged between
components |
|
Provided and required interfaces |
|
Administration and management |
|
change service attributes, check memory
resources,
start & stop components |
|
configuration of channels and locations |
|
Carp@ is itself a set of Jini services
and clients |
|
|
|
|
As defined by Garlan & Shaw and
described in Catalysis by D'Souza & Wills |
|
Components: A unit that performs
computation |
|
Services, java spaces, lookup services
and clients |
|
Ports: A point where services are
provided or required |
|
Implemented and used remote interfaces,
service proxies, listeners, JoinManager, LookupDiscovery |
|
Connectors: Connections between ports |
|
Simple remote references using method
calls, distributed events, leased resources, broadcasting
java-spaces as buffering connectors... |
|
|
|
|
Not all information was available by
standard interfaces |
|
Selected Solution: |
|
in each client or service a single
Carp@ - Bean is introduced |
|
Carp@ - Bean is a special Jini Service |
|
analyzes the service with standard
reflection as far as possible |
|
provides additional information (for
example the location) |
|
is notified by client or service about
changes |
|
is found by report service with normal
Jini techniques |
|
is requested for meta-information by
the report service |
|
propagates changes to the report
service as events |
|
|
|
|
Improve and create additional views on
the meta-model |
|
Message Sequence Charts |
|
Improve management functionality |
|
Relocation, Configuration |
|
”On the fly” byte code instrumentation |
|
Insert Carp@-Beans in predefined
service and clients automatically or assisted |
|
Investigate ”Design at runtime” |
|
|
|
For more information: www4.in.tum.de/˜carpat |
|
Download will soon be available |
|
|
|
|
|
|
Jini is for hardware devices |
|
but at least as useful for pure
software components |
|
Jini is an 'intelligent' network of
cooperating devices |
|
but until now there is no definition of
the common interfaces |
|
Jini you don't need an installation to
use a device |
|
but there is not even a standard way to
obtain user interface |
|
Jini can be used with any protocol
between the services |
|
but Jini itself requires a JVM and
class downloading |
|
Jini enables mobile computing |
|
but not networking |
|
|