- Migration Pattern
- Java framework change
migration-pattern
Migration Pattern
Success Stories
With the only one 100% automated AI-powered conversion and testing technology for modernization, we deliver a genuine open system with exceptional quality and low cost.
Several clients presented case studies at large IT events.
Case study of system infrastructure renewal at Japan Airlines
in Gatner application summit
AIX to Linux
WACs to Struts + Spring
Java upgrade
DB2 upgrade
Renewal of the JAVA framework of the core system!
Development revolution by AI
in IT Modernization Summit
Orteus to SDE
Java upgrade
Oracle upgrade
Applying AppModernizer to the parts purchasing area
in Gartner IT Symposium/Xpo
AIX to Linux
WACs to NSF
Java upgrade
DB2 to Oracle
Doda website framework modernization
in Gartner IT SymposiumXpo
Seasar2 to Spring
Struts1 to Spring
SaStruts to Spring
XenlonFramework to Spring
Java upgrade
Stop the trend of individual optimization and formulate a “Web standard platform”
Sony Life’s style of reform
in iMagazine
WACs to Spring
Struts1 to Spring
ObjectWorks to Spring
Spring upgrade
Java upgrade
the Modernization of Production Statistics Management system
in ABC Association Event
PowerBuilder to Java
Java upgrade
Oracle upgrade
We have successfully completed over 180 Java migration projects.
Currently, we are simultaneously handling an average of more than 20 Java migration projects per year.
Inevitable Java Framework Update
Frameworks with security and other issues
Struts 1 support ended after April 2013.
Seasar 2 support ended after November 2016.
WACs V8 support ended after April 2018 …
Support issues
When updating hardware etc., the Java framework must also be updated.
New technology and function utilization issues
Without access to extensive developer functionality, modifying legacy web applications becomes difficult.
For instance, using Spring Boot can greatly simplify configuration and enable rapid application development.
Inconsistent technical standards
Each Jave framework requires a significant investment in terms of manpower, money and material.
Security problems
Even if the system operates and evolves solely within an intranet environment, issues such as multiple investments in vulnerability countermeasures, performance risks, and operational management remain.
Potential Problems in Changing Java Frameworks
Since updating Java frameworks is a one-time event, it is usually handled manually or semi-automatically in most cases.
Since structural changes and fundational functionality modifications are handled manually, it can result in costs that are around half of the cost of new development (high cost).
・Significant costs are often hidden in the name of specification changes, maintenance, and other factors,making cost control challenging.
The quality is poor due to human errors during manual corrections.
Limited budget leads to insufficient testing which results in poor quality.
Recommended AI-Powered Automatic Conversion
Leveraging over 24 years of experience and insights gained from over 850 migration projects, and team of over 600 professionals that can handle 50+ projects simultaneously, we have developed ‘AppModernizer’ – a revolutionary AI tool that streamlines migration processes, saving both time and cost.
Maintainability of Source Code after Migration
Change the structure of a Java program
Clear separation of system layers and objects reduces maintenance complexity.
Generate easy-to-understand Java code
Complying with the latest technical standards and improving readability makes maintenance and specification changes easier.
Track the correlation between variables and processes across the entire system
Through thorough analysis of the entire system, the quality of the logic components is improved several times over manual efforts.
Testing for Superior Quality with Fewer Man-Hours
While most migration companies rely on customer-provided test data for quality assurance, we use the only one Al-powered migration technology to test all the migration technical points to enssure quality with shorter testing time.
Implement Specification Changes During Migration
Prolonged system freezes during migration can be avoided using our catch-up solution.
AppModernizer can achieve almost 100% automated conversion. If customer provides the latest source code after each update, we can incorporate the changes by quickly converting them into target language.
Migration cases
Sales and logistics management system (Struts1, Seasar2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support, Go-Live support
- Migration information
- Java 6 to Oracle Java 17
JSP to Thymeleaf
Java6 + Struts1.2.9 + Seasar2 + S2Dao + Ajax + jQuery to Thymeleaf 3.0.15 + SpringBoot 2.6.6 + Mybatis 3.5.9 + Ajax + jQuery3.6
Red Hat Enterprise Linux 5 to Oracle Linux 8.5
Oracle Database 10g/11g to Oracle Database 19c
Windows 10 to No changes
IE11 (IE5 mode) to No changes
PrintStream FormEditor to SVFX-Designer 10.1, SVF for PDF 10.1 - Current system scale
- Java：834.6KL, JSP：320.0KL, JavaScript：975.2KL
- Development period
- 16 months
Store facilities management system (Struts2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java 1.6 to OpenJDK 17
Struts2 + Spring Framework + iBatis to SpringBoot 2.7.4 + MyBatis3.5.9
AIX7.1 to Red Hat Enterprise Linux Server 9.2
Oracle Database 11g to Oracle Database 19C
Windows7/Windows10 to Windows7/Windows10/Windows11
IE11(IE7 mode) to Edge118, Chrome118
IE7 to No changes - Current system scale
- Java：381.6KL, JSP：119.2KL
- Development period
- 9 months
Recruiting WEB system (SeaSar2, Struts2 to Spring Boot)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java1.8 to Java11(Amazon Corretto 11)
Seasar2, Struts2 to SpringBoot2.3.2 + Mybatis3.5.1
Windows Server 2008 Enterprise to AWS EC2(Windows Server 2022)
Oracle Database 12.1.0.2.0, Postgres9.2.10 to No changes
Windows10 + Chrome v74 to No changes - Current system scale
- Java：415.3KL, JSP/JavaScript：296.7KL
- Development period
- 10 months
Insurance management system (WACs,Struts1 to Spring MVC)
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- Java 5 to Java 8
WACsV4.3.4, Struts1.1 to SpringMVC 4.3.10
z/OS V1.10 to Red Hat Enterprise Linux Server 7.2(Azure)
DB2 V8 to DB2 V8 for Linux
Windows7/8/10 to No changes
IE11 to No changes - Current system scale
- Java/JSP：998.1KL
- Development period
- 27 months
Sales system (Struts1 to Spring MVC)
- Development process
- Inventory, migration design, source migration − migration test, system test support, user acceptance test support
- Migration information
- Java 8 to Java 13 (Oracle JDK)
Struts1.1 + Hibernate to Spring MVC 5.2 + Hibernate 5.4
Oracle Database 11.2 to PostgreSQL 11.7
Windows10 to No changes
IE11 to Edge 88, Chrome 8 - Current system scale
- Java: 461.4KL, JSP: 65.0KL
- Development period
- 7 months
Manufacturing system (WACs to SpringMVC)
- Development process
- Inventory, migration design, source migration − migration test, system test support
- Migration information
- Java 1.8 to Red Hat OpenJDK 17
SQLJ 3.72.44 to SQL + Java(Red Hat OpenJDK 17)
WACs 8.4.1 to SpringMVC 5.3.31 + MyBatis 3.5.11
DB2 v11.1.3.3 to Amazon RDS for PostgreSQL
Windows10 to Windows10, Windows11
Edge (IE5) to Edge (the latest version)
IBM-943 to UTF-8 - Current system scale
- Java: 388.7KL, JSP: 29.3KL, Shell: 26.7KL, SQLJ: 134.8KL
- Development period
- 14 months
Asset trading system (Seasar2 to Spring MVC)
- Development process
- Inventory, migration design, source migration − system test, user acceptance test support
- Migration information
- Java 1.6.0_19 to Amazon Corretto 21.0.2.13.1
Seasar2 to Spring FrameWork 6.1.2 + MyBatis 3.5.15
Oracle Database 12c EE to Amazon RDS for PostgreSQL 16
Windows10 to Windows10, Windows11 (verify operation)
Edge (IE mode) to Edge121.0.2277.112 - Current system scale
- Java: 220.5KL, JSP: 29.3KL, JavaScript: 34.4KL, CSS: 16.8KL
- Development period
- 13 months
Management system
- Development process
- Inventory, migration design, source migration − migration test, system test support, user acceptance test support
- Migration information
- Java 7 to AdoptOpenJDK 8
Teeda + Seasar2 + S2Dao to Thymeleaf3.0.11 + Spring Boot2.3.1 + MyBatis 3.5.3
MySQL 5.7 to SQLServer 2019
Windows 8.1 to Windows 10
IE11, Chrome, Firefox, Safari, Edge to No changes - Current system scale
- Java: 113.3KL, HTML: 48.2KL, JavaScript: 17.6KL, SQL: 13.2KL
- Development period
- 7 months