One engineer, writing down what the migrations taught.

ESB Exit is written and maintained by Karol Krawczyk, an integration engineer and a contributor to Apache Camel (k-krawczyk). The last few years have been spent migrating TIBCO BusinessWorks estates onto Apache Camel, 5 and 6, in telco and in banking. The toolchain and the catalog on this site target BusinessWorks 5.

This site exists because the same twenty problems came up on every engagement and nobody had written them down. The toolchain exists because solving them by hand, one activity at a time, is not a good use of anyone's month.

The code samples in the catalog are written from scratch for this site. The coverage figures appear only as bands: how often a BusinessWorks activity type occurs, high, mid or low, never a number. Type names are TIBCO product identifiers; no component, service or operation name appears anywhere, and neither does the size of any estate. No client code, no client data, no screenshots of either.

What has been verified is two things, and the toolchain page says how far that goes: the generated output compiles, and a generated Spring Boot application starts with its routes in the started state. No message has been through one, and no output has been compared against the BusinessWorks original.

Contact

[email protected]. Corrections to a mapping page are as welcome as migration questions, particularly from anyone whose estate behaves differently from what a page describes.