Skip to main content

JBoss BRMS - 呼叫Rule 與 BPMN 的API

學 BRMS 呼叫 Rules 與 BPMN 的 API 真的很划算,因為學一套 API 在 Rules 與 BPMN 都在用。而且概念還滿簡單的。

最主要就是這四個Class, 會使用他們基本上大概就可以操作JBoss Rules (Drools) 與 jBPM了!

  • KnowledgeBuilder
  • KnowledgeBase
  • StatefulKnowledgeSession
  • StatelessKnowledgeSession


望文生義,這個Class 就是專門把各地的的資源,如 Drl 的檔案,jBPM 的 BPMN, 整包的binary package讀取進來,透過KnowledgeBuilderFactory 取得Builder。

如何建立一個Builder 並載入需要的Rule與資源?

A. 載入Drools ,
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();kbuilder.add( ResourceFactory.newUrlResource( "file://myrules.drl" ),ResourceType.DRL);
B.載入 Excel 的 Decision Table,

DecisionTableConfiguration dtconf = KnowledgeBuilderFactory.newDecisionTableConfiguration();
dtconf.setInputType( DecisionTableInputType.XLS );
dtconf.setWorksheetName( "Tables_2" );
kbuilder.add( ResourceFactory.newUrlResource( "file://IntegrationExampleTest.xls" ),ResourceType.DTABLE,dtconf );

C.載入 jBPM 的BPMN2.0檔案

kbuilder.add( ResourceFactory.newUrlResource( "file://myProcess.bpmn2" ),
ResourceType.BPMN2 );


String url = "http://IP:PORT/jboss-brms/rest/packages/xx.yy.aa/binary"; UrlResource resource = (UrlResource) ResourceFactory.newUrlResource(url); resource.setBasicAuthentication("enabled"); resource.setUsername("ID"); resource.setPassword("PWD"); kbuilder.add(resource, ResourceType.PKG);
E. 除了以上寫在程式內的方式外,還可以獨立用XML定義,可以新增一個sampleRule.xml <change-set xmlns=''xmlns:xs=''xs:schemaLocation='' >   <add>   <resource source='http:org/domain/myrules.drl' type='DRL' />   <resource source='classpath:data/IntegrationExampleTest.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="Tables_2" />   </resource>   </add> </change-set> kbuilder.add( ResourceFactory.newUrlResource( "sampleRule.xml" ), ResourceType.CHANGE_SET );
if ( kbuilder.hasErrors() ) {
log.exception( kbuilder.getErrors().toString());

當Builder把資源讀取完之後,就會把編譯後可以執行的 binary放置的地方拉。所以如果你想要更新引擎上面執行的Rules還是流程,就要重新載入這個部分!因為要將所有的Rule 編譯,所以會滿耗費資源的,因此我建議大家啦~ 如果可以就把這個KnowledgeBase 暫存起來在系統裡,反覆地使用會比較好!

KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();kbase.addKnowledgePackages( kbuilder.getKnowledgePackages() );

這個Session 會保持一連串呼叫的狀態。因為他會保留context中的資訊,可以再上一個執行結果之下再做更多的計算跟使用。以jBPM來說,大部份都是使用這種session.
呼叫之後就可以直接insert Facts ,insert的 Fact都會被留在working memory裡面,狀態也會保存。直到session 結束為止。

StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();

for( Object fact : facts ) {
     ksession.insert( fact );



這個Session 並不會保持狀態,也就是說,上一次的變動與下一次的變動是獨立的。因為是這種特性,它可以重複的被一直使用。所以適合在需要一直重複執行然後取得一個結果的規則。
執行的方式,就是呼叫execute, 直接把物件帶入,

StatelessKnowledgeSession ksession = kbase.newStatelessKnowledgeSession();
ksession.execute( collection );

如果想要同時輸入不同的物件,就需要借助 CommandFactory 把物件存放在一個 collection裡面執行啦。

List cmds = new ArrayList();
cmds.add( CommandFactory.newSetGlobal( "list1", new ArrayList() ) );
cmds.add( CommandFactory.newInsert( new Person( "jon", 102 ) ) );

StatelessKnowledgeSession ksession = kbase.newStatelessKnowledgeSession(); 
ksession.execute( CommandFactory.newBatchExecution( cmds ) );



Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.



JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …