This post is part of short session I spoke in Japan, strictly my opinion.

Red Hat JBoss xPaaS allows enterprise to deploy their application both on premise and cloud. Inside this hybrid environment developer does not need to worry about that sort of container or deployment environment it is deploy on. So developer can easily build their application, integrating with other service across enterprise or cloud and even orchestrate business process and rules.  That means developer can now expose their service to the outside world, it can be either through web service, either it's SOAP with XML or Restful API with JSON content.

While I was hosting a workshop on JBoss Fuse, I got a question from on of the partners, why not use ETL?

"ETL (Extract, Transform and Load) is a process in data warehousing responsible for pulling data out of the source systems and placing it into a data warehouse."

To me it's rare to compare between Fuse to an ETL solution, because I think these two should work together to compliment each other. They are solving different problems when integrating.
9

This post is part of short session I spoke in Japan, strictly my opinion.

Red Hat JBoss xPaaS can help enterprise to adopt DEVOPS in many ways. My thoughts of DEVOPS, as in many years in the industry, I believe DEVOPS can be broken down to 3 major part.

This is post is the content of one of the short session I spoked in Japan. and strictly just my opinion.

When I was a enterprise architect (long ago in Taiwan), I'm in-charge of several application in the company, we receive a large number of user requirements per month.  There were about 10 developers in my teams, every time we push out a release, we always deploy it on a testing environment. Depends on if we are busy, we often have many versions deployed on testing environment.

This time I want to talk about the error handling in Camel, when there is calculation, there will be exceptions. I know 99% of the time, it doesn't go the exception, but we don't want this 1% to screw up our entire application. So it is rather important to handle these exceptions carefully.

In Camel, there are three main ways you can handle exceptions,

Error Handler, any exceptions in the message will trigger this handler, so normally I'll use this for a more general base error handling.
3

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.

This is the last part of Fuse workshop 101, we have gone through the development part, what about in real production environment? This workshop is all about the operation and management side of JBoss Fuse. The technology we use for this purpose is called Fabric8. Fabric8 mainly takes care of  provision, automate, configure, and manage from a central location.
3
Popular Posts
Popular Posts
About Me
Archive 檔案室
Labels
Labels
Blog of My Friends
Blog of My Friends
Facebook Groups
Facebook Groups
Support a friend
Support a friend
Loading
Dynamic Views theme. Powered by Blogger. Report Abuse.