Uses of Interface
org.camunda.bpm.engine.ProcessEngineInfo
Package
Description
Public API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
Through the services obtained from such a
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration
(typically based on a configuration file), from which a ProcessEngine
can be obtained.Through the services obtained from such a
ProcessEngine
, BPM and workflow operation
can be executed:RepositoryService
:
Manages Deployment
sRuntimeService
:
For starting and searching ProcessInstance
sTaskService
:
Exposes operations to manage human (standalone) Task
s,
such as claiming, completing and assigning tasksIdentityService
:
Used for managing User
s,
Group
s and the relations between themManagementService
:
Exposes engine admin and maintenance operations,
which have no relation to the runtime execution of business processesHistoryService
:
Exposes information about ongoing and past process instances.FormService
:
Access to form data and rendered forms for starting new process instances and completing tasks.API implementation classes, which shouldn't directly be used by end-users.
-
Uses of ProcessEngineInfo in org.camunda.bpm.engine
Modifier and TypeFieldDescriptionprotected static List<ProcessEngineInfo>
ProcessEngines.processEngineInfos
protected static Map<String,
ProcessEngineInfo> ProcessEngines.processEngineInfosByName
protected static Map<String,
ProcessEngineInfo> ProcessEngines.processEngineInfosByResourceUrl
Modifier and TypeMethodDescriptionstatic ProcessEngineInfo
ProcessEngines.getProcessEngineInfo
(String processEngineName) Get initialization results.static ProcessEngineInfo
retries to initialize a process engine that previously failed.Modifier and TypeMethodDescriptionstatic List<ProcessEngineInfo>
ProcessEngines.getProcessEngineInfos()
Get initialization results. -
Uses of ProcessEngineInfo in org.camunda.bpm.engine.impl