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

FIWARE.Request.Tech.Data.CEP.Re: BeeZon CEP Problem

    Details

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

      Description

      Dear Tali,

      could you kindly help this FRACTALS accelerator SME with this issue?

      Many thanks,

      ilknur (Fractals coach)

      --------------------------------------------------

      From: Romero, Javier
      Sent: Friday, February 19, 2016 8:10 AM
      To: FRACTALS coach (fiware-fractals-coaching@lists.fi-ware.org) (fiware-fractals-coaching@lists.fi-ware.org)
      Cc: 'zahos pap'
      Subject: [Fractals] BeeZon CEP Problem

      Dear coachers

      We have the following issue from BeeZon project related with CEP

      After the FILAB PiraeusN node technical suggestions ( issue 5003 : Romero Javier assigned to Tali Yatzkar Haham)
      we had performance issues (the CEP Authoring Tool is extreme too slow)
      we install the CEP application outside the FILAB on our premises.
      We get the code from Github and using the docker we build the github docker file.

      The AuthoringTool works fine in http://51.254.200.160:8080/AuthoringTool/Main.html

      We have no more delays and we can use the GUI to create our filters on CEP.
      However the administration part (ProtonOnWeb) does not work.
      Exporting a definition of a project to the server is not possible.
      No matter how many times it is attempted the number of definitions has as result
      []. meaning null.
      http://51.254.200.160:8080/ProtonOnWebServerAdmin/resources/definitions/
      Trying through the REST Administration API and trying to post a definition does not work either unfortunately,as we get server errors.

      The same work we made on a FILAB instance with IP 185.23.171.123 ,with docker with the same results.
      (The AuthoringTool works however it is again too slow in compare with the CEP on 51.254.200.160
      and the ProtonOnWeb application does not work).

      In order to overcome this as we are close to delivery we had to restore an old version of CEP in FI Lab (from the image cep-r3.3.3-img),
      where the ProtonOnWebServer/Admin part works through the REST Admin API but not the AuthoringTool.
      REST Api: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29
      This instance works on http://185.23.171.53:8080/ProtonOnWebServerAdmin/resources/definitions/

      So now, we have 2 instances for CEP,one on custom premises to produce the definition, and one on FI Lab where ProtonWebServer works and is used from our application.

      We request your help as soon as possible for a working version of CEP where all the modules work as they should on a single instance of CEP and not having to rely on 2 instances where each of them is responsible for a module.
      Is it possible to have a problem with ProtonOnWebAdmin or ProtonOnWeb war artifacts?

      The email o the BeeZon contact is: zacpapac04@gmail.com and is also in CC

      Thanks for the support

      Best Regards
      ---------------------------------
      A. Javier Romero Negrín
      MRE - Atos Research & Innovation

      www.atos.net<http://www.atos.net/>
      _______________________________________________
      Fiware-fractals-coaching mailing list
      Fiware-fractals-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-fractals-coaching
      [Created via e-mail received from: "Romero, Javier" <javier.romero@atos.net>]

        Issue Links

          Activity

            People

            • Assignee:
              urishani Uri Shani
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: