Information Technology Reference
In-Depth Information
In the preceding diagram, we can see a few possible combinations. The first one to the
left-hand side of the diagram shows the configuration as it is available in the KIE Work-
bench using a
Virtual File System
(
VFS
) for knowledge definitions, a database to persist
runtime information, and a REST interface to expose information to clients. At the center,
we see a possible alternative where we use a NoSQL persistence for both our runtime and
definitions, and a JMS broker to communicate with clients.
Finally, we see the simplest configuration, where definitions are stored in a plain filesys-
tem as files, access is provided through the jBPM6 API, and no persistence is configured.
This is the least scalable scenario, but it is also a possibility that might be fit for the
simplest cases.
In the next section, we will discuss how we can start changing the KIE Workbench to ad-
apt its internal architecture to our specific needs.
