The business logic integration platform

It is also important to understand that jBPM is a part of a package provided by JBoss, the Business Logic Integration Platform (BLIP) that consists of the following:

Together they form a complete solution for knowledge-based application development and management for enterprise solutions.

BILP can be visualized as a rapid enterprise application development platform from which applications can be solely built by modeling rules, business process flows, events, data models, and forms with very little help from the technical users. The technology and its tools have dual focus: they explicitly serve business users, enable these users to express requirements directly by modeling, and help to engage them in the application development process, guided by technical users who make the models fully functional and realize the software application with all its qualities (nonfunctional requirements).

BLIP integrates the following three paradigms in business language-driven applications:

These paradigms, although developed as three different streams, as obvious from the definitions itself, are interrelated in a business solution context. No wonder in most of the solution architectures, these three form the cornerstones of business modeling.

These paradigms are integrated into a unified platform, where all features of one module are leveraged by the other modules. The decision-making (from the knowledge base) capabilities in Drools Expert are used by Drools Fusion; the event processing capabilities of Drools Fusion can be used by the BPM suite jBPM; and jBPM uses Drools Expert internally for executing business rule tasks.

The following figure depicts this integration and the interactions between the modules in the platform. Drools Guvnor is used for designing processes, events, rules, and related artifacts; storing them; and providing integrated testing facilities. As an integrated platform, BLIP allows interactions between rules, processes, and events.

As depicted in the preceding diagram:

We have already discussed the overview of jBPM; now, let us briefly discuss the other component in the platform in subsequent sections.

Working together

Now that we have discussed the tools, we can now move on to visualize how these tools work together to make a business solution that is completely rule-driven. The following figure provides a bird's eye view of a possible solution architecture where we use these tools together.

Together, they enable business analysts to write and manage applications by mapping business scenarios to process definitions, rule definitions for decisions, and rules including temporal logic.

1. The designer tools enable business analysts to map the business scenarios required for a solution to rules, processes, events, or related artifacts.
2. The applications/users can interact with the solution by using the operation management tooling provided by jBPM, or they can use the RESTful web service interface to access the same from their proprietary applications.
3. The runtime integrates the business processing, rule inference, and temporal reasoning capabilities to infer decisions and take actions for a business scenario.
4. The knowledge repository module provides storage, version management, deployment, and testing of the applications developed.

Another important thing I want to highlight from the preceding figure is the technology platforms used by the individual tools. The web-based user interface for process designing and operation management is developed using the UberFire framework; the Eclipse-based tooling is based on eclipse RCP; the runtime is based on the Kie framework; and Guvnor is based on virtual file system-based storage and by default uses Git. The details of these technology platforms so as to customize and extend jBPM will be discussed in Chapter 7, Customizing and Extending jBPM.

Red Hat also provides a commercially supported flavor of this package and is called Red Hat JBoss BPM Suite.