With the dependency camunda-connect, the process engine supports simple connectors. Currently the following connector implementations exist:
It is also possible to implement your own custom connector in camunda. For more information about extending connectors please visit the Connector reference.
Configure Camunda Connect
As Camunda Connect is available only partially when using the process engine (check the list below). With a pre-built distribution, Camunda Connect is already preconfigured.
connect artifacts exist:
camunda-connect-core: a jar that contains only the core Connect classes. The artifact already is available as dependency to the process engine. In addition to
camunda-connect-core, single connector implementations like
camunda-connect-soap-http-clientexist. These dependencies should be used when the default connectors have to be reconfigured or when custom connector implementations are used.
camunda-connect-connectors-all: a single jar without dependencies that contains the HTTP and SOAP connectors.
camunda-engine-plugin-connect: a process engine plugin to add Connect to the Camunda Platform.
Please import the Camunda BOM to ensure correct versions for every Camunda project.
camunda-connect-core contains the core classes of Connect. Additionally, the HTTP and SOAP connectors can be added with the dependencies
camunda-connect-soap-http-client. These artifacts will transitively pull in their dependencies, like Apache HTTP client. For integration with the engine, the artifact
camunda-engine-plugin-connect is needed. Given that the BOM is imported, the Maven coordinates are as follows:
<dependency> <groupId>org.camunda.connect</groupId> <artifactId>camunda-connect-core</artifactId> </dependency>
<dependency> <groupId>org.camunda.connect</groupId> <artifactId>camunda-connect-http-client</artifactId> </dependency>
<dependency> <groupId>org.camunda.connect</groupId> <artifactId>camunda-connect-soap-http-client</artifactId> </dependency>
<dependency> <groupId>org.camunda.bpm</groupId> <artifactId>camunda-engine-plugin-connect</artifactId> </dependency>
This artifact contains the HTTP and SOAP connectors as well as their dependencies. To avoid conflicts with other versions of these dependencies, the dependencies are relocated to different packages.
camunda-connect-connectors-all has the following Maven coordinates:
<dependency> <groupId>org.camunda.connect</groupId> <artifactId>camunda-connect-connectors-all</artifactId> </dependency>
Configure the Process Engine Plugin
camunda-engine-plugin-connect contains a class called
org.camunda.connect.plugin.impl.ConnectProcessEnginePlugin that can be registered with a process engine using the plugin mechanism. For example, a
bpm-platform.xml file with the plugin enabled would look as follows:
<?xml version="1.0" encoding="UTF-8"?> <bpm-platform xmlns="http://www.camunda.org/schema/1.0/BpmPlatform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.camunda.org/schema/1.0/BpmPlatform http://www.camunda.org/schema/1.0/BpmPlatform "> ... <process-engine name="default"> ... <plugins> <plugin> <class>org.camunda.connect.plugin.impl.ConnectProcessEnginePlugin</class> </plugin> </plugins> ... </process-engine> </bpm-platform>
When using a pre-built distribution of Camunda Platform, the plugin is already pre-configured.
To use a connector, you have to add the Camunda extension element connector. The connector is configured by a unique connectorId, which specifies the used connector implementation. The ids of the currently supported connectors can be found at the beginning of this section. Additionally, an input/output mapping is used to configure the connector. The required input parameters and the available output parameters depend on the connector implementation. Additional input parameters can also be provided to be used within the connector.
<serviceTask id="soapRequest" name="Simple SOAP Request"> <extensionElements> <camunda:connector> <camunda:connectorId>soap-http-connector</camunda:connectorId> <camunda:inputOutput> <camunda:inputParameter name="url"> http://example.com/webservice </camunda:inputParameter> <camunda:inputParameter name="payload"> <![CDATA[ <soap:Envelope ...> ... // the request envelope </soap:Envelope> ]]> </camunda:inputParameter> <camunda:outputParameter name="result"> <![CDATA[ ... // process response body ]]> </camunda:outputParameter> </camunda:inputOutput> </camunda:connector> </extensionElements> </serviceTask>