JBPM 6 开发者指南 Chapter 7.docx

Chapter 7. Defining Your Environment with the Runtime ManagerBy now, we have seen the two main components of a jBPM6 runtime, the KIE session and the Human task service. These components are provided as the basic components needed to run process interactions between humans and systems. As the responsibilities of the process runtime grows, connectors to external systems should be added to transform the process engine into a highly configurable enterprise integration platform, where coordination between different systems can be easily managed in a business-friendly way.The entire configuration involved in creating a runtime for the process engine, the Human task component, and all the external systems connectors could become cumbersome if not managed in a single place. In this chapter, we will learn about the runtime manager component, which is designed to create a bridge between all the components and configurations involved in a process execution. This component can be used to create a full runtime for the process engine. For this chapter, our goals will be as follows:Understand the role of the runtime manager in the jBPM6 architecture Get familiar with the available runtime managers and interfacesStart extending the API to create our own custom runtime managersUnderstanding the role of the runtime managerThe runtime manager’s main role in an application is to provide an application-wide point to access process runtimes (all the necessary interconnected services to execute a process execution within a specific domain). The nature of those runtimes and how many different runtimes can exist in a particular domain is a decision that each of the runtime manager implementations available has to make. By default, a runtime will be composed of two main components: the KIE session where the process is executed and the Human task component where human tasks will be handled. Both are grouped and returned from the runtime manager through the RuntimeEngine interface:public inte