...
1.1 Commissioning an Automation Composition Type Definition using the ACM REST Interface
The documentation of future releases of the system will describe how the Design Time functionality interacts with the Runtime commissioning API.
| PlantUML Macro |
|---|
@startuml participant REST participant ACM_Runtime database Commissioned_ACM_Inventory REST -> ACM_Runtime: Commission Automation Composition Type Definition ACM_Runtime -> Commissioned_ACM_Inventory: Store Automation Composition Type Definition ACM_Runtime -> ACM_Runtime: Trigger Priming of Automation Composition Type Definition ACM_Runtime -> REST: Type Definition Commissioned @enduml |
...
| PlantUML Macro |
|---|
@startuml participant SDC participant Policy_Distribution participant ACM_Runtime database Commissioned_ACM_Inventory SDC -> Policy_Distribution: [DMaaP] CSAR containing Automation Composition Type Definition Policy_Distribution -> ACM_Runtime: [REST] Commission Commission Automation Composition Type Definition ACM_Runtime -> Commissioned_ACM_Inventory: Store Automation Composition Type Definition (See 1.1) ACM_Runtime -> ACM_Runtime: Trigger Priming of Automation Composition Type Definition ACM_Runtime -> Policy_Distribution: [REST] Type Definition Commissioned Policy_Distribution -> SDC: [DMaaP] Deployment Completed @enduml |
1.3
...
Updating an Automation Composition Type Definition
This dialogue sets the values of common properties. The values of the common properties may be set, updated, or deleted at will, as this dialogue saves the properties to the database but does not send the definitions or properties to the participants. However, once an Automation Composition Type Definition and its properties are primed (See Section 1.4), the properties cannot be changed until the Automation Composition type definition is de-primed (See Section 1.5).
...