Red Hat JBoss® BPM Suite and Red Hat Decision Manager (formerly Red Hat JBoss BRMS) both use an artifact packaging known as a “KJAR”, or knowledge artifact, since version 6. What is this file type? What separates it from a standard JAR file?
The basic summary
In very few words, a KJAR is a standard JAR file that has some extra files included. A KJAR keeps the same
.jar extension as a JAR file, because its basic file structure is identical to that of a JAR.
Continue reading “What is a KJAR?”
The JBoss Ecosystem is very large and diverse, while you are looking for step by steps and practical introduction to the major JBoss products or looking for tips to improve your business by coupling JBoss Products, this book is for you.
Continue reading “JBoss Developer’s Guide Book is out”
Generally when the topic of Business Process Management (BPM) comes up we think of BPM software suites. There’s another side to BPM though, and that’s the practice of process management, which doesn’t require any software at all.
Traditionally the BPM practice has focused on continuous process improvement. There are various methodologies but it generally comes down to this:
- Collect metrics on the existing process
- Analyze those metrics
- Propose an optimization
- Simulate the optimization with the collected metrics
- Institute the validated optimization
- Do it all again
There’s nothing wrong with that. We’ve occasionally had good results with continuous improvement for processes that are core to a business. A good candidate, for example, would be a fee-for-service health insurance claim process — it’s a process that’s been around for decades and will likely be around for additional decades. It’s also high volume, so even the smallest improvement can have a major impact.
Continue reading “Business process management in a "microservices world"”
One of the core drivers behind modern application architecture, development and delivery methodologies like micro-services, agile and CI/CD is the ability to automatically test any software artifact, from application code to server configuration. Automated testing gives us the reliable, repeatable, assurance that our software meets the required quality with respect to aspects like functionality, performance, and scalability and is ready to be deployed in production. Why should testing of a business-process defined in BPMN2, a deployable software artifact, be any different?
One of the unique features of Red Hat JBoss BPMSuite is that, due to it’s adoption of Maven as de-facto build platform, it allows to utilize standard Java testing practices and methodologies in the business process space. In fact, jBPM (the upstream community project thatforms the base of Red Hat JBoss BPMSuite), provides out-of-the-box JUnit test classes that allow one to easily unit-test business processes defined in BPMN2 (see the jBPM User Guide for more detail).
Continue reading “Unit-testing your BPM processes by bending time.”