With many in-house developed systems, there was a high level of technical debt, making it difficult to change, enhance, and integrate. No integration strategy resulted in a large number of point-to-point interfaces based on a variety of technologies, tools, and platforms. Additionally, there was limited documentation on the systems in place.

In the summer of 2013, our legacy modernization team began IBM i (AS/400) development projects. Over the next two years, we built trust, learned core business processes, and helped business and IT in identifying and addressing gaps and pain points.

In the fall of 2013, our integration team was tasked with documenting existing integration solutions and developing the interfaces between e-commerce and back-end IBM i (AS/400) applications. We designed, sized, procured, and configured the infrastructure/application stack. Our team still “owns” the eCommerce interfaces, providing ongoing support, enhancements, and troubleshooting.

In the winter of 2015, our team built a business case for the Integration platform using the MuleSoft stack. We worked with IT leadership on ROI, provided high-level reference architecture, sized the solution, and created a proof of a concept Mule application. The concept application communicates with IBM i (AS/400) via custom Java components, as well as template IBM i (AS/400) code that “talks” to Mule.

The professional services team of Infoview’s integration team continued with over 25 MuleSoft integration projects in the customers’ pipeline. This was done in addition to working with IT management on the 2016 Road Map to include implementing the API management platform and considering using CloudHub for integrating with SaaS providers.