Application: It aggregates account details of customers across various Financial institutions and populates in a dashboard
Current State: It uses spring as an architectural framework and is currently deployed in Web Logic
We need to migrate this into Cloud native application running on top of spring boot.
Most of our Customer challenges for bulk migration say around 1000+ apps, manual steps are a hinderence, we have looked to automate as many as we can.
Bunch of manual steps – change config files @ weblogic, app server related settings, ssl profiles, url, jdbc connections strings, Application.yaml.
Targetting different build servers and SCM
Code changes, http session, hard coded IP addresses , in mem http sessions
For cloud migration, deployment profiles targeting various cloud providers.
DB migration – Like to Like from on prem to cloud, with schema migration and mounting data on the instances.
We will walk through CLM migration – IN this case
Configuring repository – IN this case we are doing SVN but
We can do git, gitlab, github etc as well..
Here the tool runs the code base through a patented set of rules, called CCAT – which helps identify changes in an application which doesn’t complies with the cloud principals.
The tool and rules are platform and language agnostic. We can always configure rules within the system to adhere to the enterprise standards in addition to the industry specifies for example a logicstic customer of ours have broken these into a set of 29 rules.
When CCAT runs through the application, it identifies all the violations, estimates efforts for remediation, auto remediate some 30% of violations and flags the remaining to help development team to concentrate and correct.
It divides all the violations into 4 categories: Blocker, Major, Minor, Info
**************Explaination for all those follow ************* to display a dashboard on the next slide
Here the tool runs the code base through a patented set of rules, called CCAT – which helps identify changes in an application which doesn’t complies with the cloud principals.
The tool and rules are platform and language agnostic. We can always configure rules within the system to adhere to the enterprise standards in addition to the industry specifies for example a logicstic customer of ours have broken these into a set of 29 rules.
When CCAT runs through the application, it identifies all the violations, estimates efforts for remediation, auto remediate some 30% of violations and flags the remaining to help development team to concentrate and correct.
It divides all the violations into 4 categories: Blocker, Major, Minor, Info
**************Explaination for all those follow ************* to display a dashboard on the next slide