Skip to main content

JON -安裝 JBoss Operations Network

我現在開始會努力償還債務! 雖然我還有一堆東西要弄...  OTZ

要安裝前請先確認電腦已經正確安裝JDK 1.6 版本,


  • Memory 2 GB
  • Installation Directory Storage  10 GB

安裝JON 要先知道它的架構. 請看

裡面需要安裝資料庫,這裡是用postgresql . 

A. 安裝設定Postgresql 資料庫

  • 建立使用者  rhqadmin/ rhqadmin
  • 建立資料庫,rhq rhqadmin設為 owner
  • Grant create, insert, delete, truncate, update 全部的權限

B. 安裝 JON Server
  • unzip
  • 開始安裝
  • JON_SERVER_ROOT/bin/ install
  • 啟動 Server 
  • JON_SERVER_ROOT/bin/ start
  • http://SERVER_IP:7080/ 

  • 填寫資料庫的資訊後開始安裝。

  •  解壓縮 其中的 *.jar 檔案移至 JON_SERVER_ROOTS/plugins

C. 安裝 Agent

  • java -jar rhq-enterprise-agent-4.2.0.JON.3.0.1.GA.jar –i
  • 啟動 AGENT_ROOT/bin/ -s
  • 設定 agent, server name ip and port
    Agent Name [ag1] : hostname   
    Agent Hostname or IP Address [!*] : agent ip   
    Agent Port [16163] :   
    RHQ Server Hostname or IP Address [] : server ip   
    RHQ Server Port [7080] :


D. 開始使用
進入 http://SERVER_IP:7080/
到 Inventory ->  Discover Queue 裡面就可以看到 
記得 import 加入管理群組喔!


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


    Connection Pool 最少會存留的connection 數量


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


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