...
| PlantUML Macro |
|---|
@startuml participant Participant participant ACM_Runtime database ACM_Database Participant -> Participant: Uninitialize all ACM Element Instances running on Participant\n(See Instantiation Dialogues) activate Participant deactivate Participant ACM_Runtime -> ACM_Database: Delete Participant Registration Participant <- ACM_Runtime: [ASYNC] Deregistration Accepted @enduml |
1.
...
3 Participant Supervision
Participant Supervision is performed periodically between participants and the ACM runtime server to ensure that registered participants are available over time. Participants send a heartbeat message to the ACM runtime at a configured interval.
...
| PlantUML Macro |
|---|
@startuml
participant ACM_Runtime
database ACM_Database
loop Every ACM_Runtime Supervision Interval
loop Over all Participants
ACM_Runtime -> Database: Read Participant Heartbeat Information
alt Participant Heartbeat not received in Timeout Interval
ACM_Runtime -> ACM_Runtime: Inform all ACM Element Instances\nrunning on Participant of Timeout\n(See Instantiation Dialogues)
activate ACM_Runtime
deactivate ACM_Runtime
end
end
end
@enduml |
1.4 Participant Information
The information on participants is available over a REST endpoint.
| PlantUML Macro |
|---|
@startuml participant REST participant ACM_Runtime database ACM_Database REST -> ACM_Runtime: Get Participant Information ACM_Runtime -> ACM_Database: Read Participant Data REST <- ACM_Runtime: Return Participant Information including\nsupported ACM Element Types and Heartbeat Information @enduml |
The ACM runtime regularly checks t
2 Dialogues on Automation Composition Types
...