Skip to main content

JEAP 5 - 幫J老闆減肥,減少不必要模組負擔

雖然我覺得跟我以前常用大藍的"網路球" 比起來已經是天上跟地下了~~

J老闆非常有彈性 XD,上面所有的東西都像樂高一樣可以拆來拆去!
它的All Profile 裡面,為了要提供許多功能,所以是所有profile裡面的最肥的
據我多年(不要亂猜~我沒有很老) 的經驗,大部份AP根本不會用到它50%的功能!
(JBoss 再startup 的時候,就會把deploy的東西都load 進memory!

那~要減肥也不能把自己的肝砍掉吧 !?
下面就是各功能對應的檔案,list 出來給大家,不要真把自己的有在用的肝砍掉阿XD

如果沒有用 JMS 功能 (provided via JBoss Messaging), 可以移除
  •  $CONFIG/deploy/messaging/
  • $CONFIG/deploy/jms-ra.rar
  • $CONFIG/deployers/messaging-definitions-jboss-beans.xml
  •  $CONFIG/conf/jbossts-properties.xml 裡面的 "XAResourceRecovery.JBMESSAGING1" mark :

<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>

如果沒有用 Mail 的功能的話,可以把這兩個檔案移掉
  • $CONFIG/deploy/mail-service.xml
  • $CONFIG/deploy/mail-ra.rar

如果不用 BeanShell scripts, 把這個移除
  • $CONFIG/deployers/bsh.deployer

如果沒有用EJB 3的話,請移除
  • $CONFIG/deploy/ejb3-connectors-jboss-beans.xml
  • $CONFIG/deploy/ejb3-container-jboss-beans.xml
  • $CONFIG/deploy/ejb3-interceptors-aop.xml
  • $CONFIG/deploy/ejb3-timerservice-jboss-beans.xml
  • $CONFIG/deployers/ejb3-deployers-jboss-beans.xml
  • $CONFIG/deployers/jboss-ejb3-endpoint-deployer.jar
  • $CONFIG/deployers/jboss-ejb3-metrics-deployer.jar
  • $CONFIG/deployers/ejb3.deployer/
  • 然後在deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml 裡面的WarDeployer bean 裡面加上

<property name="persistenceUnitDependencyResolver"><null/></property>

如果沒有用EJB 2 的話 (老天保佑最好沒有~不然本身AP就慢了,神都救不了了!)移除

  • $CONFIG/deploy/ejb2-container-jboss-beans.xml

  • $CONFIG/deploy/ejb2-timer-service.xml
 (移除這個EJB 3可能會掛掉)
如果APweb services 沒有使用UDDI的話, 可以移除

  • $CONFIG/deploy/juddi-service.sar
如果AP裡面沒有timer 的定時作業,也沒用到 EJBtimer 的話,可以移除

  • $CONFIG/deploy/schedule-manager-service.xml
  • $CONFIG/deploy/scheduler-service.xml
  • $CONFIG/deploy/quartz-ra.rar
  • $CONFIG/deploy/ejb3-timerservice-jboss-beans.xml
  •  $CONFIG/deploy/ejb2-timer-service.xml
如果不需要 web services, 請殺掉

  • $CONFIG/deploy/jbossws.sar
  • $CONFIG/deployers/jbossws.deployer
今天沒有圖~看起來好無聊噢!放個照片讓我的小可愛Puji亮亮相好了 !

如果發生很多dependency 的的warning log,其實沒有關係,
但是如果覺得很煩,可以關掉 (EJB 部分,其他我還沒空try)

1.  關掉WebServiceDeployerEJB 的dependency 
  <bean name="WebServiceDeployerEJB" class="org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB">
   <!-- <depends>EJB2xDeployer</depends>
2. 拿掉ejbReferenceResolver 關係
  <bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect">
    <property name="requires">WebMetaData</property>
    <property name="provides">InjectionMetaData</property>
    <property name="ejbReferenceResolver"><null/></property>


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

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 …