Does cygnus supports NGSI v2 specifications? I tried to do subscriptions following the NGSI v2 format but it is not working.
Thanks in advance for your help.
Related
Despite of set attrsFormtat to legacy it's not working, I get Missing parameter: updateAction
Any suggestions?
Thanks.
EDITED: I try it in a million ways and i can't handle this always getting the same error.
I am not an expert in Cepheus Broker but I have a bit of experience playing with Cepheus CEP and Orion Context Broker in FIWARE ecosystem, maybe I can be useful.
According to the official documentation of CEP, you should be deploying Cepheus Broker before Orion Context Broker instead after. I know that both speak the same NGSI API so it should be the same, but I am not completely sure about that. Any particular reason why you are deploying these components in that order?
I make a little experiment using official Docker images of Cepheus Broker and Orion context Broker, creating context subscriptions through v1 and v2 Orion APIs. The same error as you on Cepheus Broker logs.
Then I proved with this little app made by Fiware fellows, that you can use for debbuging NGSI context subscriptions. I tried with v1 and v2 subscriptions, with legacy and no legacy in v2 and any of this produces a "updateAction" field in the request. Then I realized that as far as I know, within the NGSI API methods the only service that receives the updateAction parameter is the updateContext service.
May be Cepheus can not connect with Orion Context Broker through Context Subscription mechanism. Maybe he's waiting for a context update instead a context change notification.
Sorry for not being of more help.
Regards!
You are trying to make Orion send a notifyContext request to the updateContext endpoint of Cepheus CEP. This cannot work as an updateContext request is expected to contain an updateAction field in the payload according to the NGSI v1 protocol.
Cepheus CEP expects notifications from subscriptions to be done to its notifyContext endpoint.
Moreover Cepheus CEP will send its own subscription requests to Orion when properly setup (you must declare Orion as a provider in the CEP configuration). It will ask Orion to send back notification to the correct endpoint.
Finaly, you cannot make the subscription on behalf of Cepheus CEP like you are trying to do: Cepheus CEP will only accepts notifications for the subscriptions it made itself because it validates the subscription ids of all notification it receives.
I'm trying to use Wirecloud the latest version available for a simple mashup project. I'm using the ngsi-source operator to retrieve data from Orion, but this is not possible because I often encounter an NGSI Proxy Connection Error (504 Gateway Timeout).
I tried with different installations of the NGSI Proxy in different servers and I have noticed that I have a 200 status in the inner REST calls made by the ngsi-source operator, only when the NGSI Proxy is reachable from the Wirecloud server installation (django server).
When the proxy is reachable only from my browser (local machine), I encounter the 504 status.
The NGSI Proxy has to be reachable from the Wirecloud installation?
Thanks in advance for the answers.
Currently, the NGSI proxy has to be reachable from the WireCloud instance. The url you were seeing (http://<wirecloud domain>/cdp/http/<ngsi-proxy domain>/eventsource) is caused by the use of the Cross Domain Proxy. We developed the NGSI proxy service to allow cross domain requests from browsers and the event source endpoint cannot be used without a direct connection from the client side, so I've opened a ticket in the github repo to solve this bug.
I need NGSI proxy over http. Is there any instance of NGSI Proxy over http?
Alternatively, Is it possible to install NGSI Proxy on my own server?
Many thanks.
We have restored the ngsiproxy.lab.fiware.org machine, this machine supports both protocols http and https.
Anyway, you can create your own ngsi-proxy instance downloading it from github.
I'm trying to make a mashup public. This mashup uses Orion Context Broker to draw some PoI in a map. I've looked at documentation on github and tried changing port to 10026 and disabling the use of credentials, but I don't get any PoIs this way.
The NGSI Source Operator settings are:
NGSI server URL: http://orion.lab.fiware.org:10026/
NGSI proxy URL: https://ngsiproxy.lab.fiware.org
Use the FIWARE credentials of the user : disabled
Is there any way to achieve this?
As stated in the NGSI source operator documentation (version 3.0.3), using the 10026 port was a hack for supporting public workspaces. That hack doesn't work anymore.
Version 3.0.4 of the NGSI Source operator adds support for using the credentials of the workspace owner instead of using the credentials of the logged user (through a new preference: Use the FIWARE credentials of the workspace owner). This can be used for creating a workspace and make it public.
While attempting to build a cluster for APIM the only documentation I've been led to is:
http://docs.wso2.org/display/Cluster/Creating+a+Cluster
Which references tribes instead of hazelcast.
I've found some other blogs with hazelcast information but nothing from WSo2.
Does anyone know of actual WSo2 doc that defines their needed settings for clustering under Hazelcast?
CLustering for the new version of WSO2 API Manager is her
http://docs.wso2.org/display/CLUSTER420/Overview
Found it under carbon 4.2.0 documentation:
http://docs.wso2.org/pages/viewpage.action?pageId=29918203