01 / CATALOG
Mapping catalog
One page per activity the toolchain implements. The Camel equivalent, side by side, and more usefully the exactly where the semantics quietly diverge.
Browse the catalog →TIBCO BusinessWorks 5 → Apache Camel
Your integration layer
should not be
a licence negotiation.
An open-source toolchain and a working reference for moving BusinessWorks 5 estates onto Apache Camel, written by an engineer who does these migrations rather than by a vendor who sells the destination.
Toolchain coverage
Emitted steps that are not a marker 96.37%
Activity occurrences whose type has a rule 98.64%
Weighted by activity occurrences
Activity types seen 77
Verified compiles, starts
What this is
Three things, built in the open, in this order.
What each activity becomes, what no converter can decide for you, and what the move is worth, so leaving BusinessWorks 5 is a costed decision rather than a guess.
02 / TOOLCHAIN
Conversion toolchain
A BW5 project parser, a neutral intermediate model, a Camel route generator and a coverage report. Command line, no IDE, no telemetry.
What it does →03 / GUIDES
Decision guides
Checkpoint recovery first, with transactions, locking and shared state to follow. The parts no converter can decide on your behalf.
Read the guides →Coverage
Measured against a production estate, not a demo.
The corpus is a client's private BusinessWorks 5 estate. How often a type appears is published as a band, never as a count: high is at least 1% of all activity occurrences, mid is between 0.1% and 1%, low is below 0.1%. The size of the estate stays with its owner.
| BusinessWorks type | How often | Rule | Status |
|---|---|---|---|
| pe.core.CallProcessActivity | high | java | Translated |
| pe.core.GenerateErrorActivity | high | yaml | Translated |
| plugin.mapper.MapperActivity | high | java | Translated |
| pe.core.CatchActivity | high | java | Translated |
| pe.core.AssignActivity | high | java-conditional | Caveat |
| plugin.timer.NullActivity | high | yaml | Translated |
| plugin.xml.XMLParseActivity | high | yaml | Translated |
| plugin.timer.SleepActivity | high | java-conditional | Caveat |
| plugin.soap.SOAPSendReceiveActivity | mid | none | Manual |
| pe.core.ConfirmActivity | mid | none | Manual |
| plugin.xml.XMLRendererActivity | mid | yaml | Translated |
| plugin.jdbc.JDBCCallActivity | mid | yaml | Translated |
12 of the 40 types the report breaks out, most used
first. A further 37 fall in the low band and have no rule.
Open the catalog →
Coverage divides by the Camel steps the generator emitted, not by the activities in the source: an activity the graph never reached is in neither half of the fraction. And compiling is not equivalence. Every generated component builds under javac; nothing beyond that has been verified.