ModernizationInPlace means Modernization without Platform Change
ModernizationInPlace is a strategy based on of a combination of later versions of off the shelf IBM i servers (v6R1+) and HP 3000 applications that have been migrated to Linux or UNIX, commercially available off the shelf tools, open source tools and techniques that can be used to provide modernization solutions to almost any sized IBM i or former HP 3000 MPE/iX shop. This includes the largest organization as well as organizations with a small budget. On the IBM i, The strategy relies on making the modernization changes on an IBM I platform instead of migrating the application to Linux, Windows or UNIX. For migrated HP 3000 applications, it relies on the use of RDBMS’s (typically Oracle, IBM DB2 or Postgresql) as a replacement for Eloquence.
.Key features of the Transformix ModernizationInPlace approach are :
• iSeries/as400/IBM i/Power i or UNIX or Linux
• Web and Mobile UX
• Green Screen Modernization
• Cloud Hosting
• RDBMS Modernization
• Rapid Application Development
Transformix focuses on modernizing Legacy applications so that they are cloud architecture compatible through the following steps:
- Adopting a Cloud Architecture Strategy for All Applications
- Modernization Tools and Techniques
- Migration Tools and Techniques
- Development Tools and Staff Modernization and Consolidation
Modernization involves substantial changes to the application.
The definitions of migration and modernization overlap. However, a key difference is that modernization allows for more substantial changes to the application than migration allows.
Modernization might include:
- User Interface Upgrades
- Rich Clients
- Web Services Integraion
- Data source Upgrade -RDBMS
- Social Media Integration
- Programming Language Conversion
- Utility and 3rd Party Products Replacement
- Integration and Networking
- Web Services
- RSS feeds
Migration retains the look and feel and program runtime behavior of the application
In general, software migration (re-hosting) is the process of moving from one operating environment to another. In its purest form, software migration targets functional equivalence. That is, although the operating system, the database, the file system, utilities and third-party tools might have been replaced, the application continues to behave as it did in the source environment. This is sometimes referred to as a like-for-like migration.
Transformix Migration Steps are:
- Proof of Concept
Modernizing Legacy applications can be constructed whereby they modernize the code and data along with the developers and their tools.
Typical solution approaches has the following features:
- Common development languages
- IBM EGL
- Legacy development
- New development
- Modern UI Development (Web, Mobile, Rich Client)
- web services development
- The ability to consume outside web services
- A common toolset that is shared for all types of development
- A common strategy and toolset to test and deploy applications to all environments.
“We didn’t have enough time to spend on learning, writing from scratch in the new Open Systems environment and then testing everything while keeping the business operating. We also didn’t want to go hire someone to do all the work for us and then they leave and expect us to maintain a bunch of code that we still needed to learn.
Also, rewriting from scratch would have put the business at a higher risk because we’d have to reinvent all the logic with our unique business rules. It seemed much more sensible to use Transformix to migrate our code “as is” and just make it run in the new environment.
This meant that no code had to be rewritten and we would be able to continue to run with the existing business logic that was known to be working correctly. While I don’t know for sure how much money this approach has saved us in our time and in contract help to have everything rewritten in the native environment, I am confident this has saved us hundreds of thousands of dollars”
Tim Manns, Overtons