What it does in BusinessWorks
Engine Command talks to the BusinessWorks engine process rather than to the message in flight.
<config><command> picks the operation, among them Shutdown, GetProcessInfo and
GetExceptions, and the activity’s output carries whatever that command returns: a list of running
jobs, the engine’s own exception log, or nothing at all for a command like Shutdown that acts and
does not answer.
Nothing about this activity is portable in principle. It is addressing a specific engine instance, using an API that belongs to the BusinessWorks runtime and to nothing else.
The Camel equivalent
There is no equivalent to show. The activity is not a message-processing step with a Camel counterpart under a different name; it queries or controls the process that is running the integration, and Camel has no such process to query in the same sense. A Quarkus or Spring Boot runtime exposes its own operational surface (actuator endpoints, JMX, a management API), and whatever the source process was using Engine Command for has to be re-derived against that surface, not translated activity by activity.
Where the semantics diverge
The three commands are three different problems. Shutdown is an operational action with no
Camel equivalent inside a route: stopping a running service from inside itself is an anti-pattern
in a runtime meant to stay up. GetProcessInfo and GetExceptions are introspection: reading them
back means reimplementing them against whatever the target runtime exposes for job tracking and
error history, which BusinessWorks and Camel do not model the same way.
Nothing about <command> is read by the generator. Every case above needs a person to look at
the source and decide the replacement; none of them can be inferred from the activity alone.
Treat every Engine Command in the estate as a design question rather than a mapping: what was it actually monitoring or controlling, and does the target runtime need that capability replaced at all, or does the reason for it disappear along with the BusinessWorks engine.
What the toolchain does
No rule exists for this type. It falls through to the generator’s default case, which emits
.log(LoggingLevel.WARN, "TODO <activity name> [com.tibco.pe.core.EngineCommandActivity]") and
nothing else. The command, its target and its output are all discarded.