diff options
author | 2023-07-26 17:19:03 +0100 | |
---|---|---|
committer | 2023-08-09 10:05:34 +0000 | |
commit | a67a3533a3760939b53114c0f442685a7535670f (patch) | |
tree | fe4ee6cb593d82530e12280f2ad41f91a3ff59ec /docs/clamp/acm/design-impl/participants | |
parent | ae68131fa419692872d75fad406720418facc256 (diff) |
Update documentation for restart ACM
Issue-ID: POLICY-4782
Change-Id: If1f15b745fc98e5c7fccfc444dd14a78b4ec42e9
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
(cherry picked from commit 4f1c3755a6e13086693f8ce56cce5358211d749a)
Diffstat (limited to 'docs/clamp/acm/design-impl/participants')
-rwxr-xr-x[-rw-r--r--] | docs/clamp/acm/design-impl/participants/participant-intermediary.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst index 42ae2d5f..36b13197 100644..100755 --- a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst +++ b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst @@ -27,6 +27,7 @@ Inbound messages to participants - PARTICIPANT_PRIME: a message received from clamp-acm runtime server for a participant update with tosca definitions of clamp-acm - PARTICIPANT_STATUS_REQ: A status request received from clamp-acm runtime server to send an immediate ParticipantStatus from all participants - PROPERTIES_UPDATE: a message received from clamp-acm runtime server for updating the Ac instance property values +- PARTICIPANT_RESTART: a message received from clamp-acm runtime server with tosca definitions and the Ac instances to handle restarting Outbound messages ----------------- @@ -43,12 +44,14 @@ Design of a PARTICIPANT_REGISTER message - in AC-runtime ParticipantRegisterListener collects the message from Message Broker - if participant is not present in DB, it saves participant reference with status ON_LINE to DB - It triggers the execution to send a PARTICIPANT_REGISTER_ACK message to the participant registered +- if participant is present in DB and there are AC Definitions related to the Participant, + it triggers the execution to send a PARTICIPANT_RESTART message to the participant restarted Design of a PARTICIPANT_DEREGISTER message ------------------------------------------ - A participant is going to close and undeploys all AC-elements and send a PARTICIPANT_DEREGISTER message - in AC-runtime, ParticipantDeregisterListener collects the message from Message Broker -- if participant has AC-elements instance, it updates with UNDEPLOYED deployStatus +- It saves participant reference with status OFF_LINE to DB - It triggers the execution to send a PARTICIPANT_DEREGISTER_ACK message to the participant deregistered - Participant is not monitored. |