10:08 a.m.
Hi all,
I'm new to Drools.
We need to have Fusion features in our systems, especially temporal
relations on events.
The problem is we don't know how to take Fusion in use.
Our rules do not fire, why ?
What are the steps to get Fusion up and running ?
We are using Drools as a web service, and it is fed with xml-formed facts
through REST interface.
Drools itself works ok.
We use Guvnor as rule editor, and have its snapshot included as CHANGE_SET
resource in knowledge-services.xml, so that's not a problem.
The rules we are now interested in sits in separate .drl files which are
read as DRL resources in knowledge-services.xml
(file contents below, with BBBafterAAA.drl as a resource).
As I have understood, we must change to stateful session from stateless, to
use Fusion.
This is so that we can define the event processing mode as STREAM in
kbase-definition,
and clock-type as REALTIME in session-definition.
We are primarily using Drools version 5.1.1 on several physical and virtual
servers
(we are just learning Drools for now, primaliry gathering data to be used in
Drools).
Now I am testing Drools version 5.3.0-SNAPSHOT (drools-camel-server),
where the config file snippet below are taken.
<path> below replaces the actual package names.
We have declared some incoming facts to be events (never mind the Bean
ending):
declares_drl.drl
{file}
package org.test;
import <path>.AAABean;
import <path>.BBBBean;
declare AAABean
@role(event)
end
declare BBBBean
@role(event)
end
{/file}
File BBBafterAAA.drl contents, withot THEN part:
{file}
package org.test;
import <path>.AAABean;
import <path>.BBBBean;
/*
declare AAABean
@role(event)
end
declare BBBBean
@role(event)
end
*/
rule "BBBAfterAAA"
dialect "mvel"
no-loop true
salience 100
when
$Aaa : AAABean();
$Bbb : BBBBean(this after[10s, 10m] $Aaa);
then
// Consequences go here
{/file}
File knowledge-services.xml contents:
{file}
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:drools="http://drools.org/schema/drools-spring"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://drools.org/schema/drools-spring
http://drools.org/schema/drools-spring-1.3.0.xsd">
<drools:grid-node id="node1"/>
<drools:resource-change-scanner id="scanner" interval="2" />
<bean name="CCCInitBean"
class="<path>.InitBean">
<property name="initOk" value="false"/>
</bean>
<drools:kbase id="kbase1" node="node1">
<drools:resources>
<drools:resource type="DRL"
source="classpath:test.drl"/>
<drools:resource type="DRL"
source="classpath:declares_drl.drl"/>
<drools:resource type="DRL"
source="classpath:BBBafterAAA.drl"/>
<drools:resource type="CHANGE_SET"
source="classpath:ChangeSet.xml"/>
</drools:resources>
<drools:configuration>
<drools:event-processing-mode mode="STREAM"/>
</drools:configuration>
</drools:kbase>
<drools:kagent id="kagent1" kbase="kbase1"
new-instance="false">
<drools:resources>
<drools:resource type="CHANGE_SET"
source="classpath:ChangeSet.xml"/>
</drools:resources>
</drools:kagent>
<drools:ksession id="ksession1" type="stateful"
kbase="kbase1"
node="node1">
<drools:configuration>
<drools:clock-type type="REALTIME"/>
</drools:configuration>
<drools:batch>
<drools:insert-object ref="mirellaInitBean"/>
<drools:fire-all-rules />
</drools:batch>
</drools:ksession>
</beans>
{/file}
Cheers,
Esko
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3287119....
Sent from the Drools: User forum mailing list archive at Nabble.com.
10:50 a.m.
I don't see how <drools:batch> in combination with a real time clock is
going to provide you with a scenario where some B can be 10s or more after
an A.
There is no particular knob to turn in order to use Fusion. Basically, it's
Expert, with some features triggered by declaring fact types as events so
that timestamps are applied upon fact insertion.
If your facts are inserted in real time into an ongoing stateful session,
declare with @role(event) and a realtime clock in STREAM mode is adequate.
Otherwise you may have to provide timestamps as bean properties, identify
the field in the declare and then you can use CLOUD mode.
-W
On 26 August 2011 17:08, eskomk <esko.hujanen(a)ebsolut.fi> wrote:
Hi all,
I'm new to Drools.
We need to have Fusion features in our systems, especially temporal
relations on events.
The problem is we don't know how to take Fusion in use.
Our rules do not fire, why ?
What are the steps to get Fusion up and running ?
We are using Drools as a web service, and it is fed with xml-formed facts
through REST interface.
Drools itself works ok.
We use Guvnor as rule editor, and have its snapshot included as CHANGE_SET
resource in knowledge-services.xml, so that's not a problem.
The rules we are now interested in sits in separate .drl files which are
read as DRL resources in knowledge-services.xml
(file contents below, with BBBafterAAA.drl as a resource).
As I have understood, we must change to stateful session from stateless, to
use Fusion.
This is so that we can define the event processing mode as STREAM in
kbase-definition,
and clock-type as REALTIME in session-definition.
We are primarily using Drools version 5.1.1 on several physical and virtual
servers
(we are just learning Drools for now, primaliry gathering data to be used
in
Drools).
Now I am testing Drools version 5.3.0-SNAPSHOT (drools-camel-server),
where the config file snippet below are taken.
<path> below replaces the actual package names.
We have declared some incoming facts to be events (never mind the Bean
ending):
declares_drl.drl
{file}
package org.test;
import <path>.AAABean;
import <path>.BBBBean;
declare AAABean
@role(event)
end
declare BBBBean
@role(event)
end
{/file}
File BBBafterAAA.drl contents, withot THEN part:
{file}
package org.test;
import <path>.AAABean;
import <path>.BBBBean;
/*
declare AAABean
@role(event)
end
declare BBBBean
@role(event)
end
*/
rule "BBBAfterAAA"
dialect "mvel"
no-loop true
salience 100
when
$Aaa : AAABean();
$Bbb : BBBBean(this after[10s, 10m] $Aaa);
then
// Consequences go here
{/file}
File knowledge-services.xml contents:
{file}
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:drools="http://drools.org/schema/drools-spring"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://drools.org/schema/drools-spring
http://drools.org/schema/drools-spring-1.3.0.xsd">
<drools:grid-node id="node1"/>
<drools:resource-change-scanner id="scanner" interval="2" />
<bean name="CCCInitBean"
class="<path>.InitBean">
<property name="initOk" value="false"/>
</bean>
<drools:kbase id="kbase1" node="node1">
<drools:resources>
<drools:resource type="DRL"
source="classpath:test.drl"/>
<drools:resource type="DRL"
source="classpath:declares_drl.drl"/>
<drools:resource type="DRL"
source="classpath:BBBafterAAA.drl"/>
<drools:resource type="CHANGE_SET"
source="classpath:ChangeSet.xml"/>
</drools:resources>
<drools:configuration>
<drools:event-processing-mode mode="STREAM"/>
</drools:configuration>
</drools:kbase>
<drools:kagent id="kagent1" kbase="kbase1"
new-instance="false">
<drools:resources>
<drools:resource type="CHANGE_SET"
source="classpath:ChangeSet.xml"/>
</drools:resources>
</drools:kagent>
<drools:ksession id="ksession1" type="stateful"
kbase="kbase1"
node="node1">
<drools:configuration>
<drools:clock-type type="REALTIME"/>
</drools:configuration>
<drools:batch>
<drools:insert-object ref="mirellaInitBean"/>
<drools:fire-all-rules />
</drools:batch>
</drools:ksession>
</beans>
{/file}
Cheers,
Esko
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3287119....
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
5:30 a.m.
Hi Wolfgang et al,
That <drools:batch> is used to run init.drl using mirellaInitBean.
mirellaInitBean is just a stub that fires init.drl which in turn starts
ResourceChangeNotifierService and ResourceChangeScannerService
(I did not remember to replace "mirella" with "CCC" in my original
post, see
knowledge-services.xml below. mirella is a product name we are working on).
But this is something that has been verified as working solution, by me
anyway.
But the problem still exist: Our rules do not fire.
Yes, we are inserting facts (events) in real time.
I thought that, in CLOUD mode, you cannot use e.g. @expires in the declare,
or it has no effect.
Is that so ?
Also you must have stateful session to use STREAM mode.
Is that so ?
There is no notion of real-time clock in stateless session.
Cheers,
Esko
-----------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3292367....
Sent from the Drools: User forum mailing list archive at Nabble.com.
7:38 a.m.
Well, I still don't see how you insert the event facts.
However, I think you must provide the declares where you define @role(event)
in the first .drl file where these types are used in one or more rules. But
failure
to do so should cause a class cast error when the condition of BBBAfterAAA
is
evaluated.
Try a rule like this which should show what is in WM:
rule x
when
$obj: Object()
then
System.out.println( "fact: " + $obj.getClass() );
end
-W
On 29 August 2011 12:30, eskomk <esko.hujanen(a)ebsolut.fi> wrote:
Hi Wolfgang et al,
That <drools:batch> is used to run init.drl using mirellaInitBean.
mirellaInitBean is just a stub that fires init.drl which in turn starts
ResourceChangeNotifierService and ResourceChangeScannerService
(I did not remember to replace "mirella" with "CCC" in my original
post,
see
knowledge-services.xml below. mirella is a product name we are working on).
But this is something that has been verified as working solution, by me
anyway.
But the problem still exist: Our rules do not fire.
Yes, we are inserting facts (events) in real time.
I thought that, in CLOUD mode, you cannot use e.g. @expires in the declare,
or it has no effect.
Is that so ?
Also you must have stateful session to use STREAM mode.
Is that so ?
There is no notion of real-time clock in stateless session.
Cheers,
Esko
-----------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3292367....
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
10:16 a.m.
We send the facts over REST interface in XStream mode:
<batch-execution lookup="ksession1">
<insert out-identifier="msg_11707096">
<path.to.AAABean>
<boxID>7</boxID>
<sensorID>37</sensorID>
<open>true</open>
<countOpened>4</countOpened>
</path.to.AAABean>
</insert>
</batch-execution>
Do we need to do an insert somewhere explicitly ?
Doesn't REST interface handle that ?
cheers,
Esko
--------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3304510....
Sent from the Drools: User forum mailing list archive at Nabble.com.
12:08 p.m.
This batch execution does not fireAllRules. So, where is that one called?
-W
On 2 September 2011 17:16, eskomk <esko.hujanen(a)ebsolut.fi> wrote:
We send the facts over REST interface in XStream mode:
<batch-execution lookup="ksession1">
<insert out-identifier="msg_11707096">
<path.to.AAABean>
<boxID>7</boxID>
<sensorID>37</sensorID>
<open>true</open>
<countOpened>4</countOpened>
</path.to.AAABean>
</insert>
</batch-execution>
Do we need to do an insert somewhere explicitly ?
Doesn't REST interface handle that ?
cheers,
Esko
--------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3304510....
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
11:38 a.m.
Hi W,
Thank you!
Adding fire-all-rules did the trick:
<batch-execution lookup="ksession1">
<insert out-identifier="msg_11707096">
<path.to.AAABean>
<boxID>7</boxID>
<sensorID>37</sensorID>
<open>true</open>
<countOpened>4</countOpened>
</path.to.AAABean>
</insert>
<fire-all-rules out-identifier="firedActivations"/>
</batch-execution>
It somewhat obscured that when dealing with plain facts there was no need to
explicitly call fireAllRules ... Why ?
Cheers,
Esko
------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3308842....
Sent from the Drools: User forum mailing list archive at Nabble.com.
12:09 p.m.
You can kickstart the Drools (and any similar) engine by telling them to do
all that needs to be done and then take Time off forever and a day
(fireAllRules), or to stay alert and catch them as they come
(fireUntilHalt). You might guess that the latter implies multiple threads.
-W
On 4 September 2011 18:38, eskomk <esko.hujanen(a)ebsolut.fi> wrote:
Hi W,
Thank you!
Adding fire-all-rules did the trick:
<batch-execution lookup="ksession1">
<insert out-identifier="msg_11707096">
<path.to.AAABean>
<boxID>7</boxID>
<sensorID>37</sensorID>
<open>true</open>
<countOpened>4</countOpened>
</path.to.AAABean>
</insert>
<fire-all-rules out-identifier="firedActivations"/>
</batch-execution>
It somewhat obscured that when dealing with plain facts there was no need
to
explicitly call fireAllRules ... Why ?
Cheers,
Esko
------
Esko Hujanen
http://www.ebsolut.fi
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3308842....
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4632
days inactive
4641
days old
7 comments
2 participants
participants (2)
-
eskomk -
Wolfgang Laun