Skip to main content

JON Alert 呼叫 CLI 執行shell or perl 程式

JON Agent 啓動時權限要注意!!!!千萬不要跟我一樣耍蠢~ 冏TZ...


昨天在測試JON執行shell script 的時候,
因為要透過Alert 啟動 shell 的程式,所以我就想在本機端啓動我的JON Server 與 agent 。

還有就是發動Alert 專用的JBoss AP Server.
但是不知道為啥,我確定所有的東西都設定的好好的!但電腦上的 Server 就是沒有找到....

搞了半小時候,才想到...ㄟ~ 我的JBoss 好像是用root 的權限啓動的... agent 只是用普通的user...
還我美麗的青春阿...果然改用root 啓動後,就順利找到啦! 請各位記住我的教訓~

  
上面是我的 JEAP Process ID


Agent 顯示終於找到JBoss 拉~ 我真是個笨蛋哈~


回到正題,這次是因為有人需要在JON 上設定發生警告(Alert)的時候,
可以去執行外部的Shell (or Perl),
而JON 在Alert 裡面提供一個統一的CLI 介面語言。
(等我Feel 到了再來寫寫 CLI  ~ XD~哈哈)

以下為設定的方式,

1. 先設定Alert ,到機器上選擇JBoss, 選擇最上面的Alert Tab。



2. 設定警告(Alert) 首先請給個名字,

 

3. 設定警告條件 (這裡不是重點,就自己設定自己需要的條件囉。)


4. CLI Script 的寫法,因為CLI 是類似Javascript 的寫法,(但是可以用來call Java 的 API) 所以我基本上使用了類似 Java 去 Call Native 執行的方式寫的!

1. 在我的sample folder 裡面, 先寫一個測試的 shell 
sh-3.2$ ls -l
-rwxrwxrwx  1 weimeilin  admin  138  5 15 11:06 alertSample.sh

這個Shell 的內容也沒啥,就是跟我說說hello~

#! /bin/sh
echo "Hello Chris ~!"
echo "hi hi Christina " > /Applications/EAP5.1/chrissample/hello.log
echo "bye bye Chris......"

2. 現在,寫一個test.js, 專門去執行 "alertSample.sh"

println("Hello Chris,  this is CLI");

//以下為執行的code, 若是perl 的程式,那就是 exec("perl /xx/sample.pl")

var runtime = java.lang.Runtime.getRuntime();
var proc = runtime.exec("sh /Applications/EAP5.1/chrissample/alertSample.sh");
var stdin = proc.getInputStream();
var isr = new java.io.InputStreamReader(stdin);
var br = new java.io.BufferedReader(isr);
var line = null;

println("====output====");
while ( (line = br.readLine()) != null){
    println(line);
}
println("====output DONE====");

var exitVal = proc.waitFor();
println("Process exitValue: " + exitVal);


完成後,我先至普通的CLI 界面執行,
看到執行是OK的~ log 也有正確產生


-rwxrwxrwx  1 weimeilin  admin  131  5 15 12:29 alertSample.sh
-rw-r--r--  1 root       admin   17  5 15 12:29 hello.log
-rwxr-xr-x  1 weimeilin  admin  540  5 15 12:28 test.js



5. 設定發生警告時,去執行 CLI, 選擇後按OK 就完成了!





當然你可以設定Error 發生幾次錯誤之後才寄送Mail。但都不是這次的重點。 所以先略過 ;p

完成之後,一旦JON Server達到警告的條件,就會去執行那隻CLI script, 相對的CLI 的script 會利用我們寫的程式去呼叫 shell 或是 perl 





Comments

Popular posts from this blog

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 …

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 …