Skip to main content

JEAP 5&6 - 啓動時自動載入properties的檔案

通常如果要載入一個.properties的檔案,應該盡量不要放在System.getProperties() 因為這是提供給整個JVM instance系統在用的變數。


1), 用load Properties的方式放進來

Properties instance = new Properties();
String value = instance.getProperty(keyName);

2), 用Resource Bundle的方式放進來(比較推薦這種)
ResourceBundle resource = ResourceBundle.getBundle("testprops",locale);

在JBoss EAP 5

只要把properties的檔案放在$JBoss_INSTALL_Path/server/$profile/conf 就可以直接在上述的地方直接寫上properties的名字就好。

在JBoss EAP 6

最簡單的方法就是將整個路徑指定到  FileInputStream 的位置,
InputStream inStream = new FileInputStream("/opt/config/");
Properties instance = new Properties();

但是這樣上述直接去讀取config下properties檔案的方式就不能用了。要使用ResourceBundle 就需去設定JBoss 啓動時自動去讀取的模組。

1. 請先到$JBoss_INSTALL_PATH 下的modules下建立路徑 conf/main/properties
2. 到新建立的路徑conf/main下,建立modules.xml


3.把你的properties檔案放到,剛剛新建立的conf/main/properties 路徑下。

使用Web Console 方式
(這裡是使用standalone模式,如果你是用domain, 請記得去你要修改的profile裡改啊!)

右上方選擇profile,左邊選單選擇container下的ee, 在Global Modules選擇Add

寫上conf (我們剛剛建立的模組名稱)



如果你是使用standalone模式,請改standalone(-*).xml ,如果是domain mode請改domain.xml (請記得去你要修改的profile裡改啊~)


然後加入全域模組<module name="conf" slot="main" /> 如下


但是。。。。。如果你的系統,前人已經寫了System.getProperties()的方式,除了詛咒他,因為他的寫法,害你要每台都去管理propertie檔案,改寫code 之外,還是可以去設定讀到System之下的。(雖然我強烈建議你就摸摸鼻子改寫吧!)

在JBoss EAP 5
在啓動的script裡面,加上-P 的讀取方式,(-P檔案位置) 如...
./ -c testProps -P/opt/config/

在JBoss EAP 6

在啓動的script裡面(standalone 或 domain),加上--properties 的讀取方式,(--properties=檔案位置) 如...
./ --properties=/opt/config/

Web Console 設定位置,
左邊選擇profile, 右邊選單選擇System Properties, 選擇Add

XML 設定位置,
Standalone, 改standalone(-*).xml , domain 改domain.xml>。
在extensions 與 management 中間新增system-properties如下




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

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 …