The ultimate goal of this project was to improve the stability of the application suite as the organization made the transition to a Microservices-style platform. Keyhole consultants assisted with the migration from a monolithic application architecture to a Microservices style that broke up application functionality into smaller runtime elements that could be tested and deployed separately.
In this project, almost 1,000 existing Model 204 batch applications were converted to Java Spring and Spring Batch-based applications.
The goal of this engagement was for Keyhole Software to help the client to implement an application architecture and platform that supports the conversion of its Model 204 applications into Spring Boot-based application modules. There were many modules, both batch and online-based, so this platform needed to allow for scalability and durability. On-demand deployment was also necessary.
The Keyhole team worked to modernize the organization’s enterprise batch processing applications. This project included converting a long list of COBOL batch processing applications into Java-based batch applications using the Spring Batch framework. The project encompasses a wide range of tasks from calculating and assessing fees, to processing large vendor fees, and running recon reports.
Sr. Keyhole Software Consultants engaged with a national provider of vision insurance to strategically improve the company’s Payment Claim batch processes. The client’s existing batch processes had been in the process of migration and rewrite from COBOL to Spring Batch by another consulting firm.
A team of Keyhole Consultants has been focused on a rewrite initiative for a client proprietary Designer tool.
This tool enables a non-programmer to create a form-based web application by dragging UI elements onto a page of a form. The form contains pages that have UI elements. Each element has a number of associated properties, interactive at design-time. Each element can have behaviors that impart program logic to the form. The form can have a workflow associated with it. The tool user interacts with those artifacts by dragging and dropping elements, drawing behavior or workflow connections, modifying properties, and then saving the form, as XML, to a server. A web-based player interprets the form XML to serve it to an end-user as a web application.