Hi,

We solve this problem all the time at Pega.  Since our founding, we have seen almost every type of legacy system.  Pega is designed for bi-directional integration with third-party systems through a combination of Services, Connectors, and Transformations, allowing you to leverage your existing enterprise systems. Pega’s unified platform supports connections to other systems via a variety of standard APIs. Standard out-of-the-box Connectors include web services (HTTP, REST, SOAP, WSDL, ODBC, JDBC), EJB, Java, JMS, MQ, .Net, SQL, CMIS, BPEL, ATOM, Cassandra, HBase, Email, and File. Standard out of the box Services, used for allowing external applications to invoke Pega processes, rules, and data, include EJB, COM, CORBA, .Net, MQ, Portlet (JSR-168, WSRP), Email, File, BPEL, Java, JMS, JSR94, MQ, HTTP (URL and REST) and SOAP. As Pega is a 100% JEE compliant solution and is able to be extended with dedicated libraries, extensibility and integration capabilities are not limited to the mentioned technologies.  Our Robotic Desktop Automation and Robotic Process Automation offerings are a nice addition to help complete The E2E journey for mainframe, client-server and other hard to connect applications.  In addition to completing the E2E Journey, you need it to be scalable and performant. Pega is unique by completing the E2E journey and processing millions of transactions per day in each of our vertical markets.

Hope this helps,

Tom