Skip to main content

JBoss Fuse - Tips, Offline Repository in Fuse

JBoss Fuse relies very heavy on maven, as it uses maven to control the dependencies for projects and jars it is using. Most of the repository settings can be found in this configuration file:

Under $FUSE_INSTALL_FOLDER/etc/ org.ops4j.pax.url.mvn.cfg

Inside this file, take a look at 2 configurations,

  • org.ops4j.pax.url.mvn.defaultRepositories
  • org.ops4j.pax.url.mvn.repositories
Or if you are using fabric, the same settings are available under io.fabric8.agent.properties in your  default profile.

The org.ops4j.pax.url.mvn.defaultRepositories, sets the location of the local repository for your Fuse to look up.  The default location are under the system folder.

And of course org.ops4j.pax.url.mvn.repositories are the external repository settings for your fuse to scan. Here are the list of default repos.   

  • https://repo.fusesource.com/nexus/content/groups/public/
  • http://repository.jboss.org/nexus/content/repositories/fs-public/
But there are often time where you don't have limited access to the world wide web, maybe it's just bad internet connection or security issues.

Inside Red Hat Fuse documentation, they showed you how to create a custom repository, where they showed you how to properly use the "" plugin to generate the necessary repo. I highly recommend you read through the documentations if you have time.

However a lazy person like me, I always tried to find some easy way out of configuring and setups. Just want to warn you, this may not be the proper way. But it works for me :)

First thing first, you got to have maven installed in your local machine, and that's about it! And I am assuming you have setup to connect to the Fuse and other needed repo too.

Find the setting.xml file, with

  • Mac or Unix, 
    • ~/.m2
  • Windows 
    • D:\Documents and Settings\{your-username}\.m2
  • Linux
    • /home/{your-username}/.m2/


And under the settings.xml, find the tag name:

<settings>
  <!--.....-->
  <localRepository>/path/to/local/repo</localRepository>
  <!--.....-->
</settings>

if you have a brand new maven installed, then you may have to create the xml file and add the tag by yourself.

OK, now,create a NEW temporary working folder and place the path in  "localRepository" tag. I prefer to put it in the same folder as the local system folder as later on I need to compare it using my script.

<settings>
  <!--.....-->
  <localRepository>//Desktop/jboss-fuse-6.1.1.redhat-412/tmprepo</localRepository>
  <!--.....-->
</settings>

Next, go back to your IDE, run a simple mvn clean install, so what this does, it actually starts download all the needed dependencies into the folder, by all, I mean it. So it is going to take a very long time to download.


Once you got everything downloaded, I want to quickly show you something, check your local repo in the system folder with your new temporary working folder. you will find there are lots of duplications of files. That is because we tried to download all the dependency to local, and we don't know which one has already existed, that's why it downloads them all.

Now we have the entire dependency repo, you can either point to this local repo directly in your org.ops4j.pax.url.mvn.defaultRepositories setting, or you can clean it up a bit using my script.

#create directories in the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" |xargs -I{} bash -c 'if [ -d {} ]; then mkdir -p newrepo/{} ; fi '

#create directories in the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" |xargs -I{} bash -c 'if [ ! -d {} ]; then mkdir -p newrepo/$(dirname {}) ; fi '

#copy all files over to the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" | xargs -I{} cp -rf {} newrepo/{}

This script checks for the repo that are not in system, can copy them out to another folder called "newrepo". So I have actually clean up the files and jars that are existed in the system folder.
(Tested on Mac and Linux, please contribute the Window version, sorry, I am not a windows person :p )

So far so good, now we are ready to point the org.ops4j.pax.url.mvn.defaultRepositories to our new repo
   file:${karaf.home}/newrepo/tmprepo/@snapshots 

And remove all proxy maven look up by adding "#" in-front all of them.


That's all. For me, this is much easier then to config a bunch so set ups. But again, this is just a tip, the recommended way is to use the one in the documentations!


Comments

Popular posts from this blog

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 。
加上…

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…

The rise of Agile Integration, Integration is not DEAD nor LAME!

I wanted to blog about this for a very long time, but because of work and being too lazy to turn on my laptop on the weekends, now I finally have a couple of hours to sit down and start blogging.

"Integration is DEAD."
"No, no, let's talk about microservice!!"
"What is that again? Integration, you mean SOA? It's lame... ".

These makes the majority of the percentage when I talk about Integration. In fact, if you happen to be in any the software conference, you see the rooms full when it's about "container" and "microservice." I understand the nature of a developer, always seeking for the latest and greatest technology out there. BUT!! In my opinion, I don't think Integration is going AWAY if you containerize your application. Neither does it will DISAPPEAR in a microservice architecture. In fact, Integration just gets more complicated and tricky when you try to break an application into smaller pieces and have them runni…