As describe in the introduction section, a CommunityMashup instance consists of

What source components and interface components to use and how to configure them is described in the mashup configuration. In the following we first describe what source components are available and then briefly address how a mashup configuration looks like - and how such a configuration can be used to instantiate a mashup instance.

CommunityMashup source components

Source components are responsible for the connection to external services. They are reading and writing data and transforming the data between the external and the CommunityMashup data model. All source components are highly configurable for special application purposes.

Public source components

The following sources are available for general use: (information from

Source components under development

The following sources have been developed for specific use cases (and are not included in the basic CommunityMashup distribution).

Recently updated / used:

Not updated for some time:

Configuring a CommunityMashup

In addition to the source components, a CommunityMashup instance consists of interface components and a data store.

Configuring a CommunityMashup instance therefore means

The whole configuration is represented in an XML file. This file can either be changed directly or be changed via the visual mashup web configurator.

See CommunityMashup - Configuration for examples of a full configuration.

Running a CommunityMashup

You can run a CommunityMashup either

Running in the Eclipse IDE

Please first follow the description for setting up an Eclipse installation with all relevant plugins and for downloading the mashups core components as provided in the section "Setting up an development environment" on CommunityMashup - Configuration.

Then create a run configuration as described in section "Testing the sources" on the same page.

In this run configuration you can specify a mashup configuration file (as described in the previous section). If no path is provided, the file is looked for in package "MashupFactoryService/configuration".

Running in a standalone server environment