1. What is Fuse Ignite?
In 2009, Gartner Says: Citizen Developers Will Build at Least 25 Percent of New Business Applications by 2014.
“…Future citizen-developed applications will leverage IT investments below the surface, allowing IT to focus on deeper architectural concerns, while end users focus on wiring together services into business processes and workflows,” said Eric Knipp, senior research analyst at Gartner. “Furthermore, citizen development introduces the opportunity for end users to address projects that IT has never had time to get to — a vast expanse of departmental and situational projects that have lain beneath the surface…”
That prediction is yet to come true, in my opinion, but the idea of a class of developers in the integration domain referred to as Citizen Integrators was born. Citizen Integrators are the class of integrators whose day job is not in IT Integration. These people understand the business. They are tech savvy to a certain degree but do not necessarily have a deep understanding of the underlying technology. For simple integrations, Citizen Integrators using the proper tools can do the job freeing up expensive IT Integration resources to do more complex integrations.
FUSE Ignite is the tool designed for Citizen Integrators. It is not meant to replace FUSE Standalone or FUSE on Openshift. For complex integrations, FUSE development by developers using an IDE is still the way to go.
FUSE Ignite is supported only on Openshift and comes with a FUSE subscription. Use of FUSE Online, the SaaS version of FUSE Ignite, is not part of a FUSE subscription though.
I evaluated FUSE Ignite in 2 different environments: Fuse Online and on my laptop running “oc cluster up”. My findings are documented below. Continue reading FUSE Ignite – First Impressions
In the previous installment, I outlined the use case or business scenario we are implementing using the 3 JBoss middleware products. In this installment, I am going to describe the Fuse to Business-as-a-service (Business rules application on the Realtime Decision Server) integration which validates the XML data and the Fuse to BPMS integration which kicks off a business process instance for a mortgage application as well as the Fuse to JBoss Data Virtualisation integration. Continue reading Making JBoss Fuse, Data Virtualisation and BPMS Work Together – Part 2
In Part 1, I describe what Data Virtualisation is and how one product, namely JBoss Data Virtualisation, works and its architecture. In this instalment, I am going to describe the implementation of a virtual database using 3 data sources. I am also going to show you how to interact with the virtual database using the SquirrelSQL client. The intention of this article is to give you some ideas as to how easy it is to aggregate several data sources to construct a virtual database. It explains the implementation on a high level only and does not give a step-by-step instruction of how to do it from scratch. Continue reading JBoss Data Virtualization Part 2 – An Example
When you are only having a few applications, it is easy to integrate them using a point-to-point approach ie, each application connects to all the other applications directly to access the information. As the number of applications increases, using the point-to-point approach will result in a non-maintainable mess of spaghetti-like chaos as shown in the diagram below. You may reduce the integration complexity by either introducing an Enterprise Integration Bus (ESB) or by using Data Virtualization. It should be noted that this is not an either-or choice as ESB and data virtualization are the two sides of the same integration coin. ESB is used for application integration and data virtualization is used for data integration. They work together well. Complexity is not the only issue here, how about administering security? In using a point-to-point approach, you have to administer security or access control on each data source for each application. Also, many organizations store information eg, on a customer, using different applications and the information they store may differ slighly from application to application. This means that, depending on the system or application you query, you may end up with conflicting information on a customer. Continue reading JBoss Data Virtualization Part 1 – Concept