Mapping TIBCO BusinessWorks 5 activities onto Apache Camel: one activity at a time, with the behavioural differences written down.https://esbexit.com/en-gbhttps://esbexit.com/catalog/http-receiver/https://esbexit.com/catalog/http-receiver/The entry point of most BusinessWorks services. Becomes a platform-http route that accepts every method on the path and only ever sets one fallback response body.Thu, 20 Aug 2026 00:00:00 GMTHTTPtranslatedhttps://esbexit.com/catalog/mapper/https://esbexit.com/catalog/mapper/Builds one document from another. The generator only translates the narrowest case, a bare variable-to-variable copy, and even then drops the source field path; everything else becomes a bean call the rule does not write.Thu, 20 Aug 2026 00:00:00 GMTGeneraltranslatedhttps://esbexit.com/catalog/assign/https://esbexit.com/catalog/assign/Writes a process variable. The generator stores the XSLT source as a string, under the activity name rather than the variable name, and keeps only the first field.Mon, 17 Aug 2026 00:00:00 GMTCorecaveathttps://esbexit.com/catalog/call-process/https://esbexit.com/catalog/call-process/Calls another process inside the same job. The generator emits a direct hop, flattens the input mapping into headers and drops the output.Mon, 17 Aug 2026 00:00:00 GMTCoretranslatedhttps://esbexit.com/catalog/catch/https://esbexit.com/catalog/catch/A fault handler attached to a process or a group. The rule that maps it only fires if a transition points at it, and TIBCO Designer normally wires a handler outside the transition graph.Mon, 17 Aug 2026 00:00:00 GMTCoretranslatedhttps://esbexit.com/catalog/generate-error/https://esbexit.com/catalog/generate-error/Raises a declared fault with a data payload. The generator throws one exception class with the activity name as its message, and the payload does not travel.Mon, 17 Aug 2026 00:00:00 GMTCoretranslatedhttps://esbexit.com/catalog/http-request/https://esbexit.com/catalog/http-request/Sends an outbound HTTP call. The generator wires the route but delegates URL construction to a bean it auto-stubs as a no-op, so the route compiles before anyone has implemented it.Mon, 17 Aug 2026 00:00:00 GMTHTTPtranslatedhttps://esbexit.com/catalog/get-shared-variable/https://esbexit.com/catalog/get-shared-variable/Reads engine-wide state. The generator emits setBody from an exchange property named after the reading activity, which is never the name the write used.Mon, 17 Aug 2026 00:00:00 GMTCorecaveathttps://esbexit.com/catalog/jms-queue-request-reply/https://esbexit.com/catalog/jms-queue-request-reply/Sends a request over JMS and waits for a correlated reply. It shares the same destination-resolution rule as JMS Queue Sender, and the same real-world outcome.Mon, 17 Aug 2026 00:00:00 GMTJMScaveathttps://esbexit.com/catalog/engine-command/https://esbexit.com/catalog/engine-command/Issues a runtime command to the BusinessWorks engine itself, shutdown, process introspection, exception listing. There is no rule for it; the generator falls through to a TODO.Mon, 17 Aug 2026 00:00:00 GMTCoremanualhttps://esbexit.com/catalog/jms-topic-publish/https://esbexit.com/catalog/jms-topic-publish/Publishes a message to a JMS topic. Same destination rule as the queue send, so the same unresolved-destination outcome in practice.Mon, 17 Aug 2026 00:00:00 GMTJMScaveathttps://esbexit.com/catalog/jms-queue-send/https://esbexit.com/catalog/jms-queue-send/Publishes a message to a JMS queue. In practice the destination almost never resolves, because the rule reads a config key the activity's schema never puts it under.Mon, 17 Aug 2026 00:00:00 GMTJMScaveathttps://esbexit.com/catalog/rethrow/https://esbexit.com/catalog/rethrow/Re-raises the fault being handled, preserving its type and data. The generator constructs a new technical fault instead, which changes both the type and where the error goes.Mon, 17 Aug 2026 00:00:00 GMTCoretranslatedhttps://esbexit.com/catalog/set-shared-variable/https://esbexit.com/catalog/set-shared-variable/Writes engine-wide state that outlives the job. The generator turns it into an exchange property named after the activity, so nothing outside that one exchange can see it.Mon, 17 Aug 2026 00:00:00 GMTCorecaveathttps://esbexit.com/catalog/critical-section/https://esbexit.com/catalog/critical-section/A BusinessWorks Critical Section serialises access to a shared resource. Camel has no direct analogue, and what you choose instead depends on whether the lock was ever really cluster-wide.Wed, 12 Aug 2026 00:00:00 GMTGroupingcaveathttps://esbexit.com/guides/checkpoint-recovery/https://esbexit.com/guides/checkpoint-recovery/BusinessWorks Checkpoint has no Camel equivalent. This is an architectural decision, not a translation. Here are the three viable answers and what each costs.Mon, 10 Aug 2026 00:00:00 GMTGuide