The client had a legacy middleware built on top of .NET with C#. This middleware served as a critical point-to-point interface connecting their Point-of-Sale (POS) and their Loan Originating System (LOS). With the goal of embracing digital transformation, the could-based POS system, Virgo, embarked on an application modernization journey. As part of this modernization effort, the POS application underwent an upgrade to adopt the latest industry-specific message standards, specifically transitioning to MISMO 3.4.
However, the LOS (Loan Origination System) application was not migrated to the cloud-based environment and instead remained in the legacy on-premises setup. This decision was driven by the complexity of the business logics embedded within the LOS application. Additionally, the legacy LOS relied on outdated message standards, specifically MISMO 2.31, which has since been deprecated.
One major challenge faced by the organization was the limitations of the legacy middleware in handling the transformation of messages from the upgraded MISMO 3.4 format to the outdated MISMO 2.31 format. To address this issue, there was a pressing need to develop new business logic within the middleware application to ensure compliance with these message standard inconsistencies.
Continue Reading
Unfortunately, the legacy middleware proved to be cumbersome and resistant to embracing these necessary changes and accommodating future innovations within the system.
The client decided to modernize their legacy point-to-point interface than migrating the complex LOS application.
On the whole, the challenges in their legacy middleware application were:
- Monolithic architecture has high coupling and is hard to scale.
- Inconsistencies in message standards between modern POS and legacy LOS applications.
- Reluctance to adopt market changes and future innovations.
- Prolonged time to market.
- Unoptimized code and deployment model.
The client was looking for an integration partner who can collaborate and rebuild their integration points with cloud solutions.
A sneak-peak of Boomi hybrid integration
| Challenge |
Solution |
Business Gain |
| Monolithic middleware application architecture |
Our team rendered the hybrid integration in Boomi to establish connectivity between modern POS (cloud) and legacy LOS (On-Premises) applications |
Enhanced business agility |
| Reluctance to adopt market changes |
Slashed Boomi licensing cost to the minimum with customized utility |
| Traditional deployment process |
Established Centre of Excellence for POS and LOS systems |
Solution: Hybrid integration in Boomi to connect modern POS and legacy LOS with customized utilities
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:
- Integration
- Transformations
Integration
We kick-started the middleware modernization by rebuilding 300+ complex logic in Boomi with customizations. Next, 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.
A positive outcome from this custom hybrid integration is, that we slashed 90% of the client’s Boomi licensing cost.
Transformation
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 imported 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 the MISMO files.
We developed a custom API utility to decrypt attachments using Load ID from the POS application. Through the utilization of the open-source SOFFICE tool and the Boomi Command shape, the utility efficiently delivers attachment files in PDF format, overcoming various input formats. This approach ensures end-to-end encryption of POS messages, effectively addressing associated challenges.
What sets this customized Boomi transformation apart is that it was created without incurring any additional licensing costs. We achieved this by leveraging open-source tools and leveraging the out-of-box features provided by Boomi.
In addition to the aforementioned transformations, we also revamped the deployment process by implementing industry best practices. We guided the client in adopting DevOps practices, resulting in a competitive edge with faster time-to-market and high-quality deliverables.
Business Gains
- Optimized COE that connects cloud-based POS and On-premises LOS application
- 60-70% reduction in interface development time
- 100% flexibility to adopt market changes and future innovations
- 90% reduction in Boomi licensing cost with custom API utilities and open source tools.
- Slashed API connectivity cost with single API and multiple sub-operations architecture
- 75% reduction in deployment efforts
+1 732 737 9188
sales@zeb.co