| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMIT / CEP - IntelligentFilter question |
« View previous topic :: View next topic » |
| Author |
Message
|
| mark.luebinski |
 Posted: Fri Jan 19, 2007 8:22 am Post subject: AMIT / CEP - IntelligentFilter question |
 |
|
Acolyte
Joined: 27 Mar 2006
Posts: 56
|
Dear Masters,
I try to use CEP for simple Problem - my Flow tree is big and if the message (response to one request in the flow) don't arrive one of leaves, some person must get one email. But it is not an error, so I must not roll all stuff back.
I defined two events (in and out), and placed two computes+intellegentFilters producing the in-Event in beginn of the flow and out - after the special MQout-Queue.
Also I have one Key (with one Field of both events) and Lifetime of 2 seconds (for testing).
In the scenario-test CEP works fine. But in the flow I get
(DEBUG ) 20070119-170607CET AbstractAmitNode::buildFlattenedMessage (): content of event (kampagneIn) passed to AMiT core
(DEBUG ) 20070119-170607CET Body.kampagneIn.ID - 414d5120514d43303035202020202020a563594520281602
(DEBUG ) 20070119-170607CET Body.kampagneIn.SCHL_BEGR - 000000005003244
(DEBUG ) 20070119-170607CET AbstractAmitNode::buildFlattenedMessage (): ***********************
and
(DEBUG ) 20070119-165809CET AbstractAmitNode::buildFlattenedMessage (): ***********************
(DEBUG ) 20070119-165809CET AbstractAmitNode::buildFlattenedMessage (): content of event (kampagneOut) passed to AMiT core
(DEBUG ) 20070119-165809CET Body.kampagneOut.ID - 414d5120514d4330303320202020202074c5a44520148e0a
(DEBUG ) 20070119-165809CET Body.kampagneOut.SCHL_BEGR - 000000005003244
(DEBUG ) 20070119-170607CET AbstractAmitNode::buildFlattenedMessage (): ***********************
so that events are more than 2 second from each other. BUT I get no message on the conditionalOuts of one of the Filter-Nodes (I hoped to get it on the conditional out of the IN-IntelligentFilter).
What's going wrong?
Thank you!
Mark |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jan 19, 2007 9:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The situation is only detected when, in your case, the lifespan ends. It won't be propagated to both IntelligentFilter nodes.
You probably want to use the SituationManager node in both cases instead of the IntelligentFilter node. Then you can instruct the node to place the situation message onto another queue - that will trigger a flow to send the email. This way your original flow is minimally changed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mark.luebinski |
| Posted: Mon Jan 22, 2007 1:44 am Post subject: CEP ignore my Out-Event !!!! |
|
|
Acolyte
Joined: 27 Mar 2006
Posts: 56
|
Hallo Jeff, dear Masters,
thank you for the answer.
I will tried SituationManager out. But it work not the way, I would expect.
The first event
(DEBUG ) 20070122-124019CET AbstractAmitNode::buildFlattenedMessage (): ***********************
(DEBUG ) 20070122-124019CET AbstractAmitNode::buildFlattenedMessage (): content of event (kampagneIn) passed to AMiT core
(DEBUG ) 20070122-124019CET Body.kampagneIn.SCHL_BEGR - 000000005003244
(DEBUG ) 20070122-124019CET AbstractAmitNode::buildFlattenedMessage (): ***********************
follows by second event
(DEBUG ) 20070122-124021CET AbstractAmitNode::buildFlattenedMessage (): ***********************
(DEBUG ) 20070122-124021CET AbstractAmitNode::buildFlattenedMessage (): content of event (kampagneOut) passed to AMiT core
(DEBUG ) 20070122-124021CET Body.kampagneOut.SCHL_BEGR - 000000005003244
(DEBUG ) 20070122-124021CET AbstractAmitNode::buildFlattenedMessage (): ***********************
The NOT-Condition-Lifespan is 122 Seconds!
<?xml version="1.0" encoding="UTF-8"?>
<!-- (C) Copyright IBM Corp. 2006 - All Rights Reserved. -->
<!-- Haifa Research Laboratory -->
<!-- Active Technologies Department -->
<amt xmlns="http://www.ibm.com/amt/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com/amt/ amt.xsd">
<domain>
<eventTypes>
<eventType name="kampagneIn" updateDefinition="add">
<identification createdBy="UMA158" createdOn="15.01.07"/>
<attributeType name="Body.kampagneIn.ID" xsi:type="string"/>
<attributeType name="Body.kampagneIn.SCHL_BEGR" xsi:type="string"/>
<attributeType name="Body.kampagneIn.GKZ" xsi:type="string"/>
<attributeType name="Body.kampagneIn.SCHL_TYPE" xsi:type="string"/>
<attributeType name="Body.kampagneIn.KAMP_NR" xsi:type="string"/>
</eventType>
<eventType name="kampagneOut" updateDefinition="add">
<identification createdBy="UMA158" createdOn="15.01.07"/>
<attributeType name="Body.kampagneOut.ID" xsi:type="string"/>
<attributeType name="Body.kampagneOut.SCHL_BEGR" xsi:type="string"/>
<attributeType name="Body.kampagneOut.GKZ" xsi:type="string"/>
<attributeType name="Body.kampagneOut.SCHL_TYPE" xsi:type="string"/>
<attributeType name="Body.kampagneOut.KAMP_NR" xsi:type="string"/>
</eventType>
<eventType name="NichtAngekommen" updateDefinition="add">
<identification createdBy="UMA158" createdOn="16.01.07"/>
<attributeType name="SCHL_BEGR" xsi:type="string"/>
</eventType>
</eventTypes>
</domain>
<rules>
<keys>
<key name="SCHL_BEGR_gleich" type="string" updateDefinition="add">
<identification createdBy="UMA158" createdOn="19.01.07"/>
<eventKey eventType="kampagneOut" expression="kampagneOut.Body.kampagneOut.SCHL_BEGR"/>
<eventKey eventType="kampagneIn" expression="kampagneIn.Body.kampagneIn.SCHL_BEGR"/>
</key>
</keys>
<lifespans>
<lifespan name="Verzoegerung" updateDefinition="add">
<identification createdBy="UMA158" createdOn="16.01.07"/>
<initiator>
<eventInitiator as="in_ev" correlate="ignore"
name="kampagneIn" where=""/>
</initiator>
<terminator>
<expirationInterval timeInterval="122000"/>
</terminator>
<keyBy name="SCHL_BEGR_gleich"/>
</lifespan>
</lifespans>
<situations>
<situation certaintyThreshold="1" initialActivation="true"
internal="false" lifespan="Verzoegerung"
name="NichtAngekommen" persistent="false" updateDefinition="add">
<identification createdBy="UMA158" createdOn="16.01.07"/>
<not>
<operandNot eventType="kampagneOut" threshold=""/>
</not>
<situationAttribute attributeName="SCHL_BEGR" expression="key.SCHL_BEGR_gleich"/>
</situation>
</situations>
</rules>
</amt>
CEP waits for about 2 Minutes und writes afterthere in the queue!!! Why???
The out event, which is expecting came after 2 seconds!
Thank you!
Mark |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
