org.camunda.bpm.engine
Interface ProcessEngine

All Superinterfaces:
ProcessEngineServices
All Known Implementing Classes:
ProcessEngineImpl

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.

Author:
Tom Baeyens, Joram Barrez, Daniel Meyer

Field Summary
static String VERSION
          the version of the process engine library
 
Method Summary
 void close()
           
 String getName()
          The name as specified in 'process-engine-name' in the camunda.cfg.xml configuration file.
 ProcessEngineConfiguration getProcessEngineConfiguration()
           
 
Methods inherited from interface org.camunda.bpm.engine.ProcessEngineServices
getAuthorizationService, getCaseService, getDecisionService, getExternalTaskService, getFilterService, getFormService, getHistoryService, getIdentityService, getManagementService, getRepositoryService, getRuntimeService, getTaskService
 

Field Detail

VERSION

static final String VERSION
the version of the process engine library

See Also:
Constant Field Values
Method Detail

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()


Copyright © 2015 camunda services GmbH. All rights reserved.