Skip to main content

JBoss BRMS - 建立第一個JBoss Rules的專案,並連結JBoss BRMS管理網站

再加上有些人不會設定JBoss Developer Studio 這個工具,
並且希望可以跟JBoss BRMS串接在一起,

完成這個之前,首先請先安裝好JBoss BRMS,請參考 JBoss BRMS - 安裝BRMS 到 EAP 6.1

首先,請下載JBoss Developer Studio 5.x版 (到目前為止,官方只有支援 5.X, 等更新了再來update這邊。)

請到這裡下載 : JBoss Developer Studio Download


1. 啓動JBoss Developer Studio(以下簡稱 JBDS),選擇一個workspace 後進入。如果是開發一般的Java程式這樣就可以開始寫了。但是因為我們要開發BRMS相關的,所以要安裝plugin. 請到中間的JBoss Central點選Software Update

勾選Business Rule Tooling, 開始安裝。

安裝完畢後就可以開始建立Drools的環境囉!開始設定Drools Runtime 環境。
在這之前,請先把JBoss BRMS的zip 解壓縮,


請解壓縮裡面的binary folder到某個路徑下。

到Preference ,

選擇Drools 下的Installed Drools Runtime,選擇左手邊的Add, 

新增一個JBoss Drools的 Runtime, 位置請輸入剛剛解壓縮的binary位置。名字隨便敲一個你認識的字就好。


安裝完畢後,按下滑鼠右鍵選擇建立第一個Drools 的Project


選起Default的 HelloWorld 最上面兩個,按下Finish 會自動產生範例的檔案。

左邊會出現新建的Project, 最主要會有一個Drools的測試程式,也會有一個範例的rules.



先離開JBDS, 到你的JBoss BRMS管理網站 http://IP:PORT/jboss-brms/
登入後,請先去新增一的package, (因為 sample的 drl 裡面有設定package, 所以要設定一致)

輸入跟drl sample一模一樣的package名稱 (com.sample)

到Window 底下的Show View下的 Other... 
Guvnor下的 Guvnor Repossitories


輸入登入JBoss BRMS的ID與密碼

這時候,就會出現JBoss BRMS上面有的資料。

要把剛剛建立的Sample.drl上傳到JBoss BRMS的儲存庫上,請在Sample.drls上面按下左邊選單,選擇Gunvnor, 的 Add. (之後若有修改就可以按下Commit更新上Server, 或是Update從Server上抓下來。 )

成功後就會看到Sample.drl 上面繪有上傳的日期

當然,不只是上傳RULEs的檔案,為了要可以再BRMS上面Validate, 編譯,修改或新增Drools, 一樣也要把定義檔案上傳上去。


再Project上按下左邊選單Export JAR檔出去,

回到BRMS 的網頁上,選擇左邊選單,Knowledge Base下的 上傳POJO Model JAR




Popular posts from this blog

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 …

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 …