* Thanks to its easy to learn Flow language, it’s quite easy to build even complex integration processes
* As build on asynchronous messages exchanges, BPM are more robust against components outages compared to monolithic solution.
* Efficient clustered solution
* Lot of adapters
* Supervision tool (optimize for Infra) is only a joke at least up to 8.2 : It’s missing lot of important figures to really follow ISes’ health (I built in house monitoring based on Flow/Java probes + PHP GUI which is far far more informative than O4I is providing).
* Every patch campaigns needs long regression testings … due to bug and regression introduced by fixes.
* Starting 9.x, administration tools were totally jeopardized among several interfaces : IS Admin, MWS, Terracotta, UM, …
* not always OpenSources friendly. Especially, web services are quite limited (a shame for such product) and I had to fight against wM to make them usable by PHP WS clients : wM's WS stack doesn't support all variants of WS.