Application Migration Definition
The term "migration" can mean different things in different contexts so its worthwhile defining what Micro Focus means by "migration" in the context of its Application Migration and Modernization offering.
Micro Focus uses the term "migration" to describe the process of taking an application that currently operates on a mainframe or mid-range platform and enabling it to operate (execute) on a new hardware platform running Windows, UNIX, Linux or zLinux.
Some examples:
- An application currently operates on a HP3000 mid-range server but you wish to "migrate" it to a fully supported Intel-based server running Windows.
- An application currently runs on a Unisys 2200 mainframe but you wish to "migrate" it to a more contemporary server running Linux (Red Hat or SuSE) or UNIX (AIX, HP-UX or Solaris).
- An application currently executes on a Bull mainframe but you wish to "migrate" it to a more strategic server running UNIX, Linux or Windows.
- An application is currently deployed on a z/OS partition but you wish to "migrate" it to a zLinux partition on your z Server
- An application currently functions on a VSE mainframe but you wish to "migrate" it to an alternative server running UNIX, Linux or Windows.
To perform any migration involves making the "appropriate changes" to enable the application to operate on the new platform and typically involves some or all of the following:
- Switching to a database technology that’s available on the new target platform
- Exporting data from original database and importing it to the new database
- Introducing a transaction processing and screen handling system that’s supported on the new platform
- Updating application code so it compiles and runs correctly on the new operating environment and software stack
- Ensuring job control elements and scheduling capabilities are reproduced on the new environment
Frequently Asked Questions
Q1: Is a migration project only applicable if we intend to abandon the current hardware platform?
A1: No, not all.
Sometimes the original platform is completely shut down because
- the platform you are migrating from is at end of life and this was the original catalyst behind the decision to migrate
- the application you are migrating is the last application still operating on the platform you are migrating from
- the other applications remaining on the platform are being replaced by a package and so once the migration is complete and the package implementation is finished, the original platform can be shut down
However, often the original platform remains in operation because
- there are many more applications that will remain on the original platform and your migration project is focused on just one application where there is a concrete business benefit in migrating this specific application e.g. postponing an MIPS upgrade, freeing MIPS for other applications etc
- the objective of the re-host project is to make the application functionality available on a new platform, in addition to it the original platform, so the business has a choice of platforms on which to provide the capability depending on the geography or size of business within a territory
- the original platform will still remain as the strategic platform for running all "new business" applications while an alternative lower cost platform is used to run less strategic applications, closed book businesses or to provide lower cost access to historical data
Q2: Does a migration project mean abandoning existing languages and skill sets?
A2: No, not with Micro Focus’s approach to application migration.
If fact, fundamental to Micro Focus’s approach to migration is the golden rule of changing as little as possible during the migration, as this dramatically reduces risk and minimizes implementation time line.
However, some languages, for example, mainframe assembler, are simply not available on the target platform and so must be replaced if the functionality they provide is still required. In such cases, Micro Focus will recommend the use of automated conversion tooling to convert the application code, ideally to whatever language the bulk of the application is written in. This rationalizes the resulting software stack and an maximizes re-use of existing skill sets.
