Our client is a leading mortgage bank based out of the US. The client offers financial assistance for home retention, foreclosure, renovation, disaster relief, professional counselling, and much more. They render services across 400+ branches with 1300+ financial advisors across the country.
The client had a legacy middleware built on top of .NET with C#. This middleware served as a critical point-to-point interface connecting Point-of-Sale (POS) and Loan Originating System (LOS). With the goal of embracing digital transformation, the POS cloud Virgo delved into application modernization. Due to this modernization, the POS application upgraded its industry-specific message standards to MISMO 3.4.
On the flip side, their LOS application was retained on the legacy on-premises environment due to the complex business logics involved in it. Also, the legacy LOS had the message standards in MISMO 2.3.1 that have been denounced.
The legacy middleware had limitations in handling these message transformations from MISMO 3.4 to MISMO 2.3.1. They were in a push to build new business logic in middleware application to comply with these message standard inconsistencies.
Unfortunately, the legacy middleware was cumbersome and reluctant to adopt these changes & future innovations in the system!
Our integration specialists delved in and scrutinized the client’s middleware application that connected POS and LOS. We recommended modernizing their legacy point-to-point interface with Boomi solutions.
The primary goal was to reengineer and shift their legacy middleware application to Boomi with a low code/no code approach. We rationalized this Boomi implementation into two segments:
We kick-started the middleware modernization by rebuilding 300+ complex logic in Boomi with customizations. Successively, to integrate the cloud-based POS and on-premises LOS application, we retained the legacy API connectivity by leveraging the environment extension feature of Boomi.
From the POS application, the interface receives the input as a single MISMO file. This single MISMO file must be routed to multiple APIs for further processing. We optimized these multiple API connections as a single API connectivity and multiple sub-operations in Boomi.
To combat the message standard inconsistencies in POS (MISMO 3.4) and LOS (MISMO 2.3.1) applications, we rendered the customized transformation solution using Boomi maps.
As a pre-requisite to this message transformation, we were in need of importing the XSD for MISMO 3.4 standards from the POS application. Due to stringent data governance policies in the fintech space, there was a limitation in getting the input fields. We overruled this challenge by manually rationalizing 10K+ input fields in MISMO file.
We created a custom API utility to decrypt the attachments with Loan ID from POS application. By leveraging the open-source SOFFICE tool, the utility delivers the attachment files in a PDF format despite the input format using Boomi Command shape. With this approach, we accomplished the end-to-end encryption of POS messages despite the challenges.
And the enticing fact of this customized Boomi transformation solution is, that we created an API utility without any additional licensing cost by leveraging open-source tools and out-of-the-box Boomi features!
On top of the above transformations, we re-engineered their deployment process with best-industry practices. We helped them adopt DevOps practices so that they could achieve a competitive edge with faster time to market and quality deliverables.
Want to know more? Let’s connect!
Call Us : +1 732 737 9188
Email Us : firstname.lastname@example.org
Book a Demo
Connect with our experts!
+1 732 737 9188