- Case-studies
- RPG -> Java migration
case-studies
Case-studies
Idemitsu Kosan, Nissan, Japan Airlines, SoftBank, Kyocera, TOTO, Murata Manufacturing, Japan Petroleum Exploration(JAPEX), Unitika, Nitori, Toppan, Ricoh, Nitto Denko, Token, DAIDO LIFE INSURANCE, Mizuho Research & Technologies, Okasan Information Systems, Kanden Systems, JAL Information Technology(JIT), ITEC HANKYU HANSHIN, Nishitetsu Information System, KIRIN BUSINESS SYSTEM, JFE Systems, KOBELCO SYSTEMS, Toray Systems Center, Bridgestone Software, Tec Information Systems, NEC Group, NTT Group, T.D.I, PERSOL P&T, Unisystem, etc.
Customer Testimonial (presentations)
What may occur during RPG → Java migration
Quality, maintainability and performance are three key factors for system migration. However, the following problems often occur during RPG → Java migration.
- As the time and budget of system migration is limited, bugs often occur in the re-development process due to missing functions and insufficient testing.
- Most conventional migration tools do not use AI technology. Maintainability of the migrated systems is bad and performance problems are likely to occur.
- Without automatic test tools, It will take a long time to test, and quality risk remains.
Our RPG → Java migration
- We can achieve almost 100% automatic conversion with AI tools.
- We can migrate to Java’s mainstream framework Spring to ensure the maintainability equivalent to that of new development. It is also possible for us to migrate to customer’s Java framework.
- With our advanced AI tool, we can analyze execution processes to merge SQL, optimize process to achieve desired performance.
*Performance is also depended on good H/W and N/W. - We perform scenarios and system testing based on our testing tools and know-how.
- Our testing coverage analytical tools can make sure all the technical points to be covered and the quality is significantly high.
Our RPG → Java migration effect
UI migration
- Migration to GUI
-
- Improved operability for using mouse, button, etc.
- Customize UI according to customer’s standards.
- A little slower response speed than the current system due to web system.
- Migration to CUI
-
- No need to do the operation training because of unchanged UI/UX.
- Higher automatic conversion rate and fewer cost.
- Quicker response speed than GUI.
System Reform Schedule
Migration Cases
Business System
- Development process
- Inventory, migration design, UI design – migration test, system test & user acceptance test support
- System reform information
- RPG & RPGLE → VB.NET2013
RPG & RPGLE → PL/SQL
PRTF → PDF
DB2 for i → Oracle11g
OS400 → WindowsServer2012 - Current system scale
- RPG：1,500KL, Form：221
- Development period
- 15 months
Production & Sales Management System
- Development process
- Inventory, migration design, specification documentation, source code migration – migration test, system test & user acceptance test support
- System reform information
- RPG → Java(online)
RPG → T-SQL(batch)
CL → PowerShell
DB2 → SQL Server
AS/400 → WindowsServer2008 - Current system scale
- RPG：155KL, CL：15.1KL
- Development period
- 9 months
Sales Management System
- Development process
- Inventory, migration design, specification documentation, source code migration – system test, user acceptance test support, go-live
- System reform information
- RPG & CLP → Java
CL → Java & PowerShell
DB2 → Oracle11g
OS/400(V5R3M0) → WindowsServer2008 - Current system scale
- RPG：110KL
- Development period
- 8 months
Sales System
- Development process
- Inventory, migration design, specification documentation, source code migration – migration test, system test & user acceptance test support
- System reform information
- RPG & CL → Java
DB2 → SQL Server 2008
OS/400(V5R3M0) → WindowsServer2008 - Current system scale
- RPG：69.2KL, CL：14.7KL
- Development period
- 7 months
Production Management System
- Development process
- Inventory & slimming, migration design, UI design – system test, user acceptance test support
- System reform information
- RPG, RPGLE → Java
CL → Java/Shell
DB2/400 → PostgreSQL v10.0
IBM V7R2 → Linux7.2 - Current system scale
- RPG：46.4KL
- Development period
- 10 months