aboutsummaryrefslogtreecommitdiffstats
path: root/docs/clamp/acm/api-protocol/acm-participant-protocol.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/clamp/acm/api-protocol/acm-participant-protocol.rst')
-rwxr-xr-x[-rw-r--r--]docs/clamp/acm/api-protocol/acm-participant-protocol.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/clamp/acm/api-protocol/acm-participant-protocol.rst b/docs/clamp/acm/api-protocol/acm-participant-protocol.rst
index b4755ae2..ee9213cf 100644..100755
--- a/docs/clamp/acm/api-protocol/acm-participant-protocol.rst
+++ b/docs/clamp/acm/api-protocol/acm-participant-protocol.rst
@@ -19,11 +19,13 @@ Participant Registration and De-Registration
--------------------------------------------
Participant Registration is performed by a Participant when it starts up. It registers its ID and the ACM Element Types it supports with the ACM runtime.
+In a scenario where Participant has been restarted, ACM runtime have to provide all Primed ACM Definition and Deployed ACM instances of the Participant sending a Restart message.
+
.. image:: ../images/system-dialogues/RegisterParticipant.png
-Participant Deregistration is performed by a Participant when it shuts down. It deregisters its ID and type with the ACM runtime. The participant should already have cleared down all its' ACM Element instances and set their states to “Not In Service”.
+Participant Deregistration is performed by a Participant when it shuts down. It deregisters its ID and type with the ACM runtime.
.. image:: ../images/system-dialogues/DeregisterParticipant.png