Skip to main content

JEAP 6 - Migration 到JBoss EAP 6 的注意事項

暫時一些遇到的注意事項,以後也會慢慢地補上。
這是從JBoss 文件看到一些內容,把它整理在這裡
===========================================

WebLogic to JBoss

weblogic.xml

Virtual Directories

weblogic.xml 裡面設定<virtual-directory-mapping>,可以讓User可以自訂檔案根目錄的功能,因為這不是JavaEE 的標準,因為隨時可以使用程式或設定達到,所以J老板沒有特別去支援這個功能。但如果你不幸使用到了這個功能,大概也只有以下三種方式
  • 乖乖的把檔案copy到你的應用程式裡面
  • 如果是用 Linux or Unix 的話,可以設定 symbolic links (symlinks) 到你想聯結的目錄(注意,目前僅EAP 6.1.0 以上支援,且必須在 jboss-web.xml 裡面加上
    symbolic-linking-enabled 為 true)
  • 把檔案放到前端的 web server然後連結到 JBoss

WebLogic 自定的 Annotations
WebLogic 有自己的 servlet 跟 filter 的annotations.但因為這不是Java EE 的標準。請直接把這個換掉吧!
WebLogicJava EE 6 EquivalentJava EE 6 Import
@WLServlet@WebServletjavax.servlet.annotation.WebServlet
@WLFilter@WebFilterjavax.servlet.annotation.WebFilter
@WLInitParam@WebInitParamjavax.servlet.annotation.WebParam

EJB 3
我不想寫EJB2, 如果你是用EJB 2 ,那我真的建議你整個改寫吧,不管是效能上,還是可維護的程度上都不可以比的!所以拜託!先做 EJB 2 到 EJB 3的 migration吧。
EJB 的寫法,請到這裡參考。
唯一要注意一下的部分反倒是 EJB Client 呼叫的時候,要稍微注意一下API。 裡面用 Context.INITIAL_CONTEXT_FACTORY 跟 Context.PROVIDER_URL的。
在Weblogic 裡面是 import weblogic.jndi.WLInitialContextFactory 但是在JBoss 是用標準的 org.jnp.interfaces.NamingContextFactory 。除了這個之外,另外也可以使用org.jboss.naming.HttpNamingContextFactory 或是org.jboss.security.jndi.JndiLoginInitialContextFactory

JMS
Weblogic
Domain 環境下的config.xml
<jms-system-resource> - connection pool 相關設定
<target> - Server or Host to deploy the connation pool
<descriptor-file-name> - connection pool configuration file.
conf/jdbc *-jdbc.xml

JBoss
Connection Factory 設定位置
deploy/jboss-messaging.sar/connection-factories-service.xml
Queue and Topic 的設定位置
*-service.xml

JDBC 
Weblogic
Domain 環境下的config.xml
<jdbc-system-resource> - connection pool 相關設定
<target> - Server or Host to deploy the connation pool
<descriptor-file-name> - connection pool configuration file.
conf/jdbc *-jdbc.xml

JBoss
*-ds.xml
Samples already in JBoss


Comments

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 …