Hi Ahmed, Probably the instructions are not clear enough. You need to add two attributes to the BContextUpdate event. The name of the first attribute is entityId, and it should be of type String (the value of this attribute at run time will be "B1", but in your event definition the name of the attribute should be entityId, and not B1) The name of the second attribute is entityType, and it should be of type String (the value of this attribute at run time will be "B", but in your event definition the name of the attribute should be entityType , and not B) Those attributes would allow you to know which entity from which type got a ContextUpdate event from Orion, and you can refer to those attributes in your other definitions (EPA, segmentation contexts,..) Best regards, Tali Tali Yatzkar Haham Smart Decision Solutions IBM Haifa Research Lab, Israel tali at il.ibm.com 972-4-8296320 From: Ahmed Sadek <don1559 at gmail.com> To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL Cc: "fiware-tech-he." <fiware-tech-help at lists.fi-ware.org>, Fabiana Fournier/Haifa/IBM at IBMIL Date: 12/05/2015 09:01 AM Subject: Re: Problem with xml events CEP and orion Dear Tali, I have read it multiple times, honestly. my understanding from those two lines is that I should add two attributes and I have added them indeed. 1- entityId ? of type String -> Inside event BContextUpdate-> attribute B1 string since this is the entity id. 2- entityType ? of type String -> Inside event BContextUpdate-> attribute B string since this is the entityType. "name": "BContextUpdate", "attributes": [ { "dimension": 0, "name": "Temperature", "type": "Integer" }, { "dimension": "0", "name": "SoC", "type": "Integer" }, { "dimension": "0", "name": "B", "type": "String" }, { "dimension": "0", "name": "B1", "type": "String" } ] Did I understand this correctly ? Best, Ahmed On Tue, May 12, 2015 at 6:29 AM, Tali Yatzkar-Haham <TALI at il.ibm.com> wrote: Dear Ahmed, Please read the CEP user guide appendix carefully, since there are several integration details that you must follow. It seems that the issue you see can be solved by following this requirement from the appendix: In the IBM Proactive Technology Online application, such event type must be defined. This event must have all the context attributes defined in the subscription, and have two additional mandatory attributes: ? entityId ? of type String. This attribute holds the entityId value provided in the message ("OUTSMART.NODE_3505" in the example above) ? entityType ? of type String. This attributes holds the entity type provided in the message ("Node" in the example above) Best regards, Tali Tali Yatzkar Haham Smart Decision Solutions IBM Haifa Research Lab, Israel tali at il.ibm.com 972-4-8296320 From: Ahmed Sadek <don1559 at gmail.com> To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL Date: 12/05/2015 02:00 AM Subject: Problem with xml events CEP and orion Dear Tali, I am trying to post xml events (from orion) to the CEP, but I am getting null point exception errors. Can you help me and tell me where is the problem. When I POST this even I also get null point exception. POST http://194.28.122.7:8080//ProtonOnWebServer/rest/events <notifyContextRequest> <subscriptionId>555128ffa85d63e238d75d8b</subscriptionId> <originator>localhost</originator> <contextResponseList> <contextElementResponse> <contextElement> <entityId type="B" isPattern="false"> <id>B1</id> </entityId> <contextAttributeList> <contextAttribute> <name>Temperature</name> <type>float</type> <contextValue>10</contextValue> </contextAttribute> <contextAttribute> <name>SoC</name> <type>integer</type> <contextValue>10</contextValue> </contextAttribute> </contextAttributeList> </contextElement> <statusCode> <code>200</code> <reasonPhrase>OK</reasonPhrase> </statusCode> </contextElementResponse> </contextResponseList> </notifyContextRequest> Attached the definition file and last catalina log. Best, Ahmed Sadek[attachment "cataline.out" deleted by Tali Yatzkar-Haham/Haifa/IBM] [attachment "lumtest.json" deleted by Tali Yatzkar-Haham/Haifa/IBM] -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150512/99476e55/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy