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.
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.
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.
2 Dialogues on Automation Composition Type Definitions
Commissioning dialogues are used to commission and decommission Automation Composition Type definitions and to set the values of Common Parameters.
Commissioning an Automation Composition Type is a three-step process
The Automation Composition Type must be created, that is the Automation Composition Type definition must be loaded and stored in the database. This step may be carried out over the REST interface or using SDC distribution.
The Common Properties of the Automation Composition type must be assigned values and those values must be stored in the database. This step is optional only if all mandatory common properties have default values. The Common Property values may be set and amended over and over again in multiple sessions until the Automation Composition Type is primed.
The Automation Composition Type Definition and the Common Property values must be primed, which is sent to the concerned participants. Once an Automation Composition Type is primed, its Common Property values can no longer be changed. To change Common Properties on a primed Automation Composition Type, all instances of the Automation Composition Type must be removed and the Automation Composition Type must be de-primed.
2.1 Commissioning an Automation Composition Type Definition using the ACM REST Interface
2.2 Commissioning an Automation Composition Type Definition using SDC
2.3 Deleting an Automation Composition Type Definition
2.4 Priming an Automation Composition Type Definition on Participants
The Priming operation sends Automation Composition Type definitions and common property values to participants. Once an Automation Composition Type definition is primed, its property values can on longer be changed until it is de-primed.
2.5 De-Prime an Automation Composition Type Definition on Participants
This dialogue allows an Automation Composition Type Definition to be de-primed so that it can be deleted or its common parameter values can be altered.
2.6 Decommissioning an Automation Composition Type Definition in CLAMP
2.7 Reading Commissioned Automation Composition Type Definitions
3. Instantiation Dialogues
Instantiation dialogues are used to create, set parameters on, instantiate, update, and remove Automation Composition instances.
Assume a suitable Automation Composition Definition exists in the Commissioned Automation Composition Inventory. To get an Automation Composition instance running one would, for example, execute dialogues 2.1, 2.3, and 2.4.
3.1 Creating an Automation Composition Instance
Note that this dialogue creates the Automation Composition Instance in the Instantiated Automation Composition Inventory. The instance is sent to the participants using the process described in the dialogue in Section 2.3.
3.2 Updating Instance Specific Parameters on an Automation Composition Instance
3.3 Updating an Automation Composition Instance with a Configuration on Participants
3.4 Changing the state of an Automation Composition Instance on Participants
3.5 De-instantiating an Automation Composition Instance from Participants
3.6 Deleting an Automation Composition Instance
3.7 Reading Automation Composition Instances
3. Monitoring Dialogues
Monitoring dialogues are used to monitor and read statistics on Automation Composition Instances.
3.1 Reporting of Monitoring Information and Statistics by Participants
3.2 Viewing of Monitoring Information
3.2 Viewing of Statistics
3.3 Statistics Housekeeping
4. Supervision Dialogues
Supervision dialogues are used to check the state of Automation Composition Instances and Participants.