[Fiware-tech-help] [frontierCities2]

[Yesnier Bravo]

Hello,

We write again about this issue. hope to clarify a bit more.

We can query the Orion CB with NGSIv1 or NGSIv2 as this is fully supported
by Orion, As Orion is intended to be the "API proxy" to the EnergySequence
Services for customer CRMs then we support NGSIv2.

The issue is that Orion is not forwarding the entity creation to the
porfolio management provider (i.e. EnergySequence) as it does with entity
update operation once we have register a product.

We have read that forwarding only works with NGSIv1 APIs and thus we
implemented that versión for the internal communication
with EnergySequence. Nevertheless, the online documentation might not be
updated and we are asking if there is any known problem (and workaround)
with the data context creation forwarding in Orion.

I will post this message to the support email list also, so you can answer
that way.

Thank you in advance.

Best,

El mar., 10 jul. 2018 a las 12:45, Ailema Vázquez García (<
avazquez at bettergy.es>) escribió:

> We have created a Context Provider that exposes an NGSI api with the
> following entry points
> url (r '^ queryContext', views.queryContext.as_view ()),
> url (r '^ updateContext', views.updateContext.as_view ()),
>
> Starting from the fact that we have registered an entity in Orion, and we
> verify that it is actually in the table registrations of the database.
>
> If we try to execute the following queries to obtain the information, we
> obtain it correctly. Checking that Orion has registered them with our
> supplier and forwards the query to it.
> GET /v1/contextEntities/5b43f945ccfc0348246283dc
> GET /v2/entities/5b43f945ccfc0348246283dc
>
> But, if we execute any of the following queries to update the data of the
> entity, they do not redirect to the Context Provider, and we obtain the
> following answers.
> PUT /v1/contextEntities/5b43f945ccfc0348246283dc/attributes
> {
>     "errorCode": {
>         "code": "404",
>         "reasonPhrase": "No context element found",
>         "details": "5b43f945ccfc0348246283dc"
>     }
> }
> PATCH /v2/entities/5b43f945ccfc0348246283dc/attrs
> {
>     "error": "NotFound",
>     "description": "The requested entity has not been found. Check type
> and id"
> }
>
> The only way we have been able to update the information is through the
> following query, which redirects correctly and updates.
> POST /v1/updateContext
> We were wondering if we are avoiding something so that just like when we
> consult the information, the update works well regardless of the query that
> is executed.
>
> Regards
> I am aware
>
-- 
Yesnier Bravo

IT Director · CIO


*t*: +34 952 025 789 <%2B34%20951334698>
*a*: Av. Juan López de Peñalver 17, 29590 Málaga
<https://www.google.es/maps/place/Av.+Juan+L%C3%B3pez+de+Pe%C3%B1alver,+17,+29590+M%C3%A1laga>
*w*: www.bettergy.es *e*: ybravo at bettergy.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180711/81612880/attachment.html>