Skip to main content

JEAP 6 - cli 筆記

這篇是拿來當做是筆記,有人問我就Update 上來,
這些應該大家也不用背拉,因為小姐我也從來沒背過,(XD, 好像不太敬業)

基本上cli 的架構一點兒都不複雜,

1. 要怎麼執行cli呢?到 EAP_HOME/bin/下執行

$:~ EAP_HOME/bin/

2. 輸入connect IP:PORT 連接你的每個host controller

3. 離開請打 quit.

4. cli 的架構很簡單

  a. 路徑 (address) 在最前面加上斜線 "/"
  b. 作業 (operation) 在最前面的加上冒號 ":"
  c. 參數 (parameter) 這不是必要欄位,但是有的話可以使用括號包起來"()"

路徑的部分相對好找,只要使用ls 就可以慢慢,一層一層的下去,如下面的example 就是 從我的這台機器下,有一個host, host 進去有個hosttwo的 host controller, 進去之後的server-config 下有個server-four, 打下pwd 就會有要用的路徑拉!

作業的部分,很簡單,就是像剛剛那樣,進到你要用的resource 下打下 :read-operation-names 就可以show出所有可以用的operation拉!

參數的部分,是(名字=值) (parameter-name=parameter-value) 的方式打進去就好

1. 如果不使用Domain mode 的 controller 是否可以重開server 哩~
當然是可以拉,如果你懂的cli 的架構,就會發現standalone 跟 domain 其實就是差在一個address上而已!(Standalone 通常就是用default binding 的localhost而已..)

所以,我先connect 到我想要去的server上,打下stop 與 start就好哩!

聯結後單一的command, 如下:

/host= host_name/server-config=server_name:stop

2. 想要使用CLI 修改instance 上的heap size , 也是差不多的.
這裡使用domain 的方式, 依照先前的做法,先看一下JVM 內有啥可以設定的.

裡面有兩個參數,是我這次要用的,heap size 與 max heap size ,

因為這個case, 我的server two 是吃domain.xml 的設定,default 是跑先前在domain.xml 裡面的 jvm = default. (main-server-group 的 jvm 設定 )

登入 cil 後, 先到這次要變更的server two 下,新增一個jvm 叫做change

進入change 這個jvm 後,看一下有哪些參數可以變更,
cd jvm=change
ls -l

這次要變更的是heap size 與 max heap size.
:write-attribute(name="heap-size", value="512")
:write-attribute(name="max-heap-size", value="1303")

修改後,可以去看一下host.xml 會發現裡面的參數已經更新了。

啟動server 後,看一下console 內的參數,就會翻現同樣都是main-server-group , 兩台的jvm 使起的設定已經變成不同了!



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 …