Modeling integration scenarios frequently involves asynchronous processes. For example, a purchase order process is initialized by the first order. Then, the user adds new items until the process is closed by receiving the payment and sending the goods to the customer.
Such processes are also known as long running transactions. All activities involved in this process may be separated by days or even weeks making it necessary to hold the states of such a purchase order persistent.
The persistent state management of containerized xUML services involves the following functions:
-
Querying the persistent state database by state, creation date / time and update date / time
-
Inspecting persistent state object details
-
Sending signals to persistent state objects
-
Deleting single and multiple persistent state objects
Accessing Persistent State Objects
Open the details page of a containerized xUML service and go to the Persistent State section. The Persistent State tab displays an overview of all processes in this service, the number of states in which process instances currently reside, and the number of stalled objects. In our example, there is only one IdeaProcess with instances in 6 different states and 0 stalled objects:
Click on a process to display its objects and states. Refer to Querying the Persistent State Database (Kubernetes) for details.