Chapter 8. Deploying and configuring the Activiti Engine
This chapter covers
- Choosing between deployment options with the Activiti Engine
- Exploring transaction management with Activiti and Spring
- Configuring the Activiti Engine
- Communicating with the Activiti Engine using the Activiti REST API
In the last two chapters, you were introduced to advanced BPMN constructs, including error boundary events and embedded subprocesses. That’s all great—but how can you install and deploy these advanced BPMN process definitions in your environment? Now, it’s time to take a step back and see how Activiti fits into the big picture of your application landscape.
First, we’ll discuss the two common deployment scenarios for the Activiti Engine: the embedded and the standalone options. In addition, we’ll take a look at how you can use the Spring container for transaction management. With the standalone option, I’ll show how you can use the Activiti REST web application as a foundation for implementing the Activiti Engine in your organization. Then, I’ll show you how to configure the Activiti Engine. Finally, you’ll see how to communicate with the Activiti Engine using the REST API and learn how to add a new Activiti REST service.
First things first: let’s take a look at the deployment options you have with the Activiti Engine and discuss why you would choose one configuration over the other.