Dear All,

We would like to have the status of the last issue of the CEP problem.
Unfortunately, we don't have any answer-info about the issue last 2 weeks.
We don't know if there is an opened issue number for our problem, if it is
assigned to anyone for checking.

Also because at the end of month the FILAB node at PiraeusN will not be
available anymore, we have problem in deploy the ProtonOnWebAdmin,ProtonOnWeb
war files on our premises.

Would like to inform us about the status of our problem?,

Zacharias Papachristos,
Thanks,

΅

On Thu, Feb 4, 2016 at 10:21 AM, zahos pap <zacpapac04@gmail.com> wrote:

>
> ---------- Forwarded message ----------
> From: zahos pap <zacpapac04@gmail.com>
> Date: Thu, Feb 4, 2016 at 9:26 AM
> Subject: CEP installation problem
> To: tech@fractals-fp7.com, Dimitris Soukaras <dsoukaras@di.uoa.gr>,
> Orfeas-Dimitrios Theofanis <orfetheo@di.uoa.gr>
> Cc: super mario <mariosprotos@gmail.com>, Dimitris Karantonis <
> dkarantonis@gmail.com>, John Sokianos <ysokianos@gmail.com>
>
>
> Deal All,
>
> 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?
>
> Zacharias Papachristos,
>
>
>

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: zahos pap <zacpapac04@gmail.com>]