Skip to main content

JEAP 5 - 安裝JBoss Enterprise Application Platform AS 5.1


環境確認
            
以下有幾項安裝前須確認的部分.

最低應體需求
        
硬體元件
最小需求量
CPU
簡易的應用程式最少1GHz
硬碟空間
1.5 GB
系統記憶體
1.5 GB
                       
OS環境安裝

請先確認以下是否安裝

Java Virtual Machine
Version
Sun JDK
1.6.x
Open JDK
1.6.x
IBM JDK
1.6.x
Azul JDK
1.6.x



安裝步驟

1. 至紅帽網站註冊試用帳號
A. 至 https://www.redhat.com/wapps/sso/login.html 點選


B. 填寫相關登入訊息



C. 帳號申請成功後, 登入Red Hat Customer Portal

D. Evaluation & Demo 選取 Application Platform, 
    選取要試用的版本




E.Download 選取Application Platform



2.下載Application Platform



3.將該檔案解壓縮至預定安裝路徑下
   路徑下應會出現此檔案結構 



4.修改Memory
    如果電腦比較舊型, 或是為32bits Windows環境
    可能需要於啟動前先調整memory 使用大小, 以免發生 OutOfMemoryException
           
     Windows,
      $JBossInstallDir/bin/run.conf.bat
     Others
      $JBossInstallDir/bin/run.conf

     將下方紅字部分(最大與最小的Memory使用)修改


    至  -Xms256m –Xmx1024m 

5.修改開放admin 帳號 (這次先default profile 為主)
   進入$JBossInstallDir/server/default/conf/props
   修改jmx-console-users.properties 檔案,
   #admin=admin #移除後Save (如下, ) 




6.設定外部Data Source(資料來源)連結
   (注意, 每個資料庫的設定都不一定相同)
           
       $JBossInstallDir/docs/examples/jca/xx-ds.xml
       找尋需要的Data Source 範本 (如圖)

7. 設定DS.xml
    依序設定
o   JNDI NAME,
o   CONNECTION URI
o   USER NAME/PWD
    等相關設定值 



8.將程式檔案(EAR or WAR)放置於$JBossInstallDir/server/default/deploy

9.$JBossInstallDir/bin啟動
    Windows
        執行run.bat
    Others
        執行run.sh


10.可使用之Console

            進入http://localhost:8080/admin-console
            (ID admin/PWD admin)







Comments

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

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

事先將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 …