Interface ProcessEngine

All Superinterfaces:
All Known Implementing Classes:

public interface ProcessEngine extends ProcessEngineServices
Provides access to all the services that expose the BPM and workflow operations. Typically, there will be only one central ProcessEngine instance needed in a end-user application. Building a ProcessEngine is done through a ProcessEngineConfiguration instance and is a costly operation which should be avoided. For that purpose, it is advised to store it in a static field or JNDI location (or something similar). This is a thread-safe object, so no special precautions need to be taken.
Tom Baeyens, Joram Barrez, Daniel Meyer
  • Field Details

  • Method Details

    • getName

      String getName()
      The name as specified in 'process-engine-name' in the camunda.cfg.xml configuration file. The default name for a process engine is 'default
    • close

      void close()
    • getProcessEngineConfiguration

      ProcessEngineConfiguration getProcessEngineConfiguration()