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!

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

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


2. 解壓縮

3. 我的環境需要我bind 一個 IP 位置給它,因為還有其他的JEAP,所以需要改PORT。
到 /$JBOSS_INSTALL_DIR/standalone/configuration/ 下有個 standalone.xml

修改IP Address

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

修改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"/>

4. 設定為Linux Service。

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

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

# chkconfig: 2345 95 20

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

export JBOSS_USER=root

儲存後,開始建立service .

chkconfig --add
chkconfig on

然後就可以打開 JBoss 啦~ 

service start

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


./ admin password 

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

6. 登入JBoss Admin/Mmgt Console . 

7. 這樣就完成拉!!!


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 …