public:smart2b:home

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
public:smart2b:home [2024/03/05 15:25]
jsanchez_odins.es [Integrating Partner FAQ] 		public:smart2b:home [2024/10/09 08:53] (current)
Line 165: Line 165:
 ### Verification of Context Source Registrations ### Verification of Context Source Registrations
  
-After registering the Context Source it can be checked if the registrations process is successful --- i.e. the integrating partner software component that receives the messages from the NGSI-LD Broker in WP3 Smart2B Platform is supposed to be registered before.+After registering the Context Source it can be checked if the registrations process was successful --- i.e. the integrating partner software component that receives the messages from the NGSI-LD Broker in WP3 Smart2B Platform is supposed to be registered before actuation can carry over from the WP3 Smart2B platform all the way down to the building equipment.
  
 The following POSTMAN collection can be employed in order to verify if the Context Source Registration took place successfully. The following POSTMAN collection can be employed in order to verify if the Context Source Registration took place successfully.
Line 185: Line 185:
 ``` ```
  
 +- For more information about the high-level architecture and flow of Actuation, please refer to [Low level interaction for actuation with NGSI-LD Broker](#low_level_interaction_for_actuation_with_ngsi-ld_broker)
  
 ## Smart2B platform resource monitoring processes ## Smart2B platform resource monitoring processes
Line 444: Line 444:
     - E.g. Query with a GET request the same ACTUATOR entity and look at the `command` attributes and their info.     - E.g. Query with a GET request the same ACTUATOR entity and look at the `command` attributes and their info.
     - Query the broker itself to get relevant information about the Context Source registration for its entities --- should get the partner IP address and TCP port.     - Query the broker itself to get relevant information about the Context Source registration for its entities --- should get the partner IP address and TCP port.
 +- Check that a Context Source Registration exists for the particular entity in the Broker. For this, follow [these instructions](#verification_of_context_source_registrations) --- otherwise no actuation will happen when the command reaches the broker.
 - If the context source registration is not propertly done --- get in contact with the relevant pilot owner. (For SCML it would be EDP SEL, for AOC its either ODINS or EB, for ABL its Martin Kaufman, for CJC is EB, for ARA is EDP Miguel) - If the context source registration is not propertly done --- get in contact with the relevant pilot owner. (For SCML it would be EDP SEL, for AOC its either ODINS or EB, for ABL its Martin Kaufman, for CJC is EB, for ARA is EDP Miguel)
 - If the context source is successfully registered, when the commands are not reaching the building equipment, get in contact with the relevant pilot owner. - If the context source is successfully registered, when the commands are not reaching the building equipment, get in contact with the relevant pilot owner.
  
  
-## Consult Smart2B platform entities by type+## Get a complete list of Smart2B platform entities by type
  
 Below is attached a JSON file that contains a Postman collection with the necessary requests to recover all the information corresponding to the entities of each type that are registered on the Smart2B platform: Below is attached a JSON file that contains a Postman collection with the necessary requests to recover all the information corresponding to the entities of each type that are registered on the Smart2B platform:
  • public/smart2b/home.1709648700.txt.gz
  • Last modified: 2024/10/09 08:35
  • (external edit)