Simply look at available source code and documentation in order to indentify all the used software languages, tools and technology.

Develop a wrapper around the MetaComponent provided by Pascal. The application implemented by the Amigo-component must be conform to behavior shown by the application based on the MetaComponet

Add semantic the description to the MetaComponet

Remove the coded discovery from the Amigo-component and replace them with the mechanisms provided by Amigo middleware. In order to test auto:discover, aggregate and composition capability of Amigo itself

Add security to the Amigo-component in order to check the design of the Amigo middleware

All the code is share by Subversion tool and can be found at the following URL:

svn://satellite.isti.cnr.it/PERSONA/Amigo/
http://satellite.isti.cnr.it/repos/PERSONA/Amigo/

Username and Password are required in order to access to the repository

The software selected for developing are:

• Eclipse: For Java developing
• Protégé: For OWL-S and Ontology

NOTE: The following instructions assume that you are installing the software on a PC with Sun or IBM JVM

mkdir Amigo
cd Amigo
wget http://amigo.gforge.inria.fr/obr/tools/oscar_j2se.zip
unzip -q oscar_j2se.zip
cd oscar_j2se
cd bundle
wget http://oscar-osgi.sf.net/repo/shelltui/shelltui.jar
cd ../lib
mv system.properties system.properties.tmp
cat system.properties.tmp | sed s/shellgui.jar/shelltui.jar > system.properties
rm system.properties.tmp
cd ..
./amigo.sh

Now that you have a working Amigo environment you have to install the right bundles in order to set up your Amigo Enviroment as a Server by typing the following command on the shell

obr install "amigo_wsdiscovery"
obr install "amigo_ksoap_binding"

Now that you have a working Amigo environment you have to install the right bundles in order to set up your Amigo Environment as a Server by typing the following command on the shell

obr install "amigo_wsdiscovery"
obr install "amigo_ksoap_export"

One of the current implementation of the Amigo middleware is based on OSGi, and in the following section we're going to report some extra details on such implementation. The details won't be reported on time scheduled but on discovery schedule.

In order to decrease the management code required by a dynamic environment like a SOA framework, Amigo uses a utility layer provide by the Service Binder.

Service Binder wraps the business logic of a bundle in a container that implements the code needed to interact with the service used by the business logic.

Anyway, the bundle developer has to provide a metadata.xml file in order to configure Service Binder

• Amigo developer's guide

• Amigo user's guide

• Amigo D3.4 Amigo overall middleware: Prototype implementation & documentation

• OSGi Tutotial {in Italian}

• OSGi Service Binder Tutorial

• Amigo Derivable

The downloaded kit doesn't compile (syntactic errors). I've written to the developer asking help. No answer till now (rochi - 4th June 2007). I've managed the problem with a minor modification of the code. I'm trying to understand a use case that could be used to integrate this component with Amigo OSGi part. Any idea is welcome!

OBR is a de facto standard related component distribution (Bundle in the OSGi language) in OSGi Enviroment that will be part of the next OSGi Specification.

Amicom Bundle Repository of Thu Jun 22 17:15:55 CEST 2006

ANS Bundle Repository of Wed Dec 27 12:32:39 CET 2006

Amigo CMS/CASD Bundle Repository of Mon Feb 26 14:27:56 CET 2007