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

FIWARE.Request.Tech.Data.CEP.Running CEP in a Docker

    Details

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

      Description

      Hi Julian,

      1. Isn't it related to issue #14?
      2. PUT is used to update existing definition. So if you already POST
      definition with the same name, you should use a PUT, but if not, you
      should use a POST. This POST/PUT add/update definition in the definition
      repository.
      If you used the Docker installation, then you need to configure the
      definitions-repository, the place the CEP should put definition files, as
      explained in the Installation guide.

      Best regards,
      Tali

      Tali Yatzkar Haham
      Smart Decision Solutions
      IBM Research - Haifa, Israel
      tali@il.ibm.com 972-4-8296320

      From: Julian Krenge <julian.krenge@gmail.com>
      To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
      Date: 29/10/2015 11:47 PM
      Subject: Running CEP in a Docker

      Hey Tali,

      thanks to the help of you guys, I was able to set up a instance of PROTON
      on one of our machines. It?s running with Docker on ubuntu in its own
      screen, the end of the start log reads:

      INFO: init: done initializing singletons , starting the servers...
      Oct 29, 2015 9:32:39 PM com.ibm.hrl.proton.server.adapter.OutputServer run
      INFO: Proton output server started, listening on output port: 3302
      Oct 29, 2015 9:32:39 PM com.ibm.hrl.proton.server.adapter.InputServer run
      INFO: Proton server Started, listening on port: 3002
      Oct 29, 2015 9:32:39 PM org.apache.catalina.startup.HostConfig deployWAR
      INFO: Deploying web application archive
      /var/lib/tomcat7/webapps/ProtonOnWebServerAdmin.war
      Oct 29, 2015 9:32:40 PM
      com.ibm.hrl.proton.admin.webapp.ProtonAdminServletContextListener
      contextInitialized
      INFO: initializing ProtonAdminServletContextListener
      Oct 29, 2015 9:32:40 PM
      com.ibm.hrl.proton.admin.webapp.ProtonAdminServletContextListener
      contextInitialized
      INFO: created popertiesFileInputStream =
      java.io.ByteArrayInputStream@716fd193
      Oct 29, 2015 9:32:40 PM
      com.ibm.hrl.proton.admin.webapp.ProtonAdminServletContextListener
      contextInitialized
      INFO: getServletContext().getRealPath =
      /var/lib/tomcat7/webapps/ProtonOnWebServerAdmin/
      SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
      SLF4J: Defaulting to no-operation (NOP) logger implementation
      SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
      details.
      Oct 29, 2015 9:32:41 PM org.apache.catalina.startup.HostConfig
      deployDirectory
      INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
      Oct 29, 2015 9:32:41 PM org.apache.coyote.AbstractProtocol start
      INFO: Starting ProtocolHandler ["http-bio-8080"]
      Oct 29, 2015 9:32:41 PM org.apache.catalina.startup.Catalina start
      INFO: Server startup in 8523 ms

      So I would say this looks good.

      From reading the docs and info there, I would assume the Admin Interface
      is at port 8080. However, when I try to curl it, I get:

      ubuntu@ip-172-31-1-99:~$ curl
      http://localhost:8080/AuthoringTool/Main.html
      curl: (7) Failed to connect to localhost port 8080: Connection refused

      Any idea what I might be doing wrong?

      Also, directly a second question:

      We have been working with the test instances already to define some rules.
      There, we exported a JSON with the config. Could we put this JSON back in
      programatically using this API?

      PUT /

      {CEP_Admin}

      /resources/definitions/

      {definition_name}

      Thanks
      ? Julian

      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: Tali Yatzkar-Haham <TALI@il.ibm.com>]

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            TALI Fabiana Fournier
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: