...
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 Participant -> ACM_Runtime: [ASYNC] Deregister ACM_Runtime -> ACM_Database: Delete Participant Registration ACM_Runtime -> ACM_Database: Set Participant State as OFFLINE Participant <- ACM_Runtime: [ASYNC] Deregistration Accepted ACM_Runtime -> ACM_Runtime: Mark all ACM Element Instances\nrunning on Participant as OFFLINE activate ACM_Runtime deactivate ACM_Runtime @enduml |
...
PlantUML Macro |
---|
@startuml participant REST participant ACM_Runtime participant Participant database ACM_Database alt Automation Composition Type has Deployed Instances REST <- ACM_Runtime: Priming of Automation Composition Type Failed, instances deployed else Automation Composition Type is in state COMMISSIONED or PRIMED REST -> ACM_Runtime: Prime Automation Composition Type ACM_Runtime -> ACM_Database: Read Automation Composition Type ACM_Runtime -> ACM_Database: Read Participants ACM_Runtime -> ACM_Runtime: Set suitable participant ID on each AC Element Type alt Was a sutable participant ID found for each AC Element Type? ACM_Runtime -> Participant: [ASYNC] Send Priming Request to all Participants\nwith Automation Composition Type Definition ACM_Runtime -> ACM_Database: Set Automation Composition Type State to PRIMING REST <- ACM_Runtime: Priming of Automation Composition Type Ordered else REST <- ACM_Runtime: Priming of Automation Composition Type Faield, no sutiable participant found end else REST <- ACM_Runtime: Priming of Automation Composition Type Failed, invalid state end @enduml |
...
Instantiation dialogues are used to create, set parameters on, instantiate, update, and remove Automation Composition instances.
3.1 Create
...
an Automation Composition Instance
...
PlantUML Macro |
---|
@startuml participant REST participant ACM_Runtime database ACM_Database REST -> ACM_Runtime: Create Automation Composition Instance for\nspecified Automation Composition Type with\nspecified parameter values alt Automation Composition Instance exists alt Automation Composition Instance is not in state UNDEPLOYED ACM_Runtime -> REST: Automation Composition instance exists and is already deployed else note right of REST Updates on "Not In Service" Automation Composition Instances are allowed end note end end alt Specified Automation Composition Type Composition Exists alt Specified Automation Composition Type is in state PRIMED ACM_Runtime -> ACM_Database: Store Automation Composition Instance ACM_Runtime -> ACM_Database: Set Automation Composition Instance State to UNDEPLOYED ACM_Runtime -> REST: Automation Composition Instance Created else ACM_Runtime -> REST: Automation Composition Type is not in state PRIMED end else ACM_Runtime -> REST: Automation Composition Type is not found end @enduml |
...