Skip to main content

JEAP 6 - Clustered EJB3

本來是想在上一篇的ejb寫個同場加映,但是剛好出差北京,
想當然爾,因為當局嚴密的監控下,所有的部落格都無法登入。
只有回到台灣才能把這篇寫上去了!
=======================================================

在閱讀這篇文章前,請先

A. 學會建立JBoss EAP 的 Cluster, Standalone or Domain 都可以. (請參考先前的文章)
B. 學會寫EJB (請看上次的 EJB 建立 Stateless session bean)

因為上次是寫Stateless, 那我們這次就寫Stateful Session Bean囉!

1. 請參考上次建立EJB 的方法,唯一的不同,就是這次建立的時候建的是Stateful. 然後建立完畢後,請在最上方加上@Clustered 的 annotation.



2. 啟動Cluster 的兩個JBoss EAP 6 Server, 把兩個EAR 檔案部署上去,這次我把其中一台的port 全部offset 成都加100.




3. 建立EJB Client, 這次換個不同的方式讀取設定檔,請在Client 的專案中,建立一個resource 的 檔案夾,建立jboss-ejb-client.properties. 這裡就是告訴我們的Client 有哪些EJB 的來源是可以去抓的。
package redhat.remote;

import java.util.Hashtable;

import javax.naming.Context;
import javax.naming.InitialContext;

import redhat.remotebeans.MyStatusBeanRemote;

public class EJBClient {
 
 public static void main(String ar[]) throws Exception{
        Context context=null;
        try{
         final Hashtable jndiProperties = new Hashtable();
            jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
            context = new InitialContext(jndiProperties);
          
        }catch (Exception e) {
              e.printStackTrace();
        }
       
       
        MyStatusBeanRemote remote=(MyStatusBeanRemote)context.lookup("ejb:MyEJBProjectEAR/MyEJBProject/MyStatusBean!redhat.remotebeans.MyStatusBeanRemote?stateful");
        System.out.println("1."+remote.getState());
        remote.updateState("Christina");
        System.out.println("2."+remote.getState()); 
       
     }

}


endpoint.name=client-endpoint
java.naming.factory.url.pkgs=org.jboss.ejb.client.naming
remote.clusters=ejb
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default,default1

remote.connection.default.host=localhost
remote.connection.default.port = 4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.default1.host=localhost
remote.connection.default1.port = 4547
remote.connection.default1.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

4. 執行 EJB Client, 可以看見他有成功地抓到兩個不同的EJB 來源。並且完成呼叫拉!




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 …