Skip to main content

JBoss BRMS - JBoss Rules 引擎規則

JBoss Rules 第一課,

JBoss Rules 基本上就是去撰寫一堆的邏輯,然後把收集的資料(Fact)放進去,執行出來的就是結果囉!

因為同時會有很多人在會在上面執行,JBoss Rules 引擎也不可能把大家丟進去的物件全部搞在一起。所以引擎必須要將每個使用者的獨立的位置去存放每個人的Fact。這個空間我們叫它Working memory. 所有在JBoss Rule裡面對於Fact的修改,全部都會在自己的Working memory 做。當你的Fact 因為條件而有所變動時的名詞叫做 Truth Management. 我們建制的規則則被讀取,然後放進引擎的RuleBase。

每次執行的時候,JBoss Rules 引擎就會開始看哪些規則可以被執行,這些符合資格可以被執行的規則就叫做Agenda, 然後決定要執行這些規則順序。被執行的規則就叫做Activation。


所以JBoss Rules 引擎就會把可以執行的Rules先找出來,跑出來的Agenda如下面藍色底色的規則

但是這些Agenda 確定執行的順序決定方式如下,也有個名字叫做 Conflict resolution. 衝突管理。

所謂的Salience 就是你在 JBoss Rules 一開始的設定的執行順序,數字越大,表示順序越高。(可以是負數)

如果沒有特別設定,而且排序相同時,他就會看一下這些規則有哪些最近常常被跑到的,會以這個為優先, 如果這些規則的執行次數都差不多的時候,他就會看這些執行規則的複雜程度。越複雜的優先。如果真的不幸每個規則都是一樣複雜的話。那就只好靠誰先load 進來誰就先執行了。

以上為執行的方式。至於計算的演算法。JBoss Rules 是用 RETE. 有機會再上來寫吧!


Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …