We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

aarranz's profile - activity

2018-07-17 12:56:11 +0100 answered a question perseo-core

I recommend you to use the any of the already provided docker images.

First, Telefónica provides the current "stable" images. See this answer for more details.

We are working on improving Perseo and having it up to date. This version is available at Docker Hub on the FIWARE organization. In this regard, Perseo has been updated to use a recent version of Esper, NodeJS, Java, ... and now comes with support for NGSIv2. If you want to test this version instead, you can use the following docker-compose.yml file:

version: '3.4'
services:

    perseo-core:
        image: fiware/perseo-core
        environment:
            - PERSEO_FE_URL=http://perseo:9090
            - MAX_AGE=6000
        depends_on:
            - mongo

    perseo:
        image: fiware/perseo
        ports:
            - 9090:9090
        depends_on:
            - perseo-core
        environment:
            - PERSEO_MONGO_ENDPOINT=mongo
            - PERSEO_CORE_URL=http://perseo-core:8080
            - PERSEO_LOG_LEVEL=info
            - PERSEO_ORION_URL=http://orion:1026/
            - PERSEO_SMTP_HOST=smtp.gmail.com
            - PERSEO_SMTP_PORT=465
            - PERSEO_SMTP_SECURE=true
            - PERSEO_SMTP_AUTH_USER=XXXXX@XXXXX.com
            - PERSEO_SMTP_AUTH_PASS=XXXXX

    mongo:
        image: mongo:3.4
        volumes:
            - ./oriondata:/data/db
        command: --nojournal

    orion:
        image: fiware/orion
        depends_on:
            - mongo
        ports:
            - 1026:1026
        command: -dbhost mongo
2018-04-09 12:25:34 +0100 answered a question Fiware Marketplace

The marketplace should be working. I recommend you to create a new question providing more details (error message, screenshots, etc...) about the problems you are facing so we are able to analyze them and provide you a better response.

As alternative, you can search WireCloud components on github. Usually, you will have to enter each repository and browser the available releases. The wgt file will be on the release details (e.g. ngsi-source v4.0.0).

2018-01-17 09:57:21 +0100 answered a question How to connect marketplace in new installation Wirecloud?

Currently, the marketplace on FIWARE Lab should be working.

Regarding, configuring a custom instance. After installing WireCloud, you will have to add a marketplace is using the following details:

Take a look into the user guide for more details.

2017-01-18 14:03:23 +0100 answered a question WIRECLOUD AND ECLIPSE

Sorry, there is not a video tutorial on how to use the plug-in, but there is a step-by-step guide on how to use it (We've detected some problems with the screenshots, now fixed). Please, take a look and don't hesitate to request more details about how to use it.

If you prefer, you can use our grunt-init templates:

those templates will create a filesystem structure for building widgets and operators using grunt. If you select this option, you will be able to use your favourite IDE.

2016-07-29 17:00:15 +0100 received badge  Enthusiast
2016-07-18 16:40:50 +0100 answered a question Internal server error 500 - Mashup Wirecloud

The problem seems to be that you tried to install a mashup with embedded components (widgets or operators). One of those components has a config.xml file that cannot be parsed by WireCloud. We have removed support for the old https://wirecloud.conwet.fi.upm.es/ns/template# description format, so probably that component is using it for its config.xml file.

We are working on fixing the internal server error (WireCloud should provide a better message in those cases). But the mashup containing the component should be fixed by upgrading the problematic component (See this StackOverflow thread for more info). The error report doesn't contain the contents of the requests, so please, let's us know if you were installing an offering from the FIWARE Lab Store/Marketplace, if you downloaded the mashup from the documentation, ... or any information you think useful so we are able to fix it :-)