fiware

How a widget can figure out the user logged in WireCloud?

偶尔善良 提交于 2019-12-05 16:34:00
As widget developer, I would like to show different information in my widget depending of the user that is logged in WireCloud. How could the widget figure out who is the user that is logged in WireCloud when it is loaded? WireCloud provides support for accessing context information currently available through the MashupPlatform API. Currently WireCloud provides both the username and the full name of the user: var username = MashupPlatform.context.get('username'); var realname = MashupPlatform.context.get('fullname'); Take a look into the "3.1.5. Accessing context information" section of the

Error Cepheus broker not forwards updates to Cepheus CEP

喜夏-厌秋 提交于 2019-12-04 19:27:06
I use Cepheus GE for my use case and I enabled it in the multi tenant mode and uploaded my config.json file to it, But when I start to send updates to the Cepheus broker in order to forward them to the CEP, the Cepheus broker just receives the updates but doesn't forward them to the Cepheus cap as it couldn't recognize the service and service-path that are set in the config.json . And when I tried to send my updates directly to the Cepheus-CEP, it accepted them and processed them successfully. So I wonder why the Cepheus broker cannot recognize the Fiware-service when it's enabled in the multi

login to fiware GE using putty (Windows) - what credentials?

﹥>﹥吖頭↗ 提交于 2019-12-04 15:57:43
I have a FiWare GE instance setup, with a security group, key, and IP all configured. I also have Putty setup to allow me to connect to the instance. My problem is that when I connect I get asked for login information. I've tried my login credentials for Fi-Ware but that doesn't work. There are no other users associated, so I'm not sure what I'm supposed to use. There doesn't seem to be any (obvious) way to create users and associate them with an application either. Are there default login credentials I should be aware of? Do I need to make a user specifically for my instance? Depending on the

ContextBroker subscriptions Error

寵の児 提交于 2019-12-04 15:09:57
I've updated cygnus from version 0.13 to 1.7.0 by installing NGSI following this tutorial: https://github.com/telefonicaid/fiware-cygnus/tree/master/cygnus-ngsi Error the subscription [ { "id": "59d38a92dbaa1e477aef9c00", "description": "A subscription to get info about pruebas", "status": "failed", "subject": { "entities": [ { "id": "pruebas", "type": "pruebas" } ], "condition": { "attrs": [ "pressure" ] } }, "notification": { "timesSent": 2, "lastNotification": "2017-10-03T13:03:43.00Z", "attrs": [ "temperature", "pressure" ], "attrsFormat": "legacy", "http": { "url": "http://localhost:5050

Send LoRa measures to Fiware IOT agent via MQTT

北慕城南 提交于 2019-12-04 07:05:42
问题 I have LoRa sensors which send measures with Cayenne LPP format payload. My Gateway(LOrank8v1) catches these packets and converts them to UDP. In the gateway there is a service(lora-gateway-bridge) which converts the packets from UDP to TCP/MQTT. Then the MQTT packets are published to the mosquitto MQTT broker in the cloud. Then i run lora-server and lora-app-server services in order to decrypt,decode and deduplicate the packets. Then i publish the decrypted information to the MQTT broker

Orion Context Broker works half of the times

北战南征 提交于 2019-12-04 04:59:38
问题 I've installed Orion Context Broker 0.23.0 and it behaves rare: it only works half of the times. For instance, when trying to retrieve the version I get this error message: $ curl "http://localhost:1026/version" curl: (52) Empty reply from server $ curl "http://localhost:1026/version" <orion> <version>0.23.0</version> <uptime>15 d, 22 h, 13 m, 18 s</uptime> <git_hash>f5d76a6f11736d52402e63a4aa0ba990bff7f5eb</git_hash> <compile_time>Fri Jul 10 13:21:42 CEST 2015</compile_time> <compiled_by

PEP proxy config file for integration of IDM GE, PEP proxy and Cosmos big data

本秂侑毒 提交于 2019-12-04 04:13:37
问题 I have a question regarding PEP proxy file. My keystone service is running on 192.168.4.33:5000. My horizon service is running on 192.168.4.33:443. My WebHDFS service is running on 192.168.4.180:50070 and i intend to run PEP Proxy on 192.168.4.180:80 But what i don't get is what should i put in place of config.account_host? Inside mysql database for keyrock manager there is "idm" user with "idm" password and every request i make via curl on Identity manager works. But with this config: config

ECONNRESET when opening a large number of connection in small time period

ぐ巨炮叔叔 提交于 2019-12-02 14:03:28
问题 I have situation where I want to create large number of entities on orion. I am using docker version of Orion and mongo with this docker-compose. version: "3" services: mongo: image: mongo:3.4 volumes: - /data/docker-mongo/db:/data/db - /data/docker-mongo/log/mongodb.log:/var/log/mongodb/mongod.log command: --nojournal orion: image: fiware/orion volumes: - /data/docker-mongo/log/contextBroker.log:/tmp/contextBroker.log links: - mongo ports: - "1026:1026" command: -dbhost mongo Now problems

Rush installation and integration with Orion Context Broker

泄露秘密 提交于 2019-12-02 13:09:05
问题 After having running the listener and one time a consumer in the Rush, I run: contextBroker -rush localhost:5001 I made sure to use Orion 0.17 instead of 0.14 and what It's shown after enter to the /version url is: <orion> <version>0.17.0</version> <uptime>0 d, 0 h, 12 m, 14 s</uptime> <git_hash>127793ff921b37a6a570cd315ddce9a3ec541ccf</git_hash> <compile_time>Fri Nov 28 09:41:22 CET 2014</compile_time> <compiled_by>fermin</compiled_by> <compiled_in>centollo</compiled_in> </orion> Now Rush

Error with Fiware-Cygnus installation via yum

泄露秘密 提交于 2019-12-02 11:23:41
问题 i am trying to install the Fireware Cygnus via yum yum install cygnus-ngsi But in the middle i got some erros. Transaction Check Error: file /usr/cygnus/init.d/cygnus from install of cygnus-common-1.2.0-0.gbd4790e.x86_64 conflicts with file from package cygnus-0.13.0-0.g0c6765f.x86_64 -...... i checked the /usr directory but there is nothing with /cygnus/init.d and so on... It is possible that there have been something before but who knows. I also tried to clean yum repo but the error still