Connectors

Operaton Connect provides a simple API for connecting HTTP services and other things. It aims at two usage scenarios: usage in a generic system such as the Operaton process engine and standalone usage via API.

Connectors

Operaton Connect provides a HTTP and a SOAP HTTP connector. If you want to add an own connector to Connect please have a look at the extending Connect section. This section also describes the usage of a ConnectorConfigurator to configure the connector instances.

During the request invocation of a connector an interceptor chain is passed. The user can add own interceptors to this chain. The interceptor is called for every request of this connector.

connector.addRequestInterceptor(interceptor).createRequest();

Maven Coordinates

Connect can be used in any Java-based application by adding the following maven dependency to your pom.xml file:

Operaton BOM

If you use other Operaton projects please import the Operaton BOM to ensure correct versions for every Operaton project.

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.operaton.connect</groupId>
      <artifactId>operaton-connect-bom</artifactId>
      <scope>import</scope>
      <type>pom</type>
      <version>${version.operaton}</version>
    </dependency>
  </dependencies>
</dependencyManagement>

<dependencies>
  <dependency>
    <groupId>org.operaton.connect</groupId>
    <artifactId>operaton-connect-core</artifactId>
  </dependency>

  <dependency>
    <groupId>org.operaton.connect</groupId>
    <artifactId>operaton-connect-connectors-all</artifactId>
  </dependency>
</dependencies>

Operaton Connect is published to maven central.

Process engine plugin

If you are using Connect in the Operaton process engine, you also need the operaton-engine-plugin-connect dependency. For more information, refer to the Connectors guide.

Logging

Operaton Connect uses operaton-commons-logging which itself uses SLF4J as a logging backend. To enable logging a SLF4J implementation has to be part of your classpath. For example slf4j-simple, log4j12 or logback-classic.

Apache HTTP Client 5.x has built-in SLF4J support, so no additional bridges are required for HTTP client logging.