- Migration Pattern
- Oracle Forms to Java migration
migration-pattern
Migration Pattern
Why migrate from Oracle Forms to Java?
Oracle Forms will eventually be migrated to new technologies.
Modernizing your Oracle Forms system early, while your internal team still retains much of the legacy system knowledge, can better support your migration and lead to lower migration costs.
Operational and modification expenses will also be reduced after migration.
Features of Our Conversion Service
Our proprietary rule-based AI tool can understand Oracle Forms system items accurately, and create pure-Java system comparable to those built by human programmers, with the highest quality and the lowest cost, proven in many past projects.
Features of AppModernizer’s Automatic Conversion
Achieves extremely high quality, low cost, and high maintainability, while also enabling integration with other Java platforms.
Testing for Superior Quality with Fewer Man-Hours
Instead of relying solely on customer-provided test data for quality assurance, we conduct test of all technical points and critical business processes to rigorously ensure quality and reduce test cost.
Extremely High Quality and Low Cost Compared to Rewriting
※¹ This is mainly a fine-tuning of the screen and report UI, and does not affect business logic.
※² JUAS (Japan Users Association of Information Systems) states that the industry-standard post-release bug rate is 0.084 to 0.1 per thousand lines of code (KL).
※³ Since business logic processing can be converted almost 100% automatically, the number of defects in the business logic portion is extremely low. Minor issues such as display position issues may occur, but this will not affect the use of the system.
Samples of AI-powered Language Conversion
①Change program structure from Oracle Forms to Java
②Generate pure Java code
Modernizing to pure Java and the latest Java technology standards is important for maintenance and improvement.
UI migration
Change the Oracle Forms screen to a standard HTML5-based web screen
Migration Cases
Production management system
- Development process
- Inventory, migration design, source code migration − migration test, system test & user acceptance test support
- Migration information
- Oracle Forms 12c to Java(OpenJDK16)
PL/SQL to PL/pgSQL
Adopting Spring MVC 5.3.7 + Spring Boot 2.5.0 + Thymeleaf 3.0.12 + Vue 2.6.8
IE 11 to Chronium Edge 92
WebLogic to Apache Tomcat 9.0.45
Oracle 12c to PostgreSQL 13.3
Keeping Windows Server 2016 - Current system scale
- Oracle Forms: 305.09KL, PL/SQL: 35.3KL
- Development period
- 16 months
Logistics management system
- Development process
- Inventory, migration design, specification documentation, source code migration − migration test
- Migration information
- Oracle Forms 10g to Java7
Adopting ASF(Customer specified framework)
Keeping PL/SQL
Oracle10g to Oracle11g
AIX 5 to RedHat Enterprise Linux 6.4
OAS 10g to JBOSS EAP6
Windows2003 SP2 to RedHat Enterprise Linux 6.4 - Current system scale
- Oracle Forms: 259KL, PL/SQL: 76KL
- Development period
- 11 months
Construction management system
- Development process
- Inventory, migration design, source code migration − migration test, system test & user acceptance test support
- Migration information
- Oracle Forms 10.1.2.0.2 to Java 1.6
Oracle Reports 10.1.2.0.2 to SVF9.0
PL/SQL to PL/pgSQL
Adopting Spring MVC
Oracle10g to PostgreSQL 10
Windows Server 2003 to RedHat Enterprise Linux 7.4 - Current system scale
- Oracle Forms: 107.6KL, PL/SQL: 39.9KL, Report:78
- Development period
- 10 months