[Fiware-tech-help] CEP and orion instance moved to Spain2 does not work

[Liu, Zhiying]

Dear Mr. Pacheco,

Thank you very much for your reply.

Actually for the orion question I asked it in Stack Overflow with tag fiware-orion last week, somehow I got comment like: "what do you want? a coffee or something? make a break and then you'll be ok after 30 minutes.", something like that. I deleted my question there since I was not feeling comfortable with such comments.

I will ask the cep question on another link.

Best regards,
Zhiying



Am 04.05.2015 um 15:11 schrieb MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>:

Dear Dr. Liu,

Please contact the GE support directly. The instructions are on our public catalogue. for your convinience I put you the direct links to both:


  *   Orion: http://catalogue.fiware.org/enablers/publishsubscribe-context-broker-orion-context-broker ("Ask in Stack Overflow with tag fiware-orion")
  *   CEP: http://catalogue.fiware.org/enablers/complex-event-processing-cep-proactive-technology-online (contact TALI at il.ibm.com<mailto:TALI at il.ibm.com>)

I hope that it helps

Miguel




El 01/05/2015 a las 21:51, Liu, Zhiying escribió:
Dear Sir/Madam,

I have an CEP instance and an orion pub sub instance running on Spain node. The CEP accept some input events, produces output events as defined, and send them to orion instance. And one can query the events from the pub-sub node. Every thing worked fine before my orion node was deleted.
As suggested by FIWARE society, I am now moving my things to Spain2.

On Spain2 node I have:

1. created a new CEP instance, and imported my project definition to the new instance,
2. created an orion pub-sub instance and have done the same things that I have done before (fortunately I have documented the steps that made things work).

However I have problems on both new instances.

1. For CEP, I get "OK" response for change definition and change state of my definition (start, stop).  But for push event like this:
curl -v -X POST http://130.206.116.4:8080/ProtonOnWebServer/rest/events
Content-Type: application/json
{"Name":"Generated","component":"wind","value":"1308.16","gtime":"20150121"}
I always get this status error:  500 Error Interno del Servido
The exact same command to the old instance works fine. The same definition is exported from the old instance and imported to the new one.

2. For Orion, I can login and start the context broker like this: “/etc/init.d/contextBroker start”.
But when I send event definition like this:
Command: POST
(curl 130.206.116.6:1026/v1/updateContext -s -S --header 'Content-Type: application/xml' -d @- | xmllint --format - ) <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<updateContextRequest>
   <contextElementList>
    <contextElement>
                 <entityId type="EnergyWarning" isPattern="false">
                        <id>NotMatch</id>
                 </entityId>
                <contextAttributeList>
           <contextAttribute>
            <name>EventId</name>
                  <contextValue>2c67baff-402d-4a48-b22d-e2f5fc743499</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>DetectionTime</name>
                  <contextValue>19/11/2014-11:02:05</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>difference</name>
                  <contextValue>600.0</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>Cost</name>
                  <contextValue>0.0</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>Certainty</name>
                  <contextValue>0.0</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>Name</name>
                  <contextValue>EWarning</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>OccurrenceTime</name>
                  <contextValue>19/11/2014-11:02:05</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>component</name>
                  <contextValue>biogas2</contextValue>
         </contextAttribute>
           <contextAttribute>
            <name>Duration</name>
                  <contextValue>0.0</contextValue>
         </contextAttribute>
      </contextAttributeList>
    </contextElement>
   </contextElementList>
   <updateAction>APPEND</updateAction>
</updateContextRequest>

The response status is ok, but the error message is:

{ "orionError" : { "code" : "400", "reasonPhrase" : "Bad Request", "details" : "service '/v1/updateContext' not found" } }

This exact same command (except ip address) works for my old Orion instance.

Any help would be highly appreciated!
With best regards,

Dr. Zhiying Liu
IT-Softwareentwicklung

QSC AG
Mathias-Brüggen-Straße 55
50829 Köln

Telefon: 0221 6698 - 497
E-Mail: Zhiying.Liu at qsc.de<mailto:Zhiying.Liu at qsc.de>
Internet: www.qsc.de<http://www.qsc.de/>

Sitz der Gesellschaft: Köln - Amtsgericht Köln HRB-Nummer 28281
Vorstand: Jürgen Hermann (Vorsitzender), Stefan A. Baustert
Vorsitzender des Aufsichtsrats: Dr. Bernd Schlobohm





_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help at lists.fi-ware.org<mailto:Fiware-tech-help at lists.fi-ware.org>
https://lists.fi-ware.org/listinfo/fiware-tech-help



--

Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 6
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                         e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

Follow FIWARE on the net

        Website:  http://www.fiware.org<http://www.fiware.org/>
        Facebook: https://www.facebook.com/eu.fiware
        Twitter:  http://twitter.com/Fiware
        LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150504/2d1cfb67/attachment.html>