The CLAMP Automation Composition Runtime Lifecycle Management uses the following system-level dialogues. These dialogues enable the CLAMP runtime capabilities described in Section 2 of TOSCA Defined Automation Compositions: Architecture and Design. Design Time dialogues will be described in future releases of the system.
| Table of Contents |
|---|
...
1 Dialogues on Participants
...
1.1 Participant Registration
Participant Registration is performed by a Participant when it starts up. It registers its ID and type with the ACM runtime.
| PlantUML Macro |
|---|
@startuml
participant Participant
participant ACM_Runtime
database ACM_Database
Participant -> ACM_Runtime: Register
ACM_Runtime -> ACM_Database: Create or Update Participant Registration
Participant <- ACM_Runtime: Registration Accepted
loop over all Automation Composition Types
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
@enduml |
...
1.2 Participant Deregistration
Participant Registration is performed by a Participant when it shuts down. It deregisters its ID and type with the ACM runtime. The ACM runtime reprimes any Automation Composition Types that use the participant type of the removed participant because the participants available to the Automation Composition Type have changed. It also triggers supervision of any AC instances using this particular participant so that the instance can be moved to another participant or can be marked as errored.
...