Skip to main content

JBoss BRMS - 安裝BRMS 到 EAP 6.X

注意,如果你是企業用戶,請安裝在 EAP 6.0上。
因為EAP 6.1 還沒有被認證喔!

1. 首先,你要先有兩個檔案,

A. BRMS 的檔案,brms-p-5.3.1.GA-deployable-ee6.zip
B. EAP 6.1的檔案,jboss-eap-6.1.0.zip

接下來,我們先安裝JBoss EAP 6.1,安裝方法也是老樣子, 先解壓縮到你的安裝路徑後即可。因為提供的WAR檔是檔案夾形式的,所以這裡是用 Standalone mode 安裝。

2. 將BRMS 所需要使用的WAR檔,部署到 JBoss EAP 6.1上,很簡單,

A. 解壓縮 brms-p-5.3.1.GA-deployable-ee6.zip 裡面的 jboss-brms-manager-ee6.zip

打開裡面會有一個jboss-brms.war的folder, 請把這個放到你的 EAP_install_path/standalone/deployments的目錄下


B. 解壓縮 brms-p-5.3.1.GA-deployable-ee6.zip 裡面的 jboss-jbpm-console-ee6.zip 
打開裡面會有四個war的folder,


  • business-central-server.war
  • business-central.war
  • designer.war
  • jbpm-human-task.war


請把所有的檔案都放到你的 EAP_install_path/standalone/deployments的目錄下

C. 請在EAP_install_path/standalone/deployments的目錄下建立五個檔案 (內容可空白)

  • jboss-brms.war.dodeploy
  • business-central.war.dodeploy
  • business-central-server.war.dodeploy
  • desginer.war.dodeploy
  • jbpm-human-task.war.dodeploy




3. 修改EAP_install_path/standalone/configuration下的 standalone.xml (如果你使用別的xml, 請記得改對咧~)!

A. 設定讀取netty的相關library, 請找到 Java EE 的 subsystem, 加上這段XML.


 
   <global-modules>
   <module name="org.jboss.netty" slot="main"/>
   </global-modules>



B. 增加BRMS 使用的datasource設定,這邊使用的是內建的h2 資料庫,如果你喜歡,也可以建立在普通的RDBMS, 有機會我再來講怎麼建立。

請找到 datasource 的 subsystem,
基本上,只要把原先那個ExampleDS的 datasource整個複製,改成jbpmDS 即可。



<datasource jndi-name="java:jboss/datasources/jbpmDS" pool-name="jbpmDS" enabled="true" use-java-context="true">
   <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
   <driver>h2</driver>
   <security>
                <user-name>sa</user-name>
                 <password>sa</password>
   </security>
</datasource>

B. 使用者登入認證設定。
請找到 security 的 subsystem,新增一個brms專用的認證設定。(到我們指定的地方抓取login 的ID 與 Password. )




<security-domain name="brms" cache-type="default">
   <authentication>
       <login-module code="UsersRoles" flag="required">
           <module-option name="usersProperties" value="${jboss.server.config.dir}/brms-users.properties"/>
                            <module-option name="rolesProperties" value="${jboss.server.config.dir}/brms-roles.properties"/>
                   </login-module>
           </authentication>
</security-domain>

這裡也需要去修改EAP_install_path/standalone/deployments/jboss-brms.war/WEB-INF/components.xml,將原先的jaas-config-name 油 jmx-console 改為 brms





4. 最後再去EAP_install_path/standalone/configuration 下,增加brms-users.properties 與 brms-users.properties 與  brms-roles.properties 兩個檔案,並在裡面打入要使用的使用者以及他/她的群組。即可啓動拉~!


brms-users.properties  增加使用者,如

admin=admin

brms-roles.properties  寫上對應的角色,如

username=JBossAdmin,httpInvoker,user,admin

4. 啟動JBoss EAP 6.1 Server, 位置在 EAP_install_path/bin 下的 ./standalone.sh


到 http://localhost:8080/jboss-brms/ 下,用剛剛的ID/PWD 登入,
看到畫面就成功拉~



以上。







Comments

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …