How Flowable open source engines connect process and case models to message brokers, integration frameworks, external services and workers in other languages, using the integration points the Flowable docs define.
Driving Flowable processes and cases from Kafka, RabbitMQ or JMS: event and channel definitions, correlation parameters that route an event to the right instance, starting processes from messages, and sending outbound events from models.
Delegating integration logic from Flowable processes to Apache Camel routes with the Camel task: the camelContext bean, sending and receiving messages, using Camel components to reach legacy systems, and where the event registry is the simpler choice.
Running process work outside the Java engine with Flowable external worker tasks: topics, job acquisition over the Java or REST API, workers written in any language, completing and failing jobs, and when this beats Java delegates or HTTP tasks.
Calling REST services directly from Flowable BPMN models with the Http task: HTTP client configuration and timeouts, request and response mapping into process variables, error handling, and securing outbound credentials.
Starting and correlating Flowable processes and cases from RabbitMQ messages with event and channel definitions, sending outbound events from models, and when RabbitMQ is the better broker choice than Kafka or JMS for process events.
Driving Flowable from JMS queues and topics: inbound channels that start processes or trigger boundary events, outbound channels from send event tasks, correlation to running instances, and what to agree with the messaging team.
Sending notification emails from Flowable processes with the email task: SMTP server configuration, recipients and templates from process variables, failure handling with async retries, and when to hand email to a notification service instead.
Using the Flowable web service task to call SOAP services from BPMN models: imported WSDL definitions, data input and output associations, when the HTTP task or a Java delegate is simpler, and testing legacy service calls.
Running Flowable external worker jobs from Python services with Flowable's official client: acquiring and completing jobs over REST, error handling and retries, authentication, and where Python workers fit next to Java delegates.
Implementing Flowable external worker tasks in JavaScript or TypeScript with the @flowable-oss/external-worker-client library: acquiring and locking jobs, signalling completion over REST, basic auth versus tokens, and scaling workers.
Replacing basic authentication on Flowable REST endpoints with Keycloak tokens: Spring Security resource server settings, mapping Keycloak roles to Flowable privileges and candidate groups, and keeping the IDM engine in sync with Keycloak users.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.