ICICI Bank: four legacy banking applications consolidated on a single Liferay DXP 7.4 platform
India
Four applications, four infrastructures, four logins and four maintenance teams. ATS planned and delivered the phased migration that brought them onto one Liferay DXP 7.4 instance — refactoring MVC portlets to React, unifying the databases and putting enterprise SSO in front of all of it.
The challenge
Four applications, four of everything
ICICI Bank ran four separate enterprise applications, each with its own infrastructure, its own maintenance team and its own user login. For the people using them the experience was fragmented: different credentials, different navigation, different behaviour. For the bank it meant four sets of servers to run and patch, four teams to fund, and a security posture that varied from application to application because each had grown up on its own.
The mandate was a single platform that would cut total cost of ownership while improving compliance and developer velocity — without a big-bang cut-over that a bank's operations could not tolerate. The target was Liferay DXP 7.4, and ATS's Liferay practice was engaged to plan and deliver the consolidation, from environment build through to the CI/CD pipeline that would keep the new platform releasable.
Our approach
A phased migration, one application at a time
Delivered by our Liferay DXP practice.
ATS architected a phased strategy rather than a single migration event. The shared platform — the Liferay DXP 7.4 instance, its Oracle database, the environments and the enterprise SSO — was built first, so each application had somewhere stable to land. The four applications then moved onto it in sequence, each phase ending with the retired application's users and data fully on the new platform before the next began.
Moving code as-is would have carried the old problems forward, so the custom MVC portlets were refactored into React-based portlets during the move. That gave each application a modern interface on the shared platform while keeping the business logic in Java 11 and Spring MVC where it belonged. The four database schemas were unified into one model, and SSO replaced the separate logins so a user signs in once and reaches every consolidated application.
- Platform first: the Liferay DXP 7.4 instance, Oracle DB, Tomcat environments and enterprise SSO in place before any application moved
- One application per phase, with users and data cut over before the next phase began
- Custom MVC portlets refactored to React portlets during migration, not after
- Four database schemas unified into a single model on Oracle
- Server setup, environment configuration and CI/CD pipeline delivered end-to-end by ATS
Architecture
One Liferay DXP 7.4 platform: React in front, Java 11 behind
The consolidated platform runs Liferay DXP 7.4 on Java 11 and Tomcat, built with Gradle, with a single Oracle database behind it. The application logic lives in Spring MVC modules; the user interface is delivered by React portlets, so the front end could be modernised without rewriting the services underneath. Enterprise SSO is integrated at the platform level, which is what let four logins become one.
Around the platform, ATS set up the servers and environment configurations and established the CI/CD pipeline — the piece that turns a one-off consolidation into an ongoing capability. With every application on one platform and one pipeline, a change is built, tested and released the same way regardless of which of the four original applications it belongs to. That is where the developer-velocity goal was met. The same platform-first sequencing underpins our Liferay upgrade and migration engagements.
Building blocks
- Liferay DXP 7.4 · Java 11 · Spring MVC · React portlets · Gradle
- Single Oracle DB with a unified schema replacing four separate databases
- Tomcat application servers with standardised environment configuration
- Enterprise SSO integration across all consolidated applications
- CI/CD pipeline for build, test and release on the shared platform
Technology stack
What changed
Less infrastructure, one login, faster pages, one support model
Consolidating four applications onto one platform reduced infrastructure cost by 45%. The React portlet migration improved page load performance by 55% over the MVC portlets it replaced. Enterprise-wide SSO eliminated login friction: one set of credentials for everything the bank had consolidated.
The organisational change was as large as the technical one. Four separate maintenance teams became a single support model, reducing operations overhead by 50%, and the shared CI/CD pipeline gave the bank one way to ship changes across what had been four codebases. For another banking platform delivered on Liferay DXP 7.4, see the Bank of Baroda EWS migration; for how we scope this kind of work, see Liferay upgrade & migration services.
Key results
Infrastructure cost reduced by 45% through application consolidation
User login friction eliminated via enterprise-wide SSO implementation
React portlet migration improved page load performance by 55%
4 separate maintenance teams consolidated into a single support model, reducing ops overhead by 50%
From the blog
All articlesMore from the portfolio
All projectsLet’s work together
Ready to build something great?
Tell us about your project. We respond within one business day and can provide a customised quote for your requirements.