Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/swamp/htdocs/includes/functions.inc.php on line 15
| SWAMP Workflow Administration and Management Platform | doc2html
SWAMP Index Design
* Home
* Documentation
* License
* Demo Server
* Wiki
* Screenshots
* F A Q
* Downloads
* Contact
* Credits

SWAMP is supported by:
SourceForge.net Logo

The Container

The central functionality of SWAMP is provided by the so-called managers. A manager is a Singleton that takes care of a specific subsystem. The managers are:

The StorageManager provides the abstraction level between data storage (currently database only) and the rest of the system. It provides the following methods for each object type Blubber we have:

  • ArrayList getBlubbers()

  • int storeBlubber(Blubber b)

  • int loadBlubber(int blubberId)

  • void removeBlubber(int blubberId)

Object types are: tasks, workflows (with all components), and data. Everything, actually.

The WorkflowManager reads in the workflow definitions and keeps track of the workflow template objects that are created from them. It provides a list of possible workflows, creates workflows on request and interacts with the StorageManager to store and reload workflows to and from storage. If you need access to one ore several workflow objects, get them from the WorkflowManager, not the StorageManager.

The TaskManager accepts tasks from the other subsystems or frontends, stores them and gives them back on request. When a task is done, the system that acted on it gives it back to the TaskManager with finishTask(Task), which then checks if everything is ok and performs the associated actions and clean-up work. Tasks containing a user action are stored until a frontend requests them, tasks for which other subsystems are responsible are handed over to them directly.

The EventManager accepts events from anywhere in the system and distributes them to any object that has registered itself as a listener to a specific event type. (Yet to be written.)

The WorkflowReader is used for reading in workflow definition files in XML.

Note: This might be split into a WorkflowXMLReader and a WorkflowSwwReader class, where "sww" stands for "SWAMP workflow". swx would be SWAMP xml file etc.

Valid CSS! Valid XHTML 1.0!