OpenLegacy Pros and Cons
It is possible to solve larger legacy API issues on an enterprise level with this product.View full review »
Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services.
Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles.
OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers.View full review »
Opens the door to connect modern web products to an old legacy system.
OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server.View full review »
Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly.View full review »
Debugging and logging for programmers could be better.
We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe.View full review »
I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same.View full review »