Skip to main content

JEAP 6 Standalone 安裝 on RedHat Linux (非rpm安裝)

JEAP 6 這禮拜終於G.A.了!
我也從蜜月的天堂掉到工作地獄裡拉~
一回來就先Try 一下 JEAP 第一個新鮮的G.A. 版本的安裝

先一步一步來從Standalone 開始。
先從非Cluster 架構開始!

==================================================

1. 首先呢!先請購買RedHat JBoss Subscription!
 (科科~要來跟我買阿!這樣才有原廠的Support阿!公司網站!)

登入客戶網站,到Download , 然後選擇 Application Platform


 下載 Application Platform 6.0.0 (拉到最下方)

之後就會自動下載一個檔案,名稱為:jboss-eap-6.0.0.zip

2. 解壓縮 jboss-eap-6.0.0.zip



3. 我的環境需要我bind 一個 IP 位置給它,因為還有其他的JEAP,所以需要改PORT。
到 /$JBOSS_INSTALL_DIR/standalone/configuration/ 下有個 standalone.xml
(如果你是開發人員,只想在本機跑,基本上這個步驟可以跳過!)

修改IP Address

    <interfaces>
        <interface name="management">
            <!-- 這裡是給管理界面Binding IP 的地方-->
            <inet-address value="${jboss.bind.address.management:偶的IP}"/>
        </interface>
        <interface name="public">
            <!-- 這裡是給程式界面Binding IP 的地方-->
            <inet-address value="${jboss.bind.address:偶的IP}"/>
        </interface>
        .......
    </interfaces>

修改Binding Port

<!-- 把每個Port都增加100 -->
 <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}">
       ........
        <socket-binding name="txn-recovery-environment" port="4712"/>
        <socket-binding name="txn-status-manager" port="4713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="localhost" port="25"/>
        </outbound-socket-binding>
    </socket-binding-group>


4. 設定為Linux Service。

(如過你是開發人員,或是你只是裝來測測,請直接去 /$JBOSS_INSTALL_DIR/ 下
執行./standalone.sh 即可!)

/$JBOSS_INSTALL_DIR/bin/init.d 下的jboss-as-standalone.sh copy 到/etc/init.d/下
先設定等一下chkconfig 要用的參數。

# chkconfig: 2345 95 20

在這裡我發現一個BUG, 我的 Linux 會抓不到 JBOSS_USER , 
所以請在上面加上你的啟動 user

export JBOSS_USER=root


儲存後,開始建立service .

chkconfig --add jboss-as-standalone.sh
chkconfig jboss-as-standalone.sh on

然後就可以打開 JBoss 啦~ 

service jboss-as-standalone.sh start

5. 建立Management 使用者。先用瀏覽器,確認一下!


這時候還不能登入,要先加入
執行 

./add_user.sh admin password 

或是執行./add_user.sh 直接一個一個輸入選項



6. 登入JBoss Admin/Mmgt Console . 
http://SERVER_IP:9990/


7. 這樣就完成拉!!!

Comments

Popular posts from this blog

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 …

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 …