Persistence
Whenever Orchestra has to store state information an underlying repository is necessary. In case of Orchestra a relational database is used. Within the relational database the following topics are stored
Configuration information
-
The repository contains all scenario elements that have been deployed to the Orchestra server.
-
In case of scenarios and process models not only the current version, also the history of the scenario elements is stored
Runtime information
-
All runtime information that needs to be persistent is also stored within the repository
-
Message data
-
Process state
-
Signals
-
System Events
-
Work queues