Skip to main content

Fuse Integration Service - Getting your Local Environment ready!

Fuse Integration Service allows developer to package and build application into containerized docker image, the whole idea of how the software is package should not impact how the developer works. But what if a developer wants to start developing without the OpenShift environment?  Since Docker is only available on linux (unless you install conversion tools), in majority of cases, developer would be working on either Windows or Max OS.  So I am going to show you how to setup your own OpenShift in your laptop(desktop).

You will need to have download the following OpenSource software.


Installing above software are pretty straight forward, just follow the default installation instruction. Then we are going to setup our Vagrant virtual machine to run the containerized version of OpenShift Enterprise on our laptop. Go to openshift-vagrant project to get the developer tooling.

Create a folder in your machine, and download the openshift-vagrant by

  • git clone https://github.com/redhat-developer-tooling/openshift-vagrant.git

Go into the openshift-vagrant/cdk-v2 folder, before we start setting up the application, there are a few plugin w have to install, run the following command to install the plugins.

  • vagrant plugin install vagrant-registration 
  • vagrant plugin install vagrant-adbinfo 
(OPTIONAL)And registered your account in the rhn network, and has subscription to RHEL server. To register you account find a RHEL server and register your account 
  • subscription-manager register --username <username> --password <password> --auto-attach
(OPTIONAL) Back to your local laptop command line console, set the registered account info by running following command.
  •  export SUB_USERNAME=<your-subscription-username>
  •  export SUB_PASSWORD=<your-subscription-password>
(NOTE: you do not have to have the RHEL account, if you you don't have one, don't worry about the two above steps)

And finally, go back your machine, under openshift-vagrant/cdk-v2   we can get started to install OpenShift on our laptop run 
  • vagrant up
(NOTE:
If you did not set the SUB_USERNAME and SUB_PASSWORD,  you will be promoted with option during setup,

  • Would you like to register the system now (default: yes)? 

please type "n" to avoid registering.)

If everything installed went well, you should be able to see the OpenShift console (http://10.1.2.2:8443/console) in your browser. 


Run and setup the Atomic Developer Bundle, to setup your Docker environment
  • eval "$(vagrant adbinfo)"

   export DOCKER_HOST=tcp://10.1.2.2:2376
   export DOCKER_CERT_PATH=<your_local_cert_path>
   export DOCKER_TLS_VERIFY=1
   export DOCKER_MACHINE_NAME=<your_docker_machine>

this will disable your OpenShift container, so we will need to restart using vagrant command.
  • vagrant provision
Next, we want to download install OpenShift CLI, 
  • Microsoft Windows
  • Apple OS X
Extract the downloaded file to a folder of your preference, and add the oc to 
  • export PATH=$PATH:<your-oc-extract-path>
Now, in your browser, go to OpenShift Console http://10.1.2.2:8443/console/,  and login with your register ID/PWD, if you did not supply anything, type in admin/admin (or anything you prefer) as ID/PWD.  Create your first project by clicking on "New Project":


Type "demo" for the project name



Once you see the project on the console, congratulation!



You have successfully setup the environment.

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…