The figure below shows the architecture of SYNERGY system:
The SYNERGY system is composed of 8 software components:
| Partner knowledge
management service (PKMS)
| PKMS provides effective mechanisms to manage and to utilize all the knowledge in the SYNERGY Knowledge Bases:
VOKB – Virtual Organization KB,
EKB – Enterprise KB, and
CPKB – Collaboration Pool KB.
|WP 2 by CU|
| The CMS is an evolution of the moderator software on to a platform like SYNERGY to support the virtual enterprises.
The CMS has its own knowledge base (CMS KB) containing information about the CMS users and knowledge about how to perform the moderation activities.
|WP 3 by LU|
| Collaboration pattern
editor and simulator (CPE)
|CPat editor and simulator allows to describe and simulate collaboration patterns as BPMN artefacts.||WP 4 by EBM|
|Collaboration pattern assistant (CPA)|| CPat assistant is a component that undertakes the management of collaboration patterns inside SYNERGY system.
CPA has an associated KB, called CPat KB, containing instances of CPat.
|WP 4 by ICCS|
| Complex event
| CEP is focused on complex patterns of events. To detect these patterns CEP is concerned with clouds of events, i.e. multiple streams, to fulfill event patterns.
SYNERGY’s CEP leverages the ESPER & ETALIS engines.
|WP 5 by FZI|
|Complex event pattern editor (CEPEDO)||CEPEDO is a Knowledge Evolution Framework dedicated to generating, maintaining and managing complex event patterns.||WP 6 by FZI|
|Event Service Bus||The SYNERGY Event Service Bus leverages the Petals open-source ESB combining event-driven and service-oriented approaches to simplify integration of software components||WP7 by EBM|
[GEasyBPMN Editor] enhanced to provide a BPMN editor and an event-based simulator. It provides also a BPMN to XPDL transformation. This Web-based GUI allows to design BPMN processes with a graphical representation.
The primary intention of the simulator is to provide users the possibility to verify their business processes. It is also aimed at providing the ability to interact with the BPMN process, so that users can play with the process elements and their behaviors. The users can make any changes on the process scenario during execution in order to observe the consequences of changes.
The Simulator integrates an engine which manages the token(s) within a process through all the various elements while “executing” their behavior and considering the scenario that the designer specified for each element. Once all the tokens have been consumed, the process can be considered as complete and a report on the simulation of the process is generated.
- WS-Notification library implemented
- [Broker component] according to the Brokered Notification