Skip to main content

JBoss BRMS - 安裝 (Business Activity Monitoring BAM) 商業活動監控報表

自從BRMS 5.3 出來之後,因為多了jBPM 這個商業流程的管理元件,所以會被問到有沒有商業活動監控報表(Business Activity Monitoring BAM) 這個功能。答案當然是肯定的,接下來就是安裝的步驟。



在JBoss BRMS 5.3 版中安裝 BAM報表功能

1. 先安裝JBoss BRMS 5.3 (請到紅帽的 Customer Portal 下載)

2. 在BRMS 的安裝路徑下增加一個birt的檔案夾,如下
$BRMS_JBOSS_HOME/server/default/data/birt

3. 在剛剛建立的 birt路徑下增加兩個檔案夾,ReportEngine 與 output
$BRMS_JBOSS_HOME/server/default/data/birt/ReportEngine
$BRMS_JBOSS_HOME/server/default/data/birt/output




4. 到以下路徑下載 birt-runtime-2_3_2
http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/R-R1-2_3_2_2-200906011507/birt-runtime-2_3_2_2.zip




5. 解壓縮檔案後,將 birt-runtime-2_3_2_2/ReportEngine 下的檔案複製到到$BRMS_JBOSS_HOME/server/default/data/birt/ReportEngine/ 資料夾


6. 從下方的路徑下載overall_activity.rptdesign 報表設計的檔案
    A. https://github.com/droolsjbpm/jbpm/tree/master/jbpm-installer/report/2_3_2_2
    B. 將檔案複製到$BRMS_JBOSS_HOME/server/default/data/birt/之下
    C. 打開 overall_activity.rptdesign, 把 odaJndiName 改成你的jbpm 的 datasource,
    以我的環境例子就是

    <property name="odaJndiName">java:/DefaultDS</property> 


7. 自 $BRMS_JBOSS_HOME/client/jbpm 複製 h2-xxx.jar  至 $BRMS_JBOSS_HOME/server/default/data/birt/ReportEngine/plugins/org.eclipse.birt.report.data.oda.jdbc_2.3.2.r232_v20090212/drivers/  與 $BRMS_JBOSS_HOME/server/default/deploy/business-central-server.war/WEB-INF/lib/路徑下



8. 自下方路徑刪除report-core-xxx.jar 與 report-shared-xxx.jar 兩個檔案
$BRMS_JBOSS_HOME/server/default/deploy/business-central-server.war/WEB-INF/lib/



9. 請下載以下的jar檔,然後複製到
$BRMS_JBOSS_HOME/server/default/deploy/business-central-server.war/WEB-INF/lib/


  A.report-core-1.3.0.jar
https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/bpm/report-core/1.3.0/report-core-1.3.0.jar
  B.report-shared-1.3.0.jar
https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/bpm/report-shared/1.3.0/report-shared-1.3.0.jar
  C.engineapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/engineapi/2.3.2/engineapi-2.3.2.jar
  D.dteapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/dteapi/2.3.2/dteapi-2.3.2.jar
  E.chartengineapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/chartengineapi/2.3.2/chartengineapi-2.3.2.jar
  F.coreapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/coreapi/2.3.2/coreapi-2.3.2.jar
  G.dataadapterapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/dataadapterapi/2.3.2/dataadapterapi-2.3.2.jar
  H.modelapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/modelapi/2.3.2/modelapi-2.3.2.jar
  I.scriptapi-2.3.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/birt/scriptapi/2.3.2/scriptapi-2.3.2.jar
  J.ecore-2.4.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/emf/ecore/2.4.2/ecore-2.4.2.jar
  K.ecore-xmi-2.4.1.jar
https://repository.jboss.org/nexus/content/groups/public/org/eclipse/emf/ecore-xmi/2.4.1/ecore-xmi-2.4.1.jar
  L.common-2.4.0.jar
http://repository.jboss.org/nexus/content/groups/public/org/eclipse/emf/common/2.4.0/common-2.4.0.jar
  M.flute-1.2.jar
http://repository.jboss.org/nexus/content/groups/public/org/w3c/flute/1.2/flute-1.2.jar
  N.sac-1.3.jar
http://repository.jboss.org/nexus/content/groups/public/org/w3c/sac/1.3/sac-1.3.jar
  O.commons-cli-1.0.jar
http://repo1.maven.org/maven2/commons-cli/commons-cli/1.0/commons-cli-1.0.jar
  P.commons-discovery-0.2.jar
http://repo1.maven.org/maven2/commons-discovery/commons-discovery/0.2/commons-discovery-0.2.jar
  Q.itext-1.3.jar
http://repo1.maven.org/maven2/com/lowagie/itext/1.3/itext-1.3.jar
  R.icu4j-3.8.1.jar
http://repository.jboss.org/nexus/content/groups/public/com/ibm/icu/icu4j/3.8.1/icu4j-3.8.1.jar
  S.js-1.6R2.jar
http://repo1.maven.org/maven2/rhino/js/1.6R2/js-1.6R2.jar




要看到Business Central 的控制台中的報表,請先登入 http://localhost:8080/busoness-central (更多細節可以參考 JBoss BRMS 的 Getting Started Guide).

要幫一個工作或是流程收集它的 BAM 數據, 當然要先執行一些流程拉,然後點選左邊選單的"Report".



右邊的工作區會顯示報表的設定選項,選擇在下拉選項中選擇"overall-activity", 然後按下"create" 即可看到執行這個流程效能的數據報表拉!


給JBoss Developer Studio 使用的報表工具安裝 - BIRT:

1.打開JBDS, 在上方選單選擇 Help -> Install New Software



2.加入 BIRT 的更新網站 http://download.eclipse.org/birt/update-site/3.7


3.下列的package應該會出現,

  • BIRT 3.7 Charting SDK
  • BIRT 3.7 Engine OSGI Runtime SDK
  • BIRT 3.7 Reporting SDK
  • BIRT 3.7 WTP Integration SDK


4.請全選後安裝,然後下一步下一步的安裝。。。



5.重開 JBDS 後即完成!




Comments

Popular posts from this blog

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.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

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

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

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 …

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 …