doesn’t necessarily mean to replace existing systems
in order to participate. This is one of the critical
success factors of our common infrastructure.
Swiss Campus
Unive r s ity Z
Institute XY Institute XZInstitute XX
University YUniversity X
Ex te rnal PartnerExternal Partner
Medium
Agent
AdapterAdapter
Ad a p t erAdapter
Adap terAdapterA dapt er
Ad a p t e r
Figure 2: Hierarchy of multi-agent systems in SCWS.
As depicted in Figure 2 the central domain is
situated on the second upper horizontal layer and
symbolizes the Swiss Campus. The above layer
comprises external domains e.g. companies
providing insurances for students or Swiss
governmental organisations. On the layer below the
Swiss Campus layer different universities are placed
that interoperate through the Swiss Campus domain.
Each university is built up of different institutional
domains. The different domains are connected by
adapters that allow for the seamless integration into
a holistic architecture.
Within the Swiss campus internet services are
provided by one central organisation. The SCWS
project considers to create one central service hub
that will be operated by the organisation currently
providing the internet services. You can think about
other approaches without a central hub to connect
Swiss universities. One example is to organise
communication in a peer-to-peer network. However
the existence of the internet service organisation and
thus the existing expertise in operating a hub and
providing services led us to the central hub approach
The hub function of the central Swiss Campus
domain allows for the loose coupling by providing a
central integration function. Furthermore it will
guarantee the availability of the message exchange
medium and provide security services.
We strongly believe that our envisaged approach
is applicable to other countries as well. Through the
loose coupling the autonomy of organisational units
will be guaranteed. However by simply defining
common rules and standards it will be possible to
make the coupling tighter.
3.2 Meeting Technical Challenges
The main technical challenge for the Swiss Campus
is the seamless integration of existing,
heterogeneous applications. We will therefore create
a central middleware medium that will allow for the
interconnection of these applications. The
applications themselves will then be connected
either directly, through adapters, or through the
coupling of the existing middleware solutions the
applications are connected to.
The basic principles for the Swiss Campus
architecture are based on best practices from service-
oriented architectures (SOA), as described in
(Arsanjani, 2004), and event-driven architectures
(EDA), as described in (Chandy, 2006). In order to
implement the described functionality of SOA and
EDA a middleware infrastructure is required that
provides special communication and mediation
services (Schulte, 2008a, Schulte, 2008b). For the
Swiss Campus we will implement an Enterprise
Service Bus (ESB) (Schmidt et al., 2005; Maurizio
et al., 2008; Papazoglou and van den Heuvel, 2007).
The required communication and mediation services
(Keen et al., 2004) will be described in more detail
later in this paper.
Furthermore we have to define standard objects
for the Swiss Campus that will be exchanged
through the event bus. These standard objects follow
both syntactical and semantic standards. An example
of such a standard object is an object containing a
student’s master data. As well we will specify a
concept for the connection of legacy applications
through adapters.
Communication and Mediation Services. One of
the challenges that the SCWS project has to cope
with is what central communication and mediation
services will be needed and where they should be
implemented. Further the service design has to be in
line with the service specification of the Event Bus
Schweiz initiative (Bund, 2006). Hence we will
guarantee that services of the ESB will be able to
seamlessly access the services of the Swiss Campus.
The services have to be divided into a group of
services that have to be implemented on the central
Swiss Campus bus and services that can be
implemented on distributed buses. The services
running on the Swiss Campus bus comprise a
directory service, an event catalogue service, a
subscription service, and security services. The
services running on the distributed buses cover
services for transformation, simulation of events,
operational services, tracing, error handling,
exception handling, validation, and routing.
Table 1 describes these services in more detail.
ICEIS 2009 - International Conference on Enterprise Information Systems
270