fiware - Can't notify from Orion context Broker v2 to Cepheus context broker v1 -


despite of set attrsformtat legacy it's not working, missing parameter: updateaction

any suggestions?

thanks.

edited: try in million ways , can't handle getting same error.

enter image description here

enter image description here

enter image description here

i not expert in cepheus broker have bit of experience playing cepheus cep , orion context broker in fiware ecosystem, maybe can useful.

according official documentation of cep, should deploying cepheus broker before orion context broker instead after. know both speak same ngsi api should same, not sure that. particular reason why deploying these components in order?

enter image description here

i make little experiment using official docker images of cepheus broker , orion context broker, creating context subscriptions through v1 , v2 orion apis. same error on cepheus broker logs.

then proved this little app made fiware fellows, can use debbuging ngsi context subscriptions. tried v1 , v2 subscriptions, legacy , no legacy in v2 , of produces "updateaction" field in request. realized far know, within ngsi api methods service receives updateaction parameter updatecontext service.

may cepheus can not connect orion context broker through context subscription mechanism. maybe he's waiting context update instead context change notification.

sorry not being of more help.

regards!


Comments

Popular posts from this blog

resizing Telegram inline keyboard -

command line - How can a Python program background itself? -

php - "cURL error 28: Resolving timed out" on Wordpress on Azure App Service on Linux -