Skip to main content

JEAP 6 - 動態新增Server 的方法

原先以為只要用 GUI 就夠了,但是有些使用者,因為想要自動化,所以尋問是否有其他的方式。

這裡提供4種方式:

1. 使用GUI 畫面增加
2. 使用 CLI 的command 的方式。
3. 使用 HTTP 的 management API
4. 使用 Java 程式


請先啓動AP Server 的 Domain Mode.

1. 使用GUI 畫面增加








完成後就可以看到 server-four 被建立成功拉!



2. 使用 CLI 的command 的方式。

先到JBoss安裝目錄/bin 下執行jboss-cli.sh (或是 bat ) 啓動 CLI,

聯結後,打入下列指令就可以建立成功拉!

your_host_name  = 想要安裝的host名稱
new_server_name = 新建立的伺服器名稱 
offset_number = port要錯開的數字, 100 的話,所有建立的port 都是預設值+100 
your_server_group = 建立的server所屬的group

/host=your_host_name/server-config=new_server_name:add(auto-start=true,group=your_server_group,socket-binding-port-offset=offset_number


看到 "outcome" => "success" 的回應就成功了。


3. 使用 HTTP 的 management API

server_name =  JBoss 管理的Server IP 或是 hostname
management_port = 預設是9990
auto_start = 新建立的server 是否自動啟動(true or false)

your_host_name  = 想要安裝的host名稱
new_server_name = 新建立的伺服器名稱 
your_server_group = 建立的server所屬的group
offset_number = port要錯開的數字, 100 的話,所有建立的port 都是預設值+100 
id = 登入JBoss管理的 ID 
pwd = 登入JBoss管理的密碼

curl --digest -D - http://server_name:management_port/management --header "Content-Type: application/json" -d '{"operation":"add", "include-runtime":"true" , "address":["host","your_host_name","server-config","new_server_name"],"group":"your_server_group","socket-binding-port-offset":"offset_number","auto-start":"auto_start", "json.pretty":1}' -u id:pwd




看到 "outcome" => "success" 的回應就成功了。

4. 使用 Java 程式

這裡要使用JBoss 提供的API 去呼叫


org.jboss.as.controller.client.ModelControllerClient;
org.jboss.as.controller.client.OperationBuilder;
org.jboss.as.controller.client.helpers.ClientConstants;
org.jboss.dmr.ModelNode;

  Sample 是一個Servlet, 部署上去後,直接呼叫  http://localhost:8680/cliTest/AddUser 就會執行囉~ Sample 程式的重點就是把該帶的參數帶進去而已。

request.get(ClientConstants.OP).set("add");
request.get(ClientConstants.OP_ADDR).add("host", "master");
request.get(ClientConstants.OP_ADDR).add("server-config", "server-six");
request.get("include-runtime").set(true); request.get("group").set("main-server-group");
request.get("socket-binding-port-offset").set("650");
request.get("auto-start").set(true);

package com.test;

import java.io.Closeable;
import java.io.IOException;
import java.io.PrintWriter;
import java.net.InetAddress;
import java.util.List;

import javax.security.auth.callback.Callback;
import javax.security.auth.callback.CallbackHandler;
import javax.security.auth.callback.NameCallback;
import javax.security.auth.callback.PasswordCallback;
import javax.security.auth.callback.UnsupportedCallbackException;
import javax.security.sasl.RealmCallback;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import org.jboss.as.controller.client.ModelControllerClient;
import org.jboss.as.controller.client.OperationBuilder;
import org.jboss.as.controller.client.helpers.ClientConstants;
import org.jboss.dmr.ModelNode;

/**
 * Servlet implementation class DSStats
 */
@WebServlet("/AddUser")
public class AddUser extends HttpServlet {
 private static final long serialVersionUID = 1L;
       
    /**
     * @see HttpServlet#HttpServlet()
     */
    public AddUser() {
        super();
        // TODO Auto-generated constructor stub
    }

 /**
  * @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse response)
  */
 protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  try {

            PrintWriter out = response.getWriter();
            List results = addUser();
            for (ModelNode result : results) {
                out.println("result: " + result.asString());
            }

            out.close();

        } catch (Exception e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
    }

    public static List addUser() throws IOException {
        final ModelNode request = new ModelNode();

        request.get(ClientConstants.OP).set("add");
        request.get(ClientConstants.OP_ADDR).add("host", "master");
        request.get(ClientConstants.OP_ADDR).add("server-config", "server-six");
        request.get("include-runtime").set(true);
        request.get("group").set("main-server-group");
        request.get("socket-binding-port-offset").set("650");
        request.get("auto-start").set(true);
        
        ModelControllerClient client = null;
        try {
         
            client =createClient(InetAddress.getByName("localhost"), 10999,"admin","Christina7979!".toCharArray(),"ManagementRealm");
            
            final ModelNode response = client.execute(new OperationBuilder(request).build());

            return response.asList();
        } finally {
            safeClose(client);
        }
    }

    public static void safeClose(final Closeable closeable) {
        if (closeable != null) try {
            closeable.close();
        } catch (Exception e) {
            // no-op
        }
    }
    
    
    private static ModelControllerClient createClient(final InetAddress host, final int port, final String username, final char[] password, final String securityRealmName) {

     final CallbackHandler callbackHandler = new CallbackHandler() {

      public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {
       
       for (Callback current : callbacks) {
        System.out.println("current callbacks:["+current+"]");
            if (current instanceof NameCallback) {
             System.out.println("username:["+username+"]");
                NameCallback ncb = (NameCallback) current;
                ncb.setName(username);
            } else if (current instanceof PasswordCallback) {
                PasswordCallback pcb = (PasswordCallback) current;
                pcb.setPassword(password);
                System.out.println("password:["+new String(pcb.getPassword())+"]");
            } else if (current instanceof RealmCallback) {
                RealmCallback rcb = (RealmCallback) current;
                rcb.setText(rcb.getDefaultText());
                System.out.println("RealmCallback:["+rcb.getDefaultText()+"]");
            } else {
                throw new UnsupportedCallbackException(current);
            }
       }
      }
     };

     return ModelControllerClient.Factory.create(host, port, callbackHandler);
    }

}



看到 "outcome" => "success" 的回應就成功了。


以上

Comments

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …