...
| PlantUML Macro |
|---|
@startuml
participant Participant
participant ACM_Runtime
database ACM_Database
Participant -> ACM_Runtime: Deregister
ACM_Runtime -> ACM_Database: Delete Participant Registration
Participant <- ACM_Runtime: Deregistration Accepted
loop over all Automation Composition Type Definitions
alt This Automation Composition Type has the Participant Type of this Participant
ACM_Runtime -> ACM_Runtime: Trigger Priming of this Automation Composition Type
end
end
loop over all Automation Composition Instances
alt This Automation Composition Instance uses this Participant
ACM_Runtime -> ACM_Runtime: Trigger supervision of this Automation Composition Instance
end
end
@enduml |
2 Dialogues on Automation Composition
...
Types
Commissioning dialogues are used to commission and decommission Automation Composition Type definitions Types and to set the values of Common Parameters.
Commissioning an Automation Composition Type is a three-step process
...
The values of common parameters are included in the TOSCA YAML file that defines the full Automation Composition Type.
2.1 Commissioning an Automation Composition Type
...
| PlantUML Macro |
|---|
@startuml participant REST participant ACM_Runtime database ACM_Database REST REST -> ACM_Runtime: Commission Automation Composition Type Definition alt Automation Composition Type exists and has Instances ACM_Runtime -> REST: Type Definition Commissioning Failed else ACM_Runtime -> ACM_Database: Create and Store Automation Composition Type Definition ACM_Runtime -> ACM_Runtime: Trigger Priming of Automation Composition Type Definition ACM_Runtime -> REST: Type Definition Commissioned end @enduml |
...