Camunda 8 Self Managed HTTP calls

Kurtis_Robinson · May 30, 2023, 5:29am

Hello all,

I have been looking into Camunda again and had a question regarding sending HTTP calls from Self Managed. For HTTP Calls, is a worker always required or can Camunda itself be configured to carry out the HTTP calls without a worker? I have got a worker performing this task to send communications to a microservice but it would be more preferable if there was no need for our own worker like the SaaS version.

I have seen the HTTP Connector in mentioned in the documentation but I am unsure what the full setup is aside from adding the elements to the modeler. How would the HTTP connector be added to a docker compose file currently?

Many Thanks, Kurtis Robinson.

tmetzke · May 30, 2023, 5:35am

Hi @Kurtis_Robinson, thanks for your interest! Did you have a look at the Connectors Installation Guide for Self-Managed already?

As detailed, you’ll need to run some kind of backend that executes the Connector logic somehow. For Connectors, you can use the provided Connector Runtime to run ONE job worker that is aware of all configured Connector logic, including the HTTP Connector.

You can include the Connector Runtime in a docker-compose file as shown in our Camunda Platform 8 docker-compose repository:

github.com

camunda/camunda-platform/blob/0c3e68a7bd6b8a8fb55d5b18ca244d9e934181aa/docker-compose.yaml#L130-L162


      
          connectors: # https://docs.camunda.io/docs/components/integration-framework/connectors/out-of-the-box-connectors/available-connectors-overview/
            image: camunda/connectors-bundle:${CAMUNDA_CONNECTORS_VERSION}
            container_name: connectors
            ports:
              - "8085:8080"
            environment:
              - ZEEBE_CLIENT_BROKER_GATEWAY-ADDRESS=zeebe:26500
              - ZEEBE_CLIENT_SECURITY_PLAINTEXT=true
              - ZEEBE_CLIENT_ID=${ZEEBE_CLIENT_ID}
              - ZEEBE_CLIENT_SECRET=${ZEEBE_CLIENT_SECRET}
              - ZEEBE_TOKEN_AUDIENCE=zeebe-api
              - ZEEBE_AUTHORIZATION_SERVER_URL=http://keycloak:8080/auth/realms/camunda-platform/protocol/openid-connect/token
              - CAMUNDA_OPERATE_CLIENT_KEYCLOAK-URL=http://keycloak:8080
              - CAMUNDA_OPERATE_CLIENT_CLIENT-ID=connectors
              - CAMUNDA_OPERATE_CLIENT_CLIENT-SECRET=XALaRPl5qwTEItdwCMiPS62nVpKs7dL7
              - CAMUNDA_OPERATE_CLIENT_KEYCLOAK-REALM=camunda-platform
              - OPERATE_CLIENT_ENABLED=true
              - CAMUNDA_OPERATE_CLIENT_URL=http://operate:8080
              - management.endpoints.web.exposure.include=health
              - management.endpoint.health.probes.enabled=true

This file has been truncated. show original

Hope that helps.

Cheers,
Tobias

Kurtis_Robinson · May 30, 2023, 9:53am

Hi Tobias,

Many thanks, we were a bit confused on our side due to conflicting information so that clears it up a bit.

Just to walkthrough the steps for this then

Configure Docker file Connector Bundle for localhost zeebe
Spin up Self Managed Docker environment
Use either Cloud Modeler or Desktop Modeler (Rest tasks need to be added in element templates folder to show in desktop application)
Deploy and run process.
This should allow rest tasks to be performed.

Is this the correct process or is there anything else that needs configured before use?

Many Thanks, Kurtis Robinson.

Kurtis_Robinson · May 31, 2023, 7:39am

Hi Tobias,

I got it working there with the use of GitHub - camunda-community-hub/camunda-8-friendly-connector-runtime: A connector runtime with UI to manage connectors and secrets as I was having issues with getting the regular runtime going.

Many thanks, Kurtis Robinson.

system · June 7, 2023, 7:40am

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.