Enhancing JBoss BPMS’ Documentation and Searching Capabilities

Some users want to use JBoss Business Process Management Suite (BPMS), or its upstream jBPM Open Source Business Process Management solution, as a documentation tool as well as an executing engine for business processes and business rules, but…

  • BPMS is not designed as a documentation tool
  • BPMS has some metadata search capability but not sufficient for the scenario customers have in mind
  • Customers want a much more powerful search capability
  • Customers want a single source of truth for all business assets for both documentation and execution purposes


I created a couple of youtube videos suggesting how this could be done:

The first video defines the mission and discusses 2 approaches to achieve the mission.

The second video describes how I created a prototype and how it looks like and works. The searching capabilities is on a different level from that of BPMS’.

However, more work needs to be done to realise a proper solution for the problem. I shall be adding more videos when new ideas come to mind. Stay tuned!

JBoss Data Virtualization Part 2 – An Example


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

JBoss Data Virtualization Part 1 – Concept

Data Challenges

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