Skip to main content

JBoss A-MQ - 安裝JBoss A-MQ

JBoss 的 A-MQ 就是OpenSource界鼎鼎大名的Apache Active MQ 企業支援版。
沿襲著JBoss良好的傳統,所有的安裝都是解壓縮,然後就可以跑了。

(這是為了不想學安裝的開發者著想,所以這個設定頂多安裝,上正式環境還是要調整一下比較好。)

1. 先從Red Hat 的網站上取得JBoss A-MQ 的檔案

   jboss-a-mq-6.0.0.redhat-024.zip

2. 把它解壓縮到你要安裝的位置,塌~搭~ 完成。哇哈哈~

雖然說這樣就裝完了,其實也是有一些東西要設定啦~
例如說,遠端登入的使用者的ID 與密碼~以及要使用A-MQ的網路控制台的登入ID 與密碼。

有兩個檔案要修改

A. AMQ_INSTALL_PATH/etc/users.properties 下,把 #admin=admin,admin# 拿掉即可


如果說你不想要用預設的ID 與密碼的話,可以修改, 大概就是這樣的

user_name1=password1,role1
user_name2=password1,role1
user_name3=password3,role2

B. AMQ_INSTALL_PATH/etc/system.properties 下,找到 activemq.jmx.user activemq.jmx.password 這兩個值。然後把剛剛設定在users.properties裡面的ID/PWD 找一個填進去就好拉。



3. 開始啓動到 A-MQ, AMQ_INSTALL_PATH/bin 下,執行start 的檔案

Windows
            start.bat
Unix
            start

4. 看起動是否有成功,除了可以到 AMQ_INSTALL_PATH/data/log 之下的amq.log檔案看看有沒有Broker amq has started. 這個字串外。


裡面也有測試的程式可以發送訊息到Queue,以及去接收訊息的Client程式。

java -jar extras/mq-client.jar producer --user admin --password admin



java -jar extras/mq-client.jar consumer --user admin --password admin
以上,安裝完成。



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 …