Once we have a BPM system component to centralize our process engine, we will need a standard way to access that environment. It is important to expose such environments in order to not clutter other systems with complicated or dependency loaded APIs.

We've seen how to add a web service component to expose the KIE Workbench's internal components through a SOAP-based web service, but there are more standard ways of accessing our environment, which are preconfigured in the KIE Workbench. Those mechanisms also come with client components, based on the RuntimeEngine interface, for which implementations are provided to access the internal runtime engines of the KIE Workbench through the following two protocols:

The following diagram shows how these different ways of connecting external systems to the KIE Workbench are implemented:

As the preceding diagram shows, the RemoteRuntimeEngine object takes advantage...