Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4569

FIWARE.Request.Tech.Apps.ApplicationMashup.ProblemConnectingToCustomOrion

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Apps
    • HD-Enabler:
      Wirecloud

      Description

      Hi Lino, I'm forwarding your request to
      fiware-incense-coaching@lists.fi-ware.org . fiware-coaches@lists.fi-ware.org
      exists for other purposes.

      Kind regards,
      P.

      Pasquale Andriani
      Direzione Ricerca e Innovazione - Research & Development Lab
      pasquale.andriani@eng.it

      Engineering Ingegneria Informatica spa
      Via Riccardo Morandi, 32 - 00148 Roma
      Tel. +39-06.87594138
      Mob. +39 3924698746
      Fax. +39-06.83074408
      www.eng.it

      On Tue, Jul 14, 2015 at 11:21 AM, Lino Prunella - Tera srl <
      nicola.prunella@terasrl.it> wrote:

      > Hi.
      >
      > I have a running instance of the Orion Context Broker GE in a CentOS 6.6
      > server. Apparently it's working fine: I can make REST queries through a web
      > REST Client, make entities with updateContext operation and retrieve
      > information about them with queryContext.
      >
      >
      >
      > The thing is that I am trying to link Wirecloud GE with my Orion instance
      > using the NGSI-Source widget. I have updated the widget's settings with my
      > instance URL as follows:
      >
      >
      >
      > NGSI Server : http://my_ip:1026 where my_ip=192.168.1.24
      >
      >
      >
      > Entity Id Filter: Room*
      >
      >
      >
      > Ngsi-proxy is up and running on port 3000
      >
      >
      >
      > The wirecloud_instance is up and running and it shows on screen :
      >
      >
      >
      > "POST /cdp/http/192.168.1.24:1026/ngsi10/queryContext? HTTP/1.1" 422 42
      >
      >
      >
      > in meanwhile on my WIRECLOUD app : Fail querying the server:
      > InvalidResponse: Unexpected error code: 422
      >
      >
      >
      > I have also deactivated the firewall and checked the port 3000.
      >
      >
      >
      > Thank you
      >
      >
      >
      > Best regards
      >
      >
      >
      > Lino Prunella
      >
      > Software engineering
      >
      > Tera srl
      >

      _______________________________________________
      Fiware-incense-coaching mailing list
      Fiware-incense-coaching@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-incense-coaching

        Issue Links

          Activity

          Hide
          backlogmanager Backlog Manager added a comment -

          Assignee before migration = Álvaro Arranz

          Show
          backlogmanager Backlog Manager added a comment - Assignee before migration = Álvaro Arranz
          Hide
          backlogmanager Backlog Manager added a comment -

          Original time span = 16 days, 22:06:41

          Show
          backlogmanager Backlog Manager added a comment - Original time span = 16 days, 22:06:41

            People

            • Assignee:
              aarranz Álvaro Arranz
              Reporter:
              pandriani Pasquale Andriani
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: