Skip to main content

JEAP 6 - Domain 啟動 Cluster

又拖稿了.... 請不要催促我咩,因為公司的事情很多!
所以我絕對沒有偷懶噢!

要啓動Domain 的Cluster 很簡單!
只要先學會如何將Domain 啓動的話!如果你不知道,可以先參考之前的文章!
這篇算是第三集了~如果你是從這篇文章開始的話,記得先回前兩個看噢!

這次的做法會將main-server-group 做成一個Cluster (下圖的Cluster One),
other-server-group 做一個Cluster (下圖的Cluster Two),
但是third-server-group 就還是保留一臺!



首先,要將main-server-group 與other-server-group 設定為 Cluster,
跟之前Domain 起動是一樣的!只是Profile 的部分,由 default 改為 full-ha 或是 ha 即可!
當然使用的socket 也要改成是 full-ha-socket 或是 ha-socket.

所以,到第一臺,也就是設定domain.xml 的地方,
打開domain.xml 到設定server-group 的地方,將 main-server-group 與 other-server-group 的 profile 改成 full-ha




接下來,因為Cluster 不只是web 的部分,還有HornetQ 所以還要修改一下設定才不會出 error log. 一樣在domain.xml中, 看自己是用哪一個profile. 如果你是用 ha 請看 ha profile 底下的,我的sample 是 full-ha 所以我就修改 full-ha profile 下的 jboss-messaging subsystem.



接下來這個步驟是optional, 也就是不一定要做,但是如果你之後要用apache 去做load balance 的話,請記得設定每個server 一個獨立的instance id.
設定方式如下:
在你的 profile 下的 web subsystem 上增加instance-id 的設定


<subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false" instance-id="${jboss.node.name}">
     <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
     <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp"/>
     ........
</subsystem>


這樣大致的設定就完成了! 你會發現,一但你定義好了 server-group, 增加 instance 或一次修改 server group 的設定變得簡單很多!
之後就可以跟先前一樣,呼叫 domain.sh or domain.bat 去執行了!

第一台 ./domain.sh


第二台 ./domain.sh


確認沒有出現Exception,
到Console上確實可以出現兩個Host 的資料,裡面也各有屬於自己的server instance.



另外,也可以看到定義的三個不同的server group.




Deploy 程式,請用Web-console 或是 cli deploy喔!
以後有空再寫!

Comments

Hi,

Could u translate this in English...tq

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …