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.

With OpenLegacy, it took only two clicks to get REST API to get to digital. We did a pilot and saw that it was easy to do. We can create REST APIs with a basic understanding of the mainframe's business logic, and without having significant Java knowledge.

Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles. In addition, OpenLegacy gives us a unified way of “calling” the mainframe programs both in 3270 screens and programs.

Digital is one of our biggest priorities and when we heard what OpenLegacy could do, we actually pursued them. Time to market is a big factor. OpenLegacy helps fill our requirement to go mobile and get more interactive between customers and our business via mobile.

The product has helped our business by allowing us to become more efficient in data handling. In this way, it has helped us quite a lot. We had several legacy systems, and because we had a lot of separate systems, we had a lot of problems integrating the data for each of them. So we purchased Open Legacy for its integration capabilities and we actually integrated all of them. That efficiency absolutely it helps.

OpenLegacy opens the door to connect modern web products to our old legacy system. Before OpenLegacy, we would either transition our entire system (a huge undertaking) or do painful workarounds to allow for innovative web products to send data back into our system of record.